| NUMBER | CRITERIA DESCRIPTIONS | RATING |
| OPAC Access/ Display/ Navigation | ||
| 1 | Interface screens are customizable by the library system, both in terms of visual design and functionality. Would Yale have complete control of the HTML that is sent to the browser? If not, which functions are not customizable? Which functions must be customized by the vendor? To what extent does customizing affect performance? Are customized changes automatically migrated to new versions of the interface? | Essential |
| 2 | Interface screens are customizable by libraries within system (e.g., Medical Library-specific version that differs from other Yale library versions) | Important |
| 3 | Easy-to-use non-proprietary, design tools are provided for customizing | Important |
| 4 | The library system and/or individual libraries can surround OPAC display with additional HTML (e.g., standard footers or navigation bar on every page) | Essential |
| 5 | The following alternative interfaces are always available in the web environment: | Essential |
| __ Menu | ||
| __ Command line (text input) | ||
| __ Graphically driven (mouse) | ||
| __ Function key alternatives to mouse action | ||
| __ Other (List): | ||
| 6 | The system has comparable functionality with various browsers (e.g., Netscape, IE). List compatible browsers and lowest compatible release. | Essential |
| 7 | The reader can utilize web browser navigation buttons while in OPAC | Important |
| 8 | The system is operable without proprietary client loaded on individual machines | Important |
| 9 | Describe how you support the need for a fast, text-only interface that could be used effectively for low speed network access. | Essential |
| 10 | The system is accessible to or adaptable for persons with disabilities via: | Essential |
| __ Functional with text-to-speech software | ||
| __ Font enlargement | ||
| __ Color insensitivity | ||
| __ Functional keyboard equivalents for elements that otherwise require activation by pointing devices such as a mouse | ||
| __ Other? | ||
| 11 | Remote authentication is possible for off-site users. Reader initiated transactions can take place without repeating authentication process. | Essential |
| 12 | Implementation of Unicode / non-Roman characters for display, input, indexing, and searching. Indicate when this functionality will be available for: | Essential |
| __ Japanese | ||
| __ Arabic | ||
| __ Chinese | ||
| __ Korean | ||
| __ Persian | ||
| __ Hebrew | ||
| __ Yiddish. | ||
| __ Other languages? | ||
| 13 | A "start-over" initiated by a reader purges his/her search history and transaction history | Essential |
| 14 | A "start-over" initiated by the system after inactivity purges search history and transaction history, with an inactivity period customizable by library | Essential |
| 15 | There is an option for a personalized reader profile tied to individual log-on (i.e., "my library" interface; default screen, links, default "home library," saved searches, customizable by reader). Describe functionality. | Desirable |
| 16 | It is possible to toggle to the MARC view of a record from the OPAC. Is the MARC view customizable? Describe customization options e.g., choice of fields be suppressed from public view). | Desirable |
| 17 | In what ways can the system record number be displayed from the OPAC (e.g., can be displayed in the MARC view, is always displayed, cam toggle on the system record number display)? | Desirable |
| 18 | There is easy and intuitive access to reader empowerment (e.g., ILL, renewal, etc.) via deliberate navigation to appropriate forms | Essential |
| 19 | There is easy and intuitive access to reader empowerment (e.g., ILL, renewal, etc.) integrated into reader's search process (e.g., a prompted option) | Important |
| Searching /Retrieval | ||
| Formulation of search | ||
| 20 | The reader can choose among various languages for the basic interface of his/her search session. Specify languages supported. | Desirable |
| 21 | The following search options are supported: | Essential |
| __ keyword | ||
| __ phrase | ||
| __ truncation (internal, left, right, implied; can truncation be disabled by reader?) | ||
| __ Boolean | ||
| __ nested | ||
| __ adjacency | ||
| 22 | These search options are supported: | Important |
| __ stacked | ||
| __ natural language | ||
| 23 | These search options are supported: | Desirable |
| __ acronyms | ||
| __ weighted searching (for relevancy ranking) | ||
| 24 | Call number searches recognize the numerous separate classifications used at Yale (LC, Old-Yale, SuDoc). | Essential |
| 25 | Call number searches can be qualified by location. | Important |
| 26 | Call numbers may be combined with other terms in a search | Desirable |
| 27 | The option to search author names in any order, with initials or forenames exists. | Desirable |
| 28 | List any other available search options. | Desirable |
| 29 | The search engine compensates for inaccuracies by | Desirable |
| __ fuzzy matches | ||
| __ spell checking | ||
| __ suggestion of plural forms | ||
| 30 | Any search engine compensation for inaccuracies is a reader-initiated option, not a default | Essential |
| 31 | What search limiters are supported: | Essential |
| __ format | ||
| __ date | ||
| __ language | ||
| __ LC call # | ||
| __ local call # | ||
| __ location | ||
| __ MARC fields. | ||
| __ other (list): | ||
| 32 | It is possible to establish a set of default limits before initiating a series of searches | Important |
| 33 | There is a clear indication of search limits currently in effect | Essential |
| 34 | It is possible to formulate a search consisting only of limits (e.g., search for all Spanish language books published in 1932) | Essential |
| 35 | "Stop words", if used, can be defined by the library. If "stop words" exist, how can they be searched? | Important |
| 36 | When searching by title, a reader can enter initial articles | Important |
| 37 | Symbols (e.g., musical symbols for sharp and flat) can be used in a search | Important |
| 38 | Filing indicators are acknowledged | Essential |
| 39 | Forward/backward browsing, and jumping, is possible through all indexes. Indicate exceptions. | Essential |
| 40 | MARC fields can be hypertext-linked to facilitate complementary searches. Which fields? | Essential |
| 41 | The library system and/or specific libraries can choose which fields are hyperlinked for redirection for new searches | Important |
| 42 | The system allows readers to store search statements for repeated future use | Desirable |
| 43 | SDIs (Selected Dissemination of Information) are supported - automatic re-runs and reporting of searches | Desirable |
| 44 | The system supports URL-constructed searching for all available search types (e.g., a link in a web-based tutorial initiates a pre-planned search when activated) | Essential |
| 45 | There is an available command line search mode compliant with Z39.58 standard (Common command language for online interactive information retrieval) | Important |
| 46 | Course reserves can be searched by these indexes: | Essential |
| __ Course number | ||
| __ Instructor name | ||
| __ Author/title | ||
| __ Call number | ||
| 47 | Course reserves can be searched by other indexes besides those noted above (e.g., by note fields). List other indexes. | Important |
| 48 | There is an option to abort a search at any time | Essential |
| 49 | Explain to what extent indexes customizable. Indicate any limits on number of indexes and index content. | Important |
| Search Results | ||
| 50 | There are different levels of detail in the display of results (like NOTIS guide/index screens). Describe these levels. Are they customizable? | Essential |
| 51 | Brief displays and/or indexes have the capability to display thumbnail images | Desirable |
| 52 | The upper limit of initial hits is unlimited. Is this true for all search types? Indicate exceptions. | Important |
| 53 | Limiting options are offered intrusively if there are too many hits. What size triggers offer of options? Is the alert customizable? | Essential |
| 54 | If there are no hits, there is an indication that "your entry would be here" in the results retrieved | Important |
| 55 | The system is capable of suggesting alternative search methods. How? | Important |
| 56 | Searches can be progressively refined and/or enhanced | Essential |
| 57 | The number of records retrieved for individual search terms in a multi-term query is displayed.. | Desirable |
| 58 | The system automatically integrates controlled vocabulary/authorized headings into subject search results (LCSH, MESH, AAT) | Important |
| 59 | Authorized headings do not appear in search results if there are no related hits | Important |
| 60 | It is possible to link to detailed shelf location information (explanatory text or graphic of floor plans) from a record's location statement - library system-wide and/or by individual library | Desirable |
| 61 | Formats are clearly distinguished from other formats in the search results (e.g., music scores, database, manuscripts, serials) How are they distinguished? | Essential |
| 62 | The system can recognize and filter duplicate field entries from the same record (e.g., same 130 and 245 fields) | Important |
| 63 | Display options available for serials include location of current and back issues, check-in status of issues. | Essential |
| 64 | Circulation status information is provided, including On Order, In Process, 24 hr. display of last discharge date | Essential |
| 65 | On Order material includes display of estimated date of arrival. | Desirable |
| 66 | Circulation status values are customizable. | Important |
| 67 | The reader's search history is easily displayed and manipulated during a session | Essential |
| 68 | The reader can define his/her own methods of sorting search results within a session. What sorting options exist? How do sorting mechanisms relate to size of results set? How are defaults for sorting defined by the library system? Can they be defined by individual libraries within the system? | Essential |
| 69 | The reader can sort search results by monographic series number | Important |
| Saving Search Results | ||
| 70 | It is possible to mark selected records or a range of records for download and the system maintains persistence in marking throughout a results set (i.e., markings not lost on going to next screen). | Essential |
| 71 | The specific fields of a record that are included in a download can be defined. Who defines them - library system, individual libraries, reader? | Important |
| 72 | The system supports fee-based printing remotely to a central location | Important |
| 73 | The system supports download via e-mail | Essential |
| 74 | The system supports the use of bibliographic software like EndNote, ProCite. List supported formats. | Essential |
| 75 | The system supports export in style manual formats | Desirable |
| 76 | The system supports download of info. to PDAs (Personal Digital Assistants) | Desirable |
| 77 | The system supports a "shopping cart" model for collecting marked records for an extended search | Important |
| 78 | The system supports a "shopping cart" model for collecting marked records for a whole session | Desirable |
| 79 | The system supports a "shopping cart" model for collecting marked records for searches of multiple databases | Desirable |
| 80 | The system supports longterm saves, via the reader's personal profile | Desirable |
| Reader-initiated Functions | ||
| 81 | Self-service check-out and renewal by readers are possible | Important |
| 82 | Readers can make and can cancel circulation requests for paging, holds, recalls, ILL - with personal information provided via initial log-on persistent throughout a session | Important |
| 83 | If a reader cancels a recall, the system will undo the revised due date for the original borrower and tell the original borrower that early return is not required. How is reader notified of the changed duedate (e.g., printed notice, email notice, message that is activated when reader's record is accessed?) | Desirable |
| 84 | Readers can make context-sensitive requests for photocopies or purchase from citation indexes (i.e., no need to re-key bibliographical information) | Desirable |
| 85 | Faculty can make context-sensitive requests to place items on course reserve (i.e., no need to re-key bibliographic information) and can cancel such requests | Desirable |
| 86 | Readers can create their own provisional patron records (subject to review by staff) | Desirable |
| 87 | Readers can revise their patron records, including email address, local address, home address, phone number - provisionally or permanently? Are staff and/or reader notified of change? How? Is notification optional? | Desirable |
| 88 | Readers can view their personal record of check-outs, fines, etc. | Essential |
| 89 | Readers pay fines online. If so, how? | Desirable |
| 90 | Readers can contest fines online. If so , how? | Important |
| 91 | Readers can direct reference questions to the library staff, electronically, from within their session | Important |
| 92 | Readers can direct feedback and evaluation of services to the library staff, electronically, from within their session. | Important |
| 93 | Readers can attach requests to order records which automatically generates a "rush" status through cataloging and processing. (Integration of acquisitions, cataloging and circulation) | Desirable |
| 94 | Personal information (ID) of reader is persistent through various transactions after initial log-on | Essential |
| 95 | Social Security Number (which is the University ID) is not used, displayed or printed during any reader-initiated functions. | Essential |
| Connectivity with other Electronic Resources | ||
| 96 | The system provides a single point of entry into the library's online environment, serving as a gateway to the central catalog as well as other e-resources to which the library has access - providing common searches when possible, or, at least, clear indication of access to available e-resources | Essential |
| 97 | The system supports hypertext links to finding aids and full text resources, and links back to a specific catalog record. | Essential |
| 98 | Multiple layers of links are possible between the catalog and other available e-resources, e.g., article-level references are linked to local holdings of journal, catalog records linked to tables of contents, links to sound-recordings, etc. | Important |
| 99 | The system supports URL-constructed searching for individual items (e.g., by ISSN or ISBN) so that outside e-resources can provide hooks to specific library holdings. | Essential |
| 100 | Simultaneous searching of multiple MARC format databases can provide integrated, de-duped search results, i.e., one listing of relevant hits - whether books, articles, etc. | Desirable |
| 101 | Simultaneous searching allows the reader to limit searches to reader specified groups of databases. | Important |
| 102 | The inaccessibility of a normally available e-resource will not disable or slow down a multi-database search | Essential |
| 103 | Simultaneous searches can incorporate both bibliographical and nonbibliographical databases (e.g., image databases), by drawing on multiple forms of metadata, and can provide an integrated search results display. | Desirable |
| 104 | When doing simultaneous searching of multiple databases, it is possible to conduct a file relevance search prior to actually retrieving results or de-duping, i.e., to identify which databases have how many hits for a particular search. Results clearly indicate source database. | Desirable |
| 105 | The library catalog can be searched simultaneously from other e-resources to which the library subscribes, with results presented through these other interfaces (e.g., Ovid search that also searches the catalog, with results displayed in Ovid). | Desirable |
| 106 | Reader-initiated ILL or purchase requests can be made from within other databases without rekeying citation data. | Desirable |
| 107 | The system supports an electronic reserve system. Does the system include an electronic reserve component itself? Does it work with third party electronic reserve systems, if so how and which ones? Does it support various file formats (PDF, HTML, SGML, graphics, etc.) for the retrieval of reserve material? | Important |
| 108 | The system can interact smoothly with "courseware" such as the classes.yale.edu system. | Desirable |
| Help Features / Messages/ Prompts | ||
| 109 | There is context-sensitive presentation of help files | Essential |
| 110 | There is a persistent index for all help screens | Essential |
| 111 | It is possible for individual libraries within the system to design their own individualized help screens | Important |
| 112 | There a context-sensitive mechanism for linking to vendor-generated or locally-generated tutorials (of an extent or purpose beyond simple help files) | Desirable |
| 113 | The system gives an indication of status if response is not immediate (e.g., "Working...."), or if system is down | Essential |
| 114 | Error messages are customizable by library system. And by specific libraries within system? | Essential |
| 115 | The system provides a mechanism for intrusive dissemination of important library news bulletins | Desirable |
| 116 | Readers are automatically notified of the status of their circulation requests (e.g., arrival of book recalled) | Essential |
| 117 | Readers are automatically notified of the status of their ILL or acquisition/cataloging requests | Essential |
| 118 | Readers can be automatically notified by serials module, e.g. re. arrival of new issues of a particular journal | Desirable |
| 119 | When automatic notification is available, how is notification given? E.G., upon login, through email, printed notice, voice-mail? Can readers request not to be notified? | Important |