YUL Criteria Lists

Number Category QUESTION
  Product Implementation Services and Resources  
1   Are conversion services available ?
2   Describe Quality Control measures for conversion services
3   How many NOTIS conversions ?
4   Provide examples of implementation timetables for conversion/implementation
5   What factors have been most responsible for causing implementation timetable disruptions ?
6   How many implementation personnel are librarians ?
7   For the following categories, how many staff do you have and how are they deployed during a typical implementation: Trainers, Software Consultants, Hardware Consultants, Database Consultants?
8   How does the vendor measure the success of implementation ?
9   What varieties of instructional support (instructor-led, online help, AV modules, etc.) does the vendor provide?
10   Will the vendor provide a record of the actual implementation particulars of this implementation for the customer?
  Product Support Services and Resources  
11   Provide a general description of the levels and degrees of support you offer.
12   What support services are available during normal business hours (Eastern time)?
13   What support services are available 24 hours a day, 7 days a week year around?
14   What quality assurance measures ensure that support services are available as promised?
15   How is support available ? (Phone , WWW , Email , On-Site)
16   How are these delivery modes monitored to detect and avoid saturation ?
17   How does the vendor measure success of these delivery modes ?
18   How does the vendor triage incoming requests for help and info ?
19   How does the vendor measure success of these triage practices ?
20   How many product support staff does the vendor employ?
21   What professional background and training do the product support staff have?
22   How are product support staff deployed to be most responsive in diverse environments?
23   Is any one (or more) staff assigned to oversee and ensure the quality of support services for individual libraries? If so, who might be assigned to the Yale library, and to what other libraries has that person been assigned? Can you provide a resume for this person ?
24   What problem tracking and resolution mechanisms does the vendor employ?
25   What measures of success does the vendor use for its problem resolution services?
26   What user groups does the vendor sponsor; how long have they been in existence; are there bylaws, etc?
27   Are there user groups not sponsored by the vendor with which the vendor works collaboratively?
28   What range of product support and development activities is conducted through user groups?
29   What vendor staff are assigned to these user groups?
30   What professional background and training do the vendor staff assigned to Users Groups have?
31   How are vendor staff assigned to User Groups deployed to meet the needs of the different kinds of member libraries?
32   What roles do customers play (if any) in setting user group agendas, conducting meetings and reporting to the vendor's senior management?
33   What warranties does the vendor make to its customers?
34   What procedures does the vendor use for interpreting its warranties, when some provision of the warranty is disputed?
35   What means have been employed by either customers or the vendor to resolve disagreements?
36   Is there any history of litigation between vendor and customer regarding product performance?
37   Is there any history of litigation between vendor and customer regarding contract compliance?
38   Have vendor and customer ever mutually agreed to cancel a contract? Why?
  Product Development Services and Resources  
39   What kinds of assistance does the vendor provide during implementation of new releases ?
40   What testing procedures does the vendor employ in developing new functionality?
41   How are new release testing results shared?
42   What specific quality standards does the vendor use for deciding that new software is ready for release?
43   What are the common causes for failures, or the common ingredients for success in new releases?
44   What considerations inform the vendor’s decisions about the pace and timing of new software releases?
45   How frequently does the vendor issue new software releases?
46   Has this frequency varied significantly over the last three years?
47   How does the vendor measure its success in meeting its goals for on-time delivery of new releases?
48   How many patches/fixes were required to correct or improve the operation of new releases over the last 3 releases?
49   What software design measures ease upgrades and minimize disruption to library services?
50   How much down time have libraries experienced in bringing up each new releases over the last three years?
51   Did the vendor provide estimates of the required down time?
52   How did customer experience compare with vendor estimations for down time?
53   What relationships exist with companies selling/developing information technology products (or any sort) and/or information content of likely interest to ARLs?
54   What strategic purposes inform these vendor-to-vendor partnerships?
55   What partnerships does the vendor have with individual customers?
56   What strategic purposes inform these vendor-to-customer partnerships?
57   How does the vendor measure the success of its partnerships with customers?
58   Have any (vendor/vendor or vendor/customer) partnerships been strikingly successful or unsuccessful? Describe.
  Vendors Business Complexion  
