Preservation Step-by-Step

• Analyze the formats and packaging of sample or supplied content
• Guided by Portico’s established preservation policies, develop a preservation plan appropriate to the supplied content and the needs of the content provider and library participants in the service. The preservation plan may include an initial migration of the packaging or files in specific formats (for example, Portico migrates publisher specific e-journal article XML to the NLM archival standard).
• Develop any new tools necessary to implement the plan – possibilities including tools to:
  • retrieve the content
  • load the content into the processing system (Figure 3: Loaders)
  • repackage the content
  • migrate files in specific formats

• Content can be manually and automatically pushed or pulled. Transfer options include:
  • portable media
  • FTP
  • OAI-PMH or OAI-ORE
  • Portico custom developed software
• Content is loaded into the Portico content storage area (Figure 9: Content Storage Area)

• Portico processes the content per the specific preservation plan and deposits it into the archive. All content processing includes:
  • Validating files against their format specifications
  • Verifying checksums
  • Extracting key technical (Figure 4: Technical Metadata) and descriptive metadata (Figure 2: Descriptive Metadata Extracted) to record in the preservation metadata
  • Capturing all actions taken on the content (Figure 11: Some Possible Events) and recording each as an event in the preservation metadata (Figure 10: Sample Events in Detail)
  • Creating a checksum for each file and recording it in the preservation metadata (Figure 12: Checksum)
  • Creating a Portico archival information package (AIP) (Figure 6: Content Model)
• E-journal and e-book content processing also include:
  • Analyzing the structure of the content to identify all the files and determine whether all files received were expected (Figure 1: Content Model Mapping)
  • Transforming descriptive metadata or structured full-text to an archival format, if needed (Figure 5: XML Transformation)
  • Migrating files in specific formats

• Regular activities:
  • Replicate content to three on-line copies and one off-line copy (Figure 15: Replicas)
  • Daily ingest fixity checks (Figure 7: Daily Fixity Check Log)
  • Twice yearly full archive fixity checks (Figure 8: Twice Yearly Fixity Check Report)
  • Repair or replace content if it becomes corrupted
  • Audit content
  • Report on the content (Figure 13: Snippet from Annual Publisher Report)
  • Refresh hardware
  • Monitor the preservation and academic community for changes in preservation needs
• Annual or as needed activities:
  • Validate or revalidate files as new tools are developed
  • Migrate files to new formats as necessitated by the changing technological environment
  • Update preservation plans
  • Receive preservation accreditation

Campus-wide access (Figure 14: Access) to preserved content is granted to libraries supporting Portico when specific conditions are met that cause titles to no longer be available from the publisher or any other source. These specific conditions are often called trigger events and include:

• A publisher stops operations
• A publisher ceases to publish a title
• A publisher no longer offers back issues
• Catastrophic and sustained failure of a publisher’s delivery platform.

Access is also available to fulfill post cancellation access claims when allowed by the publisher.