Contents |
[edit] Overview
Publishers who wish to participate in the LOCKSS Program need to make their titles LOCKSS compliant. To do this,
- We *suggest* publishers give permission in their license agreements with libraries to collect, preserve, and provide access
- It is *required* for publishers to give permission on their website for the LOCKSS software to crawl, to collect, and to preserve the content.
[edit] Permission to Librarians
Publishers must give librarians permission to collect, preserve, and provide access to their content. The language suggested below is for publishers to add to their institutional terms and conditions statements or site licenses. This permission is granted to all libraries (exceptional circumstances not withstanding) and is not negotiated institution by institution. This suggested license language permits libraries to:
- Collect and preserve currently accessible materials;
- Use material consistent with original license terms;
- Provide copies to other appliances for purposes of audit and repair.
[edit] Suggested License Language for Subscription Materials
"Publisher acknowledges that Licensee participates in the LOCKSS system for archiving digitized publications. Licensee may perpetually use the LOCKSS system to archive and restore the Licensed Materials, so long as Licensee's use is otherwise consistent with this Agreement. Publisher further acknowledges and agrees that, for the purpose of repairing damage to or loss of another LOCKSS system's copy of Licensed Materials, Licensee's LOCKSS system may make Licensed Materials available to that other LOCKSS system provided that the other LOCKSS system had previously proven to Licensee's system that it had the same Licensed Materials."
[edit] For Freely Available Materials
"Publisher perpetually authorizes LOCKSS members to archive and restore [our publication] through the LOCKSS system."
[edit] Permission to the LOCKSS Software
Permission is granted to the LOCKSS software through a web page called a LOCKSS publisher manifest (example). A publisher manifest permits the software to crawl, collect, and preserve the content. It also lists the top level URLs so the crawler knows where to start the collection process. A publisher manifest is needed for each Archival Unit to be preserved through the LOCKSS system. For subscription content, an Archival Unit is often defined as a volume. For freely available content, an Archival Unit is often the entire title. Putting Up a Manifest Page
[edit] Online License Language
The LOCKSS system requires the manifest page contain either a suitable Creative Commons license, or, one of the following texts:
LOCKSS system has permission to collect, preserve, and serve this Archival Unit.
LOCKSS system has permission to collect, preserve, and serve this open access Archival Unit.
[edit] Suggested LOCKSS Branding
We encourage you to add the LOCKSS logo and statement below to your web site. This lets your customers know that your content is already LOCKSS-compliant and available to be collected and preserved by authorized subscribers.
"The LOCKSS system preserves [publisher name here] at research libraries worldwide."
[edit] Statistics
The COUNTER Code of Practice, Journals and Databases: Release 3, Published August 2008, page 34 says, " Activity generated by LOCKSS or a similar cache system during the process of loading, refreshing, or otherwise maintaining the cache must be excluded from all COUNTER reports. from user statistics reported to libraries."
Your site will see requests from LOCKSS boxes in two situations: when it collects content to preserve, and whenever a user requests a page.
Requests that have a "user-agent" header with the value "LOCKSS cache" are part of the collection process and may be excluded from your usage statistics. These will occur in clusters, whenever any LOCKSS box crawls for new content, which they each do at approximately 2 week intervals. They may also occur sporadically at other times, to repair missing or damaged content.
Requests (from LOCKSS boxes) that do not include this user-agent header mean that a user, proxying through the LOCKSS box, has requested that page. These requests will contain a Via header (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) identifying the particular LOCKSS box. LOCKSS always forwards such requests on to the publisher so that you can count them. If the LOCKSS box has the content (because it has previously collected it), it adds an if-modified-since header to the request, and if your server returns a 304 (Not Modified) response (or does not respond within a short time) it will serve that content to the user. If your site returns content, that content will always be served to the user.