59   How many staff does the vendor now employ? 
60   How many staff are librarians ?
61   How many of these staff are assigned respectively to (as a number, a percent of total, or a ratio): Sales, Production Implementation, Product Support, Product Development, Business Management, Other tasks.
62   How (if at all) has the vendor’s staffing patterns varied significantly in the last three years?
63   What was the average gross pre-tax income of the vendor over the last three years?
64   Does the vendor price software maintenance and product development separately? If so, on what principles does the vendor distinguish between the two?
65   How much of the vendor’s income over the last three years was attributable respectively to: Initial System Sales, Product Implementation fees, Product Support Service fees, Product Development fees (I.e., charging for new releases), Other activities.
66   What measures does the vendor take to control the cost to customers of project implementation and product support and development?
1 Multi-tier System must have a multi-tiered Client/Server Architecture Essential
2 Multi-platform System must provide Windows, web browser and text-based clients Essential
3 Standard DBMS Data must be stored in a RDBMS or ODBMS conforming to industry standards, i.e. non-proprietary Essential
4 Standard WWW System must support use of standard WWW servers and browsers Essential
5 Scaleable Each layer of the architecture must be scalable and manageable independently from every other layer Essential
6 Z39.50 clients System should support all Z39.50 compliant clients Essential
7 Browser Independent Browser Clients should run in either a Windows or Mac/OS environment Important
8 Staff clients Staff clients should run in all Windows environments (Win 95+) Important
9 Distributed The architecture should support multiple processors Important
10 ISO based ILL The system should provide tools for ISO 10160/10161 protocols for ILL Important
11 X12 based EDI The system should provide tools for an X12 interface to EDI Important
12 UNICODE The system should provide for multiple national languages through implementation of ISO standard 10646 (UNICODE) Important
13 ISO based Quality The system should conform to the ISO 9000-3 guidelines for the development and support of quality software products. Important
14 OO interface The system should support a distributed object model such as CORBA, IIOP, EJB Desirable
15 Thin client Support for "thin clients" such as the Solaris Sun Ray Desirable
16 University ITS supported servers Servers must run on a unix platform from either IBM or SUN Essential
17 University YAD supported clients Browsers and staff clients must run on Intel platforms Essential
18 University LSO supported OS Browsers and staff clients must run on Windows NT and Windows 2000 Essential
19 University supported open system Browsers and staff clients should run on LINUX systems and network appliances Desirable
20 Business Critical reliability System must have a reliability factor of 99.99% Essential
21 Business Critical Availability System must operate on a nearly 24X7 basis Essential
22 Reporting(1) System must provide regular reports on the status of all system management and policy files, as well as all profiles, tables, and other parameters that control the system. Essential
23 Reporting(2) Vendor must provide established procedures to report and track application problems as specified in ISO guideline ISO-9000-3 Essential
24 Scaleable hardware System should be designed to run on parallel system Important
25 Low Maximum response time Transaction response time less than 3.0/secs Essential
26 Low Typical response time Transaction response time less than 0.5/secs Desirable
27 Low Maximum startup time Client Initialization time less than 30 seconds (after OS initialization) Essential
28 Low typical startup time Client Initialization time less than 10 seconds (after OS initialization) Desirable
29 Non disruptive update and reporting (1) Batch data loads, indexing and report generation should not require the system to go down Important
30 Non disruptive update and reporting (2) Batch data loads, indexing and report generation should not significantly impact performance Important
31 Operational documentation Vendor must provide documentation for all transactions, batch, and reporting jobs Essential
32 Recovery Vendor must provide recovery procedures for all tasks including batch type and reporting jobs Essential
33 Fix Distribution Vendor must provide established procedures to distribute bug fixes Essential
34 Upgrade distribution Vendor must provide established procedures for release updates and new versions of the application Essential
35 Customization Customization and maintenance tasks of the application like table changes should be performed by a graphical tool Important
36 Well structured installation Clients used to access the system should be easy to install, maintain, and few in number Important
37 Access to Source Code The system must provide a flexible development environment by providing and maintaining customer access to current source code to facilitate integration of: locally developed applications; third party software; and interoperability with other Yale systems. Essential
38 ISO 9000 The ability to demonstrate quality control over vendors, internal processes, and user support interfaces as defined in ISO 9000, 9001-9003 Essential
39 Version control The system must provide both forward and backward version control of all software components both distributed and under development. Essential
40 Industry Standard language Only modern and current programming languages, operating systems, network and database interfaces, such as ANSI C, C++, Java, and Visual Basic may be used. Any software content consisting of object code only, or developed using non-industry standard programming languages is unacceptable. Essential
41 Industry Standard Data Interchange Must support data access via standard, non-proprietary database and network protocols ODBC, JDBC, SQL92, CORBA, IIOP, RMI, or equivalents as well as IETF approved TCP/IP transfer protocols Essential
42 Incremental change The development environment should accommodate short development cycles and continuous improvement, without the need for frequent wholesale upgrades to remain current. Important
43 Industry standard IDE Access to services should be based on integrated development environments (IDE) provided by IBM, Sun, Microsoft and others Important
44 Class extensions The ability to locally extend or implement common OO class libraries and interfaces Important
45 XML extensions XML, XSL, XHTML, are all preferred methods of abstracting data content from layout and description. Important
46 Standard scripting tools Scripting interfaces, such as Apache CGI and PERL, which work well in the open software environment. Important
47 Java standard Defined by Sun JDK 1.1.3 and above Important
48 Support for active user development Provision of tools / venues / websites for the development and exchange of user developed software Important
49 Single development language per component Multiple development languages within a single component is undesirable except in the context of a clearly defined short term migration effort. Desirable
50 Enterprise Java Beans As defined by Sun Java 2 and above Desirable
51 JDBC/CORBA/IIOP Current Industry standard Desirable
52 ISO 9000 certificate Certification of compliance by ISO Desirable
53 TCSEC level C2 design System should be able to demonstrate compliance with DoD Trusted Computer System Evaluation Criteria class (C2).  
54 Systems in this class make users individually accountable for their actions through login procedures, auditing of security-relevant events, and resource isolation. The following are minimal requirements for systems assigned this rating: Essential  
55 Secure Clients System must have secure clients -- private data is encrypted when passed over the network Essential
56 Encrypted Login Login to technical service modules dependent upon userid and password must be encrypted Essential
57 Log transactions Secure transactions must cut a log record that can be used to trace a transaction Essential
58 No Compromise of trusted subsystems System must not use trusted subsystems (e.g. DBMS) in a manner that defeats or compromises the inherent security of the subsystem (e.g. trivial passwords) Essential
59 Multiple authentication Authentication and authorization must be able to be applied to a user or workstation or both Important
60 Multiple secure domains The system should not adversely affect or be affected by proxies, firewalls or other university security infrastructure Important
61 Secure scripting All scripts should be centrally located and protected with wrappers or sbox or equivalent Important
62 Validate input Programs must validate user input Important
63 Protect server information System protects information about site and server host Important
64 Secure Shell Telnet and FTP access to services should be done via SSH2 Important
65 PKI enabled An API into a PKI capability should be available so that certificates can be used for authentication and authorization Desirable
66 TCSEC C2 certified Where possible, systems and subsystems should be TCSEC certified. Desirable
  Staff Productivity    
