Summary of OCLC Compliance with ICOLC

Summary of OCLC Compliance

with ICOLC Guidelines

ICOLC REQUIREMENTS	OCLC COMPLIANCE YES	OCLC COMPLIANCE NO
Each use element defined below should be able to be delineated by the following subdivisions: By each specific database of the provider	X
By each institutionally-defined set of IP addresses/locators to subnet level		X
By total consortium	X
By special data element passed by subscriber( e.g., account or ID number)	X
By time period. Vendor’s system should minimally report by month. For each month, each type of use should be reported by hour of the day, and vendor should maintain 24 months of historical data	X OCLC maintains 20 months of historical data
Use Elements that must be provided are: Number of queries (Searches) categorized as appropriate for the vendor’s information.	X
Number of Menu Selections categorized as appropriate to the vendor’s system.		X
Number of sessions (Logins), if relevant, must be provided as a measure of simultaneous use.	X
Number of turn-aways, if relevant, as a contract limit	X
Number of items examined (i.e., viewed, marked or selected, downloaded, emailed, printed) to the extent these can be recorded and controlled by the server rather than the browser:		X
Other: Citations displayed (for A&I databases)		X
Full text displayed broken down by title, ISSN with title listed, or other title identifier as appropriate		X
Tables of Contents displayed		X
Abstracts displayed		X
Articles or essays, poems, chapters, etc., as appropriate, viewed (e.g., ASCII or HTML) or downloaded (e.g. PDF, email)	X
Other (e.g., image / AV files, ads, reviews, etc., as appropriate)	X