Current	Mandatory	Notes
1	Does the system assign a unique and searchable number to identify each transaction which stays with it from start to finish?		yes
2	Does the system retain the transaction numbers of requests forwarded from remote systems, such as OCLC, while also retaining the local unique transaction number?		yes	FCLA will add OCLC # and OCLC request # to current form.
3	Does the system include status values that manage and track the request which conform to those specified in NISO Z39.63 and the ISO ILL protocols, including date requested, supplier, date filled, date returned, etc.?		yes
4	Are the status values set automatically during item processing on individual items?		yes
5	Does the system detect duplicate requests from the same user?		yes
6	Does the system select a request destination by verifying the availability of an item at the selected destination?		yes	yes within the SUS; no for non-SUS
7	Does the system provide automatic notification to the requestor when an item is cancelled and the reason for the cancellation?		yes
8	Does the system send requests directly to the OCLC & DOCLINE?		yes
9	Does the system send the request to the holding library system or document supplier via Z39.63 over TCP/IP or using Z39.50 Extended Services Item Order?		yes	BUT OCLC doesn't accept Z39.63
10	If the system does not use the above standards and protocols, how does the system attain the described results?		N/A
11	Does the system provide the ILL staff with the ability to download in batch pending requests, sort the requests and print pull slips or lists that include bibliographic information, local call number, all lending library locations, unique system identification numbers, ship to address and other locally specified information?		yes	if OCLC supports ISO protocols for lending libs.
12	Does the system have the ability to use printed barcodes for subsequent updating of request status?		yes
13	Does the system allow online and printed reports by status of ILL request, such as: complete, received, returned, will supply, shipped, unfilled, cancelled, etc?		yes
	ILL BORROWING AND LENDING REQUIREMENTS
14	Does your system support requests for original items, document photocopies, and materials in electronic format?	yes	yes
15	Does your system provide for user notes?	yes	yes
16	Does your system allow for multiple user options?	yes	yes
17	Does your system process requests in ISO standard message format?		yes
18	Does your system collect bibliographic information from a variety of sources:
	Local catalog?	yes	yes
	Local index and abstract or full text database?	yes	yes
	External catalogs or databases?	no	yes	with Z39.50
19	Does your system provide the option for blank request templates that may be used to request items that have not been located in local or remote catalogs or databases?	see note	yes	in development as part of Phase I
20	Are locally held items readily identified for the user?	yes	yes
21	Is the user blocked from requesting locally held items from other sources?		yes
22	Is your system able to capture and/or import the following data from a remote or local catalog or database?
	Bibliographic/citation information?	yes	yes
	Location?		yes
	Call number?	yes	yes
	Date after which item is no longer needed?	yes	yes
	Availability of the item?		yes
23	Does your system recognize locations or collections which are non-circulating for returnable items?		N/A
24	Does your system allow users to search via OCLC, RLIN Z30.50 and DOCLINE ILL systems?
25	Does your system allow requests to be placed and received via OCLC, RLIN ILL or DOCLINE?
26	Does your system provide for user authentication?	yes	yes
27	Does your system require user's authorization to place a request based on locally designated criteria?	yes	yes
28	Does your system provide an option for the local library to specify how many requests can be placed by one user?		yes
29	Does your system use published standards and/or interfaces, and cache the user information to eliminate re-authentication during the current session?		yes, if possible to preserve privacy	Desireable to have options of "Submit,continue" and "Submit, last request" so that the user won't have to re-enter ID for each request in a session.
30	Does your system prompt the user to sign off once his/her requests are placed?		yes, if 29 is possible
31	Is your system capable of capturing or importing the following data from a local circulation or user ID system:
	User data?	yes	yes
	Delivery information	yes	yes