1   Reports can be defined online through an easy-to-use, graphical interface with interactive editing. Essential
2   A suite of standard reports can be used as is or customized to meet varying requirements. Essential
3   Authorized staff can produce and print most standard or customized reports on demand, without Systems staff involvement. Essential
4   Reports can be generated unattended (e.g., in a nightly batch) on a pre-determined schedule. Essential
5   Report structure, parameters, specifications and criteria can be saved and reused. Essential
  Report definition    
6   Relate one time period to another and current activity to previous periods, e.g., current year to past year, total circulation this July to total circulation last July. Important
7   Use Boolean logic, date calculations, and mathematical calculations. Essential
8   Allow staff to select, sort, and set limits on fields to be included in reports. Essential
9   All fields of all files in the system are available as report criteria and/or content. Essential
10   Produce reports using selection criteria across multiple database tables. Essential
11   Provide formatting options including, but not limited to, definition of headers, footers, and column headings; design of layout; and sort criteria. Essential
12   Sort data on multiple levels and provide totals and subtotals. Essential
13   Provide summary statistics for various timeframes, e.g., current day, month-to-date, previous month, year-to-date, etc. Essential
14   Does the LMS support the projection of future trends from current data? How? Desirable
15   Define reports using third-party tools via ODBC (or ODBC-like) connections. Examples include a relational DBMS like Access or a query tool like Brio Query. Essential
16   Perform basic statistical calculations. Essential
17   Generate standardized and customized reports using archived data. Important
18   Generate reports regularly required of YUL. See ARL forms, http://www.arl.org/stats/arlstat/99survey.pdf which are representative of such reports. Essential
19   Provide shelf listing by location and across location by call number. Note: YUL uses multiple classifications, e.g., LC, old-Yale, SuDoc and others. Note also that it should be possible to generate reports using [permanent] location or temporary location. Essential
  Report Output    
20   Support the application of statistical analysis to any report generated. Essential
21   Produce reports in a variety of formats including, but not limited to, hard copy, ASCII, ASCII delimited, HTML, and email, regardless of how report is generated, i.e., whether created by using a standard report or an SQL-based report generator. Important
22   Run reports and manipulate results in real time. Essential
23   Support scheduled and on-demand report generation without negative impact on system operation. Essential
24   Authorize report generation based on login ID and password or another similarly effective method. Essential
25   Provide very flexible security for report generation. Some staff will be authorized to run only specific reports. Others will have no report generation restrictions. Important
26   Provide easy to use data dictionaries. Important
27   Maintain a system log of reports generated. Important
28   Provide ability for system administrator to monitor and control report generation in conjunction with system performance. Essential
29   Maintain storage of reports. Essential
  General Statistical Reports    
30   For all files, provide statistical reports, e.g., number of authority, bibliographic, patron, vendor, item, order, etc..  
31   Selection criteria for statistical reports can specify any data element in any record in any file, e.g., number of records based on record status, source, dates, field content, field existence, etc.  
32   For all files, provide reports of file activity over a specified period of time, e.g., number of records added, updated, deleted, etc. this month, this year, this semester, etc..  
33   For all files, provide reports based on the application of mathematical, statistical, or date calculations to records which meet selection criteria.  
  General Inventory Reports    
34   For all files, provide inventory reports, e.g., lists of records.  
35   Selection criteria for inventory reports can specify any data element in any record in any file.  
36   Inventory report content can include any data element in any record in any file.  
  Access Services Reports    
37 Calculate and Inventory Report all transactions involving fees and fines; criteria will specify location and timeframe. Report output should include transaction date and type, payment type, amount paid, item record and patron ID; sort on transaction type/transaction date/amount paid/payment type; subtotal after each transaction type and total after all entries.  
38 Calculate and Inventory Report turnaround time for holds paged from another location; criteria will specify locations (requesting, supplying) and timeframe. Report output should include request date, paging library, discharge date, supplying library, and turnaround time (calculated from request and discharge dates); sort by supplying library/request date; calculate average turnaround after each library and calculate overall average after all libraries.  
39 Count Count and report the total number of items for each of the following criteria--checked out, by patron category; checked out; recalled, by type (regular or rush); declared lost, missing or billed; used in-house--within a specified timeframe and for specified service location.  
40 Inventory List all items on reserve; criteria will specify location and timeframe. Report output should include call number or shelving number, author, and title; sort by call number or shelving number.  
  Acquisitions Reports    
