AMICO  
Enabling Educational use of Museum Multimedia MEMBERSContributeUniversitySchool
How ToLibraryCommitteesDiscussionGovernanceManagementTimelineProjectsDocumentsMembershipContact Us

AMICO Users & Uses Committee

RLG / AMICO Logging and Reports
November 20, 1998

  1. Summary
    This document sets forth specifications for two areas of AMICO:

    1. The aspects of the system which should be logged (including where they should be logged)
    2. How the reports, created from the logs, should appear and who should receive them

  2. Information needed in AMICO Logging
    There are six categories of information which must be gathered and retained for AMICO:

    1. Image use
    2. Interface usability
    3. Retrieval
    4. Requests
    5. Searching
    6. Access

    2.1 Image Use
    As defined by the AMICO implementation team, this requirement includes the following elements:

    1. thumbnail
    2. snapshot
    3. inspection
    4. presentation

    The imageID, which will be recorded whenever an image is accessed, contains the contributor ID, the image size, and the image identifier. With this information, a report will be presented to AMICO, the contributors, and RLG showing which sizes and images are most often viewed. The report will contain the contributor, and image title, followed by the number of times the image was accessed as a thumbnail, snapshot, inspection, and presentation. A value will also be supplied for the number of times a presentation image was accessed immediately following inspection image access (instead of the Maximum Image Dimension option being set for presentation). Total numbers will be supplied at the bottom of the report.

    Sorting this report in descending order by number of snapshots followed by number of inspection images will provide information about which images most often appear in a full display. The information will be logged on the enterprise server. For an example report, see section 3.1.a.

    2.2 Interface Usability
    As defined by the AMICO implementation team, this requirement includes the following elements:

    1. Changing Display Options
      There are five options which can be changed in AMICO:

        a. Maximum image dimensions
        Image sizes will be logged in the section on Image use (2.1).

      The sort order, result number, result formatting, and full display viewing will be recorded on the enterprise server when items are sent to the brief display. This information will be reported to RLG. See section 3.1.b for an example display options report.

        b. Sort order
        Search results are, by default, sorted by creator. The options display allows the sort order to change to title or owner.

        c. Number of items in each search result screen
        The default number of items in brief display is 10. The number of items returned can be changed to 5, 15, or 20.

        d. Search result formatting (display)
        The default formatting for the brief display is images and text. Other options include images only or text only.

        e. Full display viewing
        The default for viewing the display includes image borders and menu backgrounds. The optional view is no borders or backgrounds.

    2. Saving to the Notebook
      Currently, the notebook works through the browser by creating a notebook file for each session. The notebook ID contains information which allows the browser to retrieve the brief display contents for the item chosen. The notebook ID's will be logged along with the session ID on the enterprise server when users logoff the system. The notebook report will contain the total number of sessions, the percentage of sessions in which the notebook was used, and the mean number and standard deviation of items contained in the notebook when users logoff. See section 3.1.d for an example report.

    2.3 Retrieval
    As defined by the AMICO implementation team, this requirement includes logging the search terms and indexes used when a full display is accessed. By logging this information, we will have a good idea which searches resulted in successful results. The report, sorted by index and in alphabetic order by search term will be sent to D & J, the contributors, and RLG. Boolean searches will be separated. The enterprise server will be the host for this information. An example report can be found in section 3.1.c.

    2.4 Requests
    As defined by the AMICO implementation team, this requirement includes the following elements:

    1. jpeg
    2. tiff
    3. metadata
    4. description

    When the option to download a jpg, a tiff, metadata, or descriptive information is chosen, a middleware script will log the sessionID, the imageID(s) and which option was chosen on the enterprise server. A report will be created for the testbed users, contributors, and RLG. The contributors' report will contain the contributor, the image title, and the number of times a download option is chosen for the particular image. For contributors, reports will be sorted by contributor and then by image title. A total count of the number of times each option is chosen will end the report (example report section 3.1.e). The testbed users' report will contain the institution name followed by the image title and the number of times each download option was chosen for the image. The report will be sorted by institution followed by image title. A total for each category will follow a insitution's requests (sample report section 3.1.f).

    2.5 Searching
    As defined by the AMICO implementation team, this requirement includes the following elements:

    1. index
    2. terms
    3. refinement
    4. result

    Just as in the logging of Eureka Web, logging of the index, terms, refinement, and result number will be logged by Zephyr. All three reports will be created for AMICO, the contributors, and RLG. The first report will contain the index, and the number of times the index was used, as well as the number of zero results, and results greater than 200. Percentage totals will end the report (sample report section 3.2.a).

    A second report will contain the search terms used and the indexes searched, sorted by most popular terms. Boolean searches will count as separate entries (sample report section 3.2.b).

    A third report will contain the number and percentage of boolean searches (sample report section 3.2.c).

    2.6 Access
    Access logging will record the date, time, and bytes of each AMICO session. The information will be logged by Zephyr and reported to AMICO, the contributors, and RLG. The report will contain the number of sessions started and the number of bytes used per hour each week. For an example report, see section 3.2.d.

  3. Anatomy of AMICO Logs and Reports
    AMICO logging will take place on two servers:

    1. Enterprise Server
    2. Zephyr

    Reports will be published monthly on the Web.

    RECIPIENTS: AMICO, Contributors, RLG

    3.1.a IMAGE REPORT (Example)

    CONTRIBUTOR IMAGE TITLE #THUMB #SNAP #INSP INSP-PRES #PRES
    Art Gallery of Ontario Seal Hunting 34 20 9 6 6
    Center for Creative Photography Winter Squash 35 15 10 3 4
    TOTALS 69 35 19 9 10

    Sort Note: The table above is sorted by number of snapshots then by number of inspection images.

    RECIPIENT: RLG

    3.1.b DISPLAY OPTIONS REPORT (Example)

    SORT % RESULT % DISPLAY % VIEW %
    creator 85% 5 10% images/text 98% normal 77%
    title 10% 10 75% images only 1% plain 33%
    owner 5% 15 5% text only 1%    
        20 10%        

    Sort Note: N/A

    RECIPIENTS: AMICO, Contributors, RLG

    3.1.c FULL DISPLAY REPORT (Example)

    INDEX SEARCH TERMS
    Creator Monet
    Creator Monet, Claude

    Sort Note: In the above table, items are sorted alphabetically by index and then search term

    RECIPIENT: RLG

    3.1.d NOTEBOOK REPORT (Example)

    # Notebook Sessions % of Total Mean # Items Standard Dev. #
    500 50% 5 4

    Sort Note: N/A

    RECIPIENT: Contributors, RLG

    3.1.e DATA REQUEST REPORT #1 (Example)

    CONTRIBUTOR IMAGE TITLE #JPEG #TIFF #DESC #META
    AGO Seal Hunting 1 0 2 1
    AIC Pier Table 5 1 3 1
    TOTALS 6 1 5 2

    Sort Note: The above table is sorted by contributor and then image title.

    RECIPIENT: Testbed Users, RLG

    3.1.f DATA REQUEST REPORT #2 (Example)

    INSTITUTION IMAGE TITLE #JPEG #TIFF #DESC #META
    Boston Col. Pier Table 5 1 3 1
    TOTAL 5 1 3 1
    CMU Seal Hunting 1 0 2 1
    CMU DOGS 2 2 4 5
    TOTAL 3 2 6 6

    Sort Note: The above table will be sorted by institution and then image title.

    3.2 Zephyr Server Logs

    RECIPIENT: AMICO, Contributors, RLG

    3.2.a REPORT ON SEARCHING (Example)

    INDEX #SEARCH #ZERO #>200
    Creator 400 10 20
    Owner 200 0 10
    TOTAL 400 0.025% 0.075%

    Sort Note: N/A

    3.2.b REPORT ON SEARCHING Part 2 (Example)

    INDEX TERMS #USED
    Keyword Art 43
    Keyword Painting 41

    Sort Note: The above table is sorted by search term and then index.

    3.2.c REPORT ON SEARCHING Part 3 (Example)

    REFINE #USED %SEARCHES
    and 200 10
    or 200 10
    not 100 5

    Sort Note: N/A

    RECIPIENT: AMICO, Contributors, RLG

    3.2.d REPORT ON ACCESS/USE

    Week Hour # Sessions # Bytes
    011298 23:00 10 3008
    011298 24:00 5 1005
    TOTAL 508 120 MB
    081298 01:00 0 0

    Sort Note: The above table is sorted by week and then hour.


Last modified on