32	Does your system allow the user to cancel a request prior to sending it?	yes	yes
33	Does your system allow users to search their local catalog or databases and place local loan delivery requests between campus libraries or branch libraries?		yes
34	Does the local library have the option to turn this feature on/off at the institution's discretion?		yes
35	Does your system allow the user to specify the desired delivery mode(format)?		yes
36	Does your system allow the user to specify delivery locations?		yes
37	Does your system provide the option of requesting items from a fee-based document supplier?			library decision
38	Does your system allow the local library the option of paying for all or part of any request?			library decision
39	Does your system allow the institution to charge the user for a request?			library decision
40	Does your system support the local library setting a threshold by user or other specified method below which the transactions are at no cost and after which the user will pay?			library decision
41	Does your system allow additional user fees to be added by the institution?			library decision
42	Does your system offer the user a variety of payment options?			library decision
43	Does your system allow the user to search for his/her own outstanding requests and supply the user with the status of a request based upon the status codes?		yes
44	Does your system allow the user to cancel a request before a lending library fills the request?		yes
45	Does your system remind the user to sign out once he or she has finished searching?			IGNORE: duplicates question 30
46	Does your system include a message feature to allow borrowing and lending staff to communicate via messages on the ILL request with notification of pending messages via the status tracking file?		N/A
47	Does your system provide for multiple potential lenders on a request record and automatically forward the request from one lender to the next?		N/A
48	Does your system capture the correct call number from each successive potential lender and correlate the information to the appropriate lender in successive requests?		N/A
49	Does your system support the ability to re-initiate requests that were not supplied?		N/A
50	Does your system permit users to communicate with ILL departments electronically?		yes
51	Does your system allow e-mail connectivity to alert users automatically when requested items arrive?		yes
52	Does your system allow the patron to select a pick-up location and automatically route requests to the proper location for ordering?	yes	yes
53	Does your system comply with national and international ILL standards?		yes
54	Is your system ANSI/NISO Z39.63 compliant?			BUT OCLC doesn't accept Z39.63
55	Does your system allow for an on-screen message display?	yes	yes
56	Does your system give the patron the option of replying "yes" or "no" to copyright compliance acceptance?	yes	yes
57	Does a "No" answer provide an explanation and halt the request?	yes	yes
58	Is your system compliant with ISO Interlibrary Loan standard protocols?		yes
59	Will your system be able to import/export data from a local ILL request system?		yes	to OCLC
60	Can your ILL system be disabled if a library chooses not to use your system in favor of a local system?		yes	User can be denied at point of ID entry
61	Does your system have written documentation to support the ILL system?		yes
62	Is technical support for your system available?	yes	yes
63	Does your system allow for receipt of documents from other libraries or vendors via, but not limited to, email, fax, ARIEL, or other electronic transmission?		yes	library decision
64	Does your system allow for delivery of documents directly to patrons by electronic means?		yes	library decision
65	Does your system allow patrons to track the status of ILL requests?		yes	duplicates question 43
66	When does your system prompt the patron to exit the system so that the request may be sent?			see questions 30 & 31
67	Does your system provide user-initiated ILL or document delivery for items found in other Z39.50 compatible catalogs or databases?		no
68	Does your system provide ILL transactions for libraries without automated systems or systems that do not comply with ISO ILL protocols?		N/A
69	Does your system accept electronic ILL requests from patrons regardless of the programming language origin of the request from sources including email, OCLC and local OPAC options?		N/A
70	Does your system have the capability to interact with patron circulation records for patron validation without additional system entry functions and administrative access?	yes	yes
71	Does your system allow ILL staff to block or suspend ILL privileges based upon local protocols?		yes
72	Does your system provide access for the ILL staff to complete information in the patron database?	yes	yes	if library allows access for ILL staff by security level
73	Does your system allow for automatic ILL request tracking and status updating by lending and borrowing libraries and vendors?		yes
74	Does your system provide a unique record number with processing date and time for each ILL request processed?		yes
75	Does your system allow patrons to track the status of their ILL request?		yes
76	Does your system allow for automatic notification of received ILL materials directly to the patron's e-mail address or other electronic address?		yes
77	Does your system have the ability to archive completed ILL transactions?		yes
78	Does your system allow for local definitions of time periods during which archives are considered to be active or inactive?		yes
79	Does your system charge ILL fees and fines to the patron's circulation record?		yes
80	Does your system have the capability of blocking charges according to preset protocols?		yes
81	Does your system provide customized interlibrary loan reports?		yes
82	Does your system provide ILL reports in conjunction with or separately from the library's circulation reports?		yes	as separate report
83	Does your system provide online or printed ILL request status reports according to local specifications?		yes
84	Does your system refer requests to ILL staff that require individualized attention?	yes	yes
85	Does your system provide copyright notification to the requestor?	yes	yes
86	Does your system allow ILL staff to intercede or stop a request from further processing for review or referral?	yes	yes
87	Does your system allow for requests to be processed either mediated or unmediated by ILL staff?		yes
88	Does your system allow ILL staff to customize ILL rejections based on ILL policy, material type, or other library specifications?		yes
89	Does your system provide for the development of automatic routing of requests similar to the OCLC/Custom Holdings program and path development by which requests can be automatically forwarded to potential lending libraries in a specified order?		N/A
90	Does your system allow for the creation of a database of potential lending libraries according to local specifications?		N/A