41 Calculate and Inventory Produce monthly and quarterly reports of all purchasing card transactions; criteria will specify order unit code(s). Report output should include transaction date, record key, title, vendor, receipt date, amount of charge; sort by transaction date/vendor/title; total after all entries.  
42 Count Count and report the total number of books received each month; criteria will specify receipt unit code(s).  
43 Inventory List all titles received on exchange; status will be determined by exchange coding and open order record, and criteria will specify order unit code. Report output should include record key, title, call number, exchange partner, exchange number, date of last receipt; sort on title.  
44 Calculate Calculate vendors' turnaround time and fill rate for book orders; criteria will specify order unit code(s), vendor codes, and timeframe. Report output should include vendor name, total number of orders, number of orders filled, average number of days to fill, and percentage filled; sort on vendor.  
  Cataloging Reports    
45 Calculate and Inventory Count the total number of item records based on specified status, e.g., missing, lost, withdrawn, temporary location. Report output should include record key, status, location, and total number of items; sort by status/record key.  
46 Count Produce a monthly report of bibliographic records added to the database. Report output should subtotal on type of material and total all records added; sort by material format.  
  Collection Development Reports    
47 Inventory List all continuation orders (serials, standing orders, multi-volume monographs); criteria will specify receipt unit or location code(s). Report output should include record key, title, call number, vendor, date of last receipt; sort by title.  
48 Calculate Produce monthly and year-to-date expenditure reports for all funds; criteria will include fund codes. Report output should include fund name, fund code, total amount expended during specified timeframe; sort by fund.  
49 Inventory List titles purchased; criteria will specify fund(s), selector, and timeframe. Report output should include title, call number, location, country of publication, and amount; sort on call number.  
  ILL/Document Delivery Reports    
