To ingest content via file transfer technology for LOCKSS network preservation, please comply with the requirements below.

Content delivery

General requirements

  • Uniquely named deliveries, including full text and supplemental materials.
  • Clear, consistent file naming convention that correlates specific metadata to full text content.
  • Full-text content in a standard readable form (e.g., PDF).
  • Delivery of duplicative content only for corrections and updates.
  • Delivery of final published content, no in-progress issues or pre-publication articles.
  • Delivery may be in an archive or in unpacked directories but delivery must be in non-proprietary formats (such as tar and zip).

Metadata requirements

General optimizations

  • Content as individual PDFs without redundant versions such as manuscript, epub, mobi.
  • Notification to the delivery alias when a delivery has occurred.
  • A listing of files delivered with updates clearly identified.
  • Deliveries in tar or zip bundles should be completely self-contained. Multiple archives should not need to be expanded to map metadata to articles.
  • Updates to previously delivered content would include just the modified items.
  • Semi-annual list of individual items sent for preservation – e.g. all the ISSNs and DOIs.

Server staging setup

  • If the publisher has a staging server, please tell us: the location and password; the update schedule; the content removal schedule.
  • If the publisher would like to send content to the LOCKSS network staging server, we will send you the location and password; please tell us your update schedule.

NOTE: do not routinely send “published before print” articles in your preservation feed.