Content Management

Revision as of 14:22, 25 March 2016

In general, digitized content is:

1. created in Digital Services,
2. temporarily stored on the Share drive (a Windows server) for:
   1. optimization,
   2. quality control verification and
   3. batch completion,
3. and then uploaded to the libcontent server in two forms:
   1. derivatives, for web delivery, and
   2. the archival files, for archiving.

Thus, it makes sense to divide our documentation by what happens on the Share drive, what happens on the Linux Server (Server-Side Work), and the workflow that ties them together:

1. Share_Drive_Protocols
2. Workflow
3. Server-Side Work

Some work, however, crosses boundaries. We test our content for validity and well-formedness during the quality control process, prior to uploads. The information generated via this testing is used in creating our standardized preservation metadata, some of which is then stored in a database for easy search and retrieval.

Once in the archive, content needs to be managed for long-term access.

This includes:

1. tracking and monitoring different formats so we know where to find content in need of migration
2. tracking what is in LOCKSS and when it was added, and pushing for complete content in LOCKSS
3. checksum verifications weekly
4. extraction and storing of appropriate technical metadata, including some in the database for easy access
   1. Image_Technical_Metadata
   2. Audio_Technical_Metadata
5. documenting anomalies that will need to be managed long-term
6. ensuring we have adequate and viable backups
7. updating metadata, transcripts, and tags
8. documenting the storage system, content and structure, including software needed for access and reconstruction
9. preservation planning
10. business continuity planning
11. disaster recovery preparation

For information on incoming digital content, see Born_Digital.