50 Count and Inventory Report journal titles which have exceeded copyright limits. Report output should include title, number of requests by publication year, number of copyright fees already paid; sort on title/publication year.  
51 Count Produce monthly and semi-annual reports of the number of requests by status, e.g., filled, request pending, unfilled; located in-house, etc. Report output should include totals for each status.  
52 Calculate Calculate fill rate and turnaround time for loans and copies; criteria will specify type of borrowing or lending and type of transaction. Report output should include type of transaction, fill rate (percentage), average turnaround time for vendor, and average internal turnaround time.  
Number Criteria Names Criteria Descriptions Rating
1 Record integration Records are fully integrated and the existence of related records is indicated in staff mode. Examples: If a title has an order record, a bibliographic record, a USMARC holdings record and an item record all records can be accessed from all staff modules; Circulation information about an item is available to staff from all modules; In Cataloging staff should be able to see that orders for other copies are outstanding; In Acquisitions, when placing an order or receiving an approval title, staff should be able to immediately determine if a copy is already on-order, received or cataloged. Important
2 Ease of navigation in staff modules Can move between all staff functions easily. Staff clients, if used, are fully integrated. When processing material, the material does not need to be searched again in each module but instead is carried from module to module. Important
3 Ease of navigation from public to staff modules Can move easily between public and staff views. Do not have to repeat a search to see records in both views. Describe how a record is 'carried' from public to staff view and from staff to public view, Important
4 Ease of completing repetitive, high transaction tasks. In all modules, can quickly update large numbers of records with like information (e.g., bulk field updates in cataloging, bulk renewals in circulation, bulk reserve activation, bulk transfer of materials to the library shelving facility). Give examples of productivity functions for repetitive, high transaction tasks. Important
5 All search modes available to public are also available to staff   Important
6 Search history Ability to display, revise and re-execute searches from staff modules. Desirable
7 Ability to limit and re-sort search results in staff mode   Important
8 Ability to locally define indexes Ability to locally define indexes. Which records and what fields are available to local index definition? For Marc records to what level of granularity can indexes be defined (e.g., can they be built from subfields only (7xx $t). Is this available at the server level and/or at the workstation level? Important
9 Security Ability to control who can work with which records by logon, workstation, or department/library. Supervisor override is essential. No use of social security number in screen displays, passwords, printed receipts or other system functions. Logins should not use social security number (which is also the university ID) in any module. Essential
10 Ability to set up multiple workflows and preferences, and save them   Important
11 System alerts System gives alerts when it's reaching a space limit such as end-of-field. Important
12 Constant-data/templates for record creation Allow configurable templates for input of new records. At what level are these stored (server or workstation)? Is there a limit on how many templates can be created? List records for which templates are not used. Essential
13 Ability to back out of or undo processes Ability to back out and/or delete when processing. Is there an 'undo' option for record updates? Which records have this option? Important
14 Saving records to workfiles Can records be saved to workfiles for later processing? If so, which records? Desirable
15 Word processing editing capabilities In all modules, for all records, can use word processing editing capabilities such as copy, cut, paste, font changes, etc. Important
16 Duplicate record checking Duplicate checking is available for which records? What criteria are used to determine that records are duplicates? Is duplicate checking optional? Important
17 Value lists for fields When value lists (lists of valid entries) are used in records (e.g., all location codes, bibliographic record fixed field values), ability to see all possible values, ability to re-order values, and ability to enter value in file directly without invoking drop-down list. Important
18 Help, error messages and status messages Help screens, error and status messages are readily changeable by library staff. Important
19 Record history Maintain a history of record updates. Identify which records include a modification history and what information about the modification is retained. Important
20 Physical and logical deletion Allows both logical and true physical deletion of records and real-time de-indexing of deleted records. Identify records that cannot be both physically and logically deleted. Important
21 Record locking Describe record locking and unlocking during update Important
  Systems & Standards    
22 Electronic Data Exchange (EDI) Ability to exchange acquisitions information in electronic form according to the latest standards (ANSI X12, UN/EDIFACT, BISAC, SISAC) using industry implementation guides. This includes our ability to send orders and claims to vendors and receive electronic acknowledgments from them; also their ability to send and our ability to receive invoices, claim responses, dispatch data, and reports electronically. Important
23 Ability to check in serial issues using SICI barcodes   Important
24 Interfaces with University's Oracle-based financial database Invoices get paid once on both systems; you only have to enter vendor & other information in one system & it updates both Desirable
25 Interfaces with LARS binding system Communicates with commercial binding management software Desirable
26 How many pay statements can there be in an invoice?   Important
27 How many funds can be used to pay a single invoice?   Important
28 How many order records can be associated with a title?   Important
29 How many characters are in a fund code?   Important
30 Can order, pay, and claim electronically & record these activities in system for non-EDI compliant vendors. For non-EDI standards compliant vendors, what capabilities exist for ordering, claiming and paying electronically and recording these activities in the system (as with, for example, the NOTIS VITLS program). Important
31 System validates fund and vendor codes Blocks the use of inappropriate (e.g., belonging to another library) or non-existent codes; a person with high level security clearance could manually override existing codes (but not non-existent ones) Important
32 Detects duplicate invoices Will block invoices with same vendor & invoice no.; can manually override Important
33 Dynamic currency update   Important
34 Acquisitions records are searchable by all data fields; system allows Boolean searching Searchable fields should include selector, operator id, create date, vendor, vendor invoice no., donor, order status, order type, fund, price, format, etc. Important
35 Note field length How long are note fields in the order and vendor records? Important
36 Record lengths What are the limits of record length for order, payment and checkin records? Important
37 Can relink order records Can relink the order record from one bibliographic record to another in the case of a serial title change Important
38 Claiming occurs automatically (unless you stop it) Feature can be disabled at the record level; you should also be able to initiate claims manually Important
39 Ability to do vendor evaluation Can compute average length of time vendor takes to fill an order, etc. Desirable
40 Ability to show discount for an individual item   Desirable
41 Default exists to set currency for each vendor   Desirable
42 Can change vendor or fund information after an invoice has been approved Describe steps. Important
43 Vendor address Vendor record accommodates multiple addresses (e.g., different addresses for ordering, claiming, payment and returns). How long is the address field? Important
44 Deposit accounts Describe acquisition deposit account functions. Important
45 Non-standard acquisitions How are non-standard acquisitions supported? E.G., materials received on memberships, gifts, exchanges, samples. Important
46 Can change predictive patterns easily Can override system when predictive patterns are inappropriate Essential
47 Multiple publication patterns Can have more than one publication pattern per record Important
48 Can sort series by volume number   Important
49 System generates pattern predictions From information in the bibliographic record; staff do not have to enter patterns from scratch Important
50 Database of publication patterns Availability of a database of publication patterns for loading during conversion (Note: Yale does not use NOTIS serials module) Desirable
51 Can relink serial patterns to new order record or bib record for title changes Important
52 Automatic claiming when issue is skipped in check-in i.e. when there's a gap in checking in issues, claiming happens automatically Important
53 Serials check-in automatically generates USMARC holdings record   Important
54 Language code generates crib sheet For enumeration terms in that language (e.g., vol., issue, part, etc.) Desirable
55 Ability to link to individual electronic journal issues with a URL in the check-in record   Desirable
  Record Exchange    
56 Load bibliographic, holdings and authority records in batch (i.e., bulk loads) as new and overlay records. Ability to execute loads of large numbers (10,000 - 500,000) of MARC21 bibliographic and authority records and USMARC holdings records without interrupting system use or slowing response time. Records may come from any source (e.g., OCLC, RLIN, OCLC MARS, MARCIVE, vendor files, etc). Ability to load RLINMARC and OCLCMARC records. Essential
57 Field changes during bulk loads Support the ability to add/delete/modify/protect/customize fields during bulk loads of bibliographic, holdings and authority records. Examples: when loading authority records, retain 090 fields within overlaid records; for loads of vendor records for e-journals, construct 856 tags. Important
58 Batch load record validation Perform validation on batch loaded records, but allow records that fail validation to enter the database. Produce a report of the records that fail validation. Important
59 Export MARC21 bibliographic records with USMARC holdings, or authority records Ability to export bibliographic, holdings and authority records to RLIN, OCLC, OCLC MARS, or other MARC databases. Essential
60 Load bibliographic field-level updates Ability to load field-level updates to bibliographic records rather than full-record replacements. For example, load a new 650 to replace an obsolete 650 or load Table-of-Contents fields. Important
61 Real-time load of authority and bibliographic records Ability to download authority and bibliographic records from MARC database (e.g., RLIN or OCLC) and load in real time. Essential
62 Extract and reload full bibliographic records Ability to extract bibliographic records, send to vendor for processing, and reload processed records. (For authority control or TOC processing) Essential
63 Shelf-ready materials Ability to batch load or real-time import all records (bibliographic, holdings, item, order, etc.) associated with shelf-ready materials. Desirable
64 Access to LC's catalog of bibliographic and authority records Ability to use LC authority and bibliographic records and to derive or copy them Essential
65 Z39.50 compliant Support a Z39.50-compliant technical services client, including the ability to search and import bibliographic records Essential
66 What are the bibliographic, holdings and authority record overlay rules? Can you target a particular record, even if the standard numbers don't match? Ability to specify the bibliographic or authority record that is to be overlaid upon record import Important
67 Limits on record length, field length and subfield length Limits on record length, field length and subfield length are consistent with those defined by MARC21. Identify any limits that exist that are not consistent with the MARC standard. Important
68 ALA Character set Ability to import, export, store, retrieve, edit and display records that use the ALA extended character set. Essential
69 Unicode Ability to import, export, store, retrieve, edit and display records that use the Unicode character sets. Important
70 Full-screen text editor Ability to enter a complete bibliographic record from a blank screen Important
71 Order of tags Ability to re-order tags. Important
72 Field validation in bibliographic records Performs bibliographic verification against the MARC21 tables upon input. Can validation table be modified? Important
73 Macros Ability to create true macros as well as "quick keys" (i.e. keystroke capture). At what level are these stored (server or workstation)? Are they retained from one release to the next? Important
74 Entering diacritics Availability of multiple methods of diacritic entry including ability to locally define keyboard mapping for frequently used diacritics and graphic tables by language for infrequently used diacritics. Important
75 Related records linking fields Possible to use linking fields (76x-78x) to create a logical link between related records, and to display links in public view. Important
76 Shelflisting Ability to automatically shelflist from the bibliographic record 050, 090, 086, e.g., select call number field in bibliographic record and system will retrieve a browse index with an indication of where the selected data would be. Note: Yale uses multiple call numbers, including LC, Old Yale, SuDoc. Desirable
77 Shelflist Call number searching in staff mode must include ability to limit by classification scheme and location. Important
  Authority Control    
78 Global change Ability to perform global change reliably and with a minimum of quality control required. Ability to change tags, indicators, subfield codes, headings, subdivisions and strings of characters globally. Essential
79 Global change ability for non-heading fields Ability to execute global change for non-authority controlled headings and fields. Important
80 No blind references. If there are no headings under a reference, do not display the reference in the OPAC. This must be accomplished without manual interventions (i.e., editing the authority record). Essential
81 Heading verification Support real-time validation and verification of headings used in record creation or modification Important
82 Automatic creation of authority records Support automatic creation of individual authority records using data from the bibliographic record according to pre-configured rules. Important
83 Multiple thesauri Describe how multiple thesauri with conflicts (e.g., LCSH and MESH) are handled and displayed. Desirable
  Item Records    
84 One to many relationships with item records Ability to link one record to multiple bibliographic records (resolving bound-with problems) Essential
85 Relink item records Ability to relink item records from one bibliographic record to another or one copy to another Essential
86 Barcodes Support Codebar modulus 10 barcodes. Is check-digit calculation executed upon barcode entry? Is check-digit used in circulation? Important
87 Spine labels Support the automatic printing of spine labels. Describe formatting options. Essential
  Record Exchange - Circulation    
88 Import of patron data Ability to customize patron loaders to import data from University Oracle-based files. Important
89 Export of patron data Ability to customize patron export by specifying format and content of exported file. Desirable
90 Dynamic patron record update Dynamic update of patron address info from the University Oracle-based personnel files; ability to submit updates to same files. Desirable
91 Import/Export fine information Ability to dynamically send fines to Bursar (Oracle-based financial system) and receive payment updates Important
92 Library Shelving Facility requests Ability to initiate a request for material with a Library Shelving Facility Location and have that request transferred automatically in real-time to the Library Shelving Facility locator system. Desirable
  Patron Records    
93 Create patron records Ability to manually create and update patron records with field validation and ID duplication check. Support multiple patron "barcode" ( i.e., patron id) formats including social security number + 1 digit (043-12-5678-1) and alpha-numeric ID's (vis 00 0007 5, MIS 00 0000 4). Essential
94 Keyword Boolean searching in patron database Ability to perform keyword Boolean searches on data from patron record, e.g., last name and phone number. Desirable
95 Multiple ID's Ability to have multiple check-out ID's attached to or associated with a patron (i.e. proxies). Important
96 Notices for multiple ID's The library may chose to send notices to either or both the “main” and the proxy borrower(s). Important
97 Multiple ID's - update Ability to do batch updates of renewals or due dates for primary and all proxy ID's. Essential
98 Multiple ID's - display all information Display all items attached to patron, regardless of ID status (e.g., active, inactive, main, proxy). Important
99 Multiple ID's - alternate index displays Provide index display options to see all ID's, only active, only inactive, only proxy, etc. Desirable
100 ID changes If ID is changed, all transactions and financial information from old ID must be accessible from new ID (by transferring them to the new ID or other means). Retain and index old ID. Important
101 Staff-initiated ID changes Ability to manually record new ID's and deactivate lost ID's Essential
102 Normalize patron names in searching Normalize hyphens, spaces, irregular capitalization in patron searches Important
103 Patron self-initiated Status View Patron can independently access status of items checked-out, items requested, items recalled, items overdue, and bill & fine information via web or telephone. How is status under proxy ID identified in patron self-initiated Status View? Does this function include the ability to see paid bills and fines? Important
104 Patron self-initiated Authentication/Security Password-protected access to patron information that is not based on social security number (University ID); no use of social security information in display screens, printed receipts, notices, etc. is essential Essential
105 Patron self-initiated One-stop Shopping A patron request is issued for material; the system determines the action necessary to obtain it - page, ILL request, hold, recall, etc., and prompts patron for appropriate information to complete transaction. Desirable
106 Is there a limit to the number of transactions a patron can have?   Important
107 Addresses Patron records may have multiple addresses including multiple email addresses. Staff may define priority for use of multiple addresses. More than one email address may be active. Individual addresses may be protected from record overlay. Important
108 Permanent retention of patron and circulation information Ability to permanently retain patron information and all related circulation transactions for patrons using materials from specified libraries. For example, retain a permanent record of all transactions that occurred involving rare book library materials. Desirable
  Financial Information    
109 Deposit accounts Ability for staff to establish reader deposit accounts for fine and service payments. Important
110 Reader initiated deposit accounts Ability for readers to establish and fund their own deposit accounts (e.g., with a credit card number) for fine and service payments (e.g., printing charges, document delivery/ILL charges). Is reader notified of deposit account activity? How? Desirable
111 Online access to archived financial information Access archival financial information in real time Important
112 Bulk update of fines Ability to pay, forgive, or credit all, or a selected number of fines for a patron. Ability to select fines associated with single library Essential
113 Payment type Payment type is identified, e.g., cash, credit card, deposit account, transfer to bursar. Important
114 After-billing collection Ability to automatically generate follow-up communication with readers (e.g., collection letters/email) on a library defined schedule for library-specified categories of readers for material that is billed but not returned. Desirable
  Item records    
115 Create circulation records on the fly Ability to create unlinked item or temporary item records from within circulation in order to check-out records that are not fully cataloged. Are these records indexed and displayed in the OPAC? What kind of information is generated for notices and on reports for these items? Essential
116 Attach item record to bibliographic record Ability to attach an item record to a bibliographic record within circulation Essential
117 Relink item records Can easily re-link item records (move item from one record to another with a min. of steps). Important
118 Circulation history recorded within the item record Record in the item record the last two patrons who checked out the item Important
119 Circulation history The complete circulation history should be accessible in real time Important
120 Route Item records Ability to 'flag' or 'route' a book for review by staff without placing a hold on it. A one-keystroke system is preferred Important
121 Serial and multi-volume sets Ability to view summary list and see checked out volumes (in vol# order) from staff mode Essential
122 Locally-defined item codes Ability to locally define codes describing the item such as missing, lost, at the bindery, etc. Essential
123 Automatic action dates Ability to set action date after which unfulfilled pages, recalls, etc. generate a specific action (e.g. send messages to staff, generate email to staff). Important
  ILL Services    
124 ILL Services - ISO 10160 / IPIG profile ILL modules must conform to ISO 10160 standards, with conformance to the IPIG Profile for the ISO ILL Protocol (this protocol is used by RLG and OCLC) Essential
125 Interface with ILL management software provided by third-party vendors Such as ILLIAD and CLIO. Provide list of all working interfaces. Desirable
126 ILL Services - Z39.63-1989 Support Z39.63-1989 to facilitate ILL communication Important
127 Patron initiated requests Allows patron initiated ILL requests from the OPAC, journal citation databases and databases searched using Z39.50. Important
128 Personal profiles Ability for patron to retain personal profile information through all requests submitted during a particular session. Important
129 Renewal Ability for patron to review pending and received ILL requests. Important
130 Tracking The system maintains and tracks history of request from point of submission through return of material. Important
131 Electronic inventory Ability to go to the shelf with a hand-held barcode scanners and collect inventory information. Supports loading of inventory information into system for comparison against database and transaction file to identify missing and misshelved items. What reports are generated from inventory system? Important
  Reserve records    
132 Faculty notification Course list electronically emailed to Faculty before each semester Important
133 Faculty generated reserve lists Ability for faculty to create a reserve list in the OPAC and automatically deliver it to library staff. Does faculty generated reserve list create reserve transaction? Can faculty cancel reserve requests electronically? Desirable
134 Staff-mode reserve indexes What search options are available for reserve materials in staff mode? Essential
135 Activation and deactivation of reserve records Ability to batch activate and deactivate course reserve list set to start and end dates. Essential
136 Rush recalls Ability to generate bulk Rush Recalls for all materials needed for reserve a library-specified number of days before course activation. Essential
137 Automatic purging of Res. Records Ability to automatically purge course reserves that have been inactive for a locally-designated period of time and the ability to manually delete a course reserve list. Important
138 Electronic Reserves Ability to store digital version of reserve item, along with copyright and use/fee information and point to digital version from an OPAC reserve list Important
139 Patron authentication Ability to associate students with specific classes for electronic reserves copyright purposes Important
140 Multiple items and lists Ability to have one course reserve list for multiple faculty; ability to have one item on multiple course lists. Desirable
  Media Booking records    
141 Equipment and Seminar Room Ability to schedule equipment and seminar rooms on a calendar schedule Desirable
142 Access to archival media booking info Ability to access archival booking schedule - online, through reports, etc. Desirable
  Circulation Functions    
143 Offline circulation Back-up circulation function so that items can circulate when system is down Important
144 Loan rules - item, location, patron matrix Create and maintain complex loan period structure based on item type, item location, circulation location, and patron type, including the ability to create loan periods down to the minute. Important
145 Renewal function Ability to renew all items in a list or only renew select items from a list. Ability to select all items based on specific criteria, e.g., from 'my' library. Ability to recognize and not renew certain types of item records automatically, (e.g., ILL item records) Important
146 Holds against in-process materials Ability to place a hold against in-process or on-order material (with or without an item record). Important
147 Override all system circ dates Ability to manually change dates for check-outs, check-ins, renewals, etc. Essential
148 Customizable audio and visual alerts System should provide customizable (at the workstation level) visual and audio alerts when the item being processed has an outstanding check-out, hold, recall, fine, block, or note. Important
149 Notices Ability to output notices via e-mail, phone(voice), fax, and print Important
150 Search and retrieve across metadata schema & databases (i.e. ability to communicate and integrate with MARC21 and non-MARC21 tagged data outside the LMS) - LMS can seamlessly search multiple databases that use various metadata schema, retrieve the metadata records, usefully present the results to the reader, and enable the reader to obtain and make use of the materials. Important
151 Translation and exchange across metadata schema & databases (i.e. ability to convert non-MARC21 tagged data into MARC21 within the LMS and the ability to convert MARC21 tagged data into other forms of metadata [e.g. Dublin Core in XML and HTML, TEI-header, etc.]) - LMS supports metadata schema translation and record exchange for staff in single transaction and batch process modes to allow high flexibility for re-purposing metadata in whatever form is best for a given project or need. For example: header in TEI-conformant SGML document is converted by catalog staff to MARC21 format at workstation; 1,000 MARC21 records converted by batch process to Dublin Core XML for inclusion in web-oriented database of e-resources; 50,000 VRA core records converted to MARC21 by loader program for inclusion in online catalog. Desirable
152 Catalog integrates multiple metadata schema within the catalog LMS supports multiple metadata schema internally; must include MARC21 and Dublin Core at minimum. This is a CORC-like catalog, and RDF-XML environment. LMS must also support translation and record exchange for metadata schema that are not native to the catalog. Desirable
153 Catalog supports current hyperlinking protocols LMS can understand hyperlinks embedded in metadata and parse them. (Including Hytime, MARC21 856, XLINK, LINK, HREF) Desirable
154 LMS must support open-system design for metadata LMS should openly share information with external systems needing to access core metadata - i.e. LMS cannot just export to external systems. Desirable
  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, can toggle on/off 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 (How is format defined?)  
  __ 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 are 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 For browse indexes, if there are no hits, there is an indication that "your entry would be here" in the results retrieved. What is the No Hits response for keyword searches? 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? How are they defined? 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. Describe display options for titles with multiple copies in different locations each having different call numbers and holdings. 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 long-term 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. Is notification of transaction sent to the reader? 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
109 Describe features specifically designed to support integration of non-print material (images, audio, video, etc.) Desirable
  Help Features / Messages/ Prompts  
110 There is context-sensitive presentation of help files Essential
111 There is a persistent index for all help screens Essential
112 It is possible for individual libraries within the system to design their own individualized help screens Important
113 There a context-sensitive mechanism for linking to vendor-generated or locally-generated tutorials (of an extent or purpose beyond simple help files) Desirable
114 The system gives an indication of status if response is not immediate (e.g., "Working...."), or if system is down Essential
115 Error messages are customizable by library system. And by specific libraries within system? Essential
116 The system provides a mechanism for intrusive dissemination of important library news bulletins Desirable
117 Readers are automatically notified of the status of their circulation requests (e.g., arrival of book recalled) Essential
118 Readers are automatically notified of the status of their ILL or acquisition/cataloging requests Essential
119 Readers can be automatically notified by serials module, e.g. re. arrival of new issues of a particular journal Desirable
120 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

Last Updated on 9/20/00
By Audrey Novak