Campus Publications Workflow: Overview

Create a collection record in the Library Digital Repository for the Campus Publications digital collection. Do this only once. (SCRC)

Done. Campus Publications Digital Collection

The Campus Publications Digital Collection contains titles drawn from the following list.

For each title to be digitized, a list of issues will be drawn up, indicating the Title, Date, Identification Number and Description of each issue as the first four fields of a spreadsheet. This is an example for the Cap and Gown. Each row will be used to automate the production of a .dc.xml file, as follows:

<metadata>
 <title>Cap and Gown</title>
 <date>1895</date>
 <identifier>mvol-0001-0001-0000</identifier>
 <description>The student yearbook of the University of Chicago.</description>
</metadata>

The .dc.xml file is named after the identifier in the row. In this example, it is mvol-0001-0001-0000.dc.xml (the value of the identifier element plus the string "dc.xml").

The list of issues will be used to digitize the complete run of the title as specified in the list. The list of issues will also be used to check that the title is complete before it is transferred to the Library Digital Repository (LDR). The directory for each issue will contain a .dc.xml file as described above which will be produced automatically before the title is accessioned into the LDR as part of processes internal to LDR workflows, i.e., not as part of Preservation Department workflows.

The list of issues should indicate which issues (if any) are missing in a fifth, Notes field. This field can also be used to indicate if an issue is embargoed (not available for public viewing).

For each issue, a list of page objects will be constructed. These instructions have been documented here. This file is named using the identifier of the issue plus the string ".struct.txt". In the example we have been using, it would be mvol-0001-0001-0000.struct.txt.

Note: If digitized before 2015, this file would have been named mvol-0001-0001-0000.txt. However, from 2015, a file so named contains raw OCR for an issue, not structural metadata.

The list of page objects will be used to ensure the completeness of an issue.

Issues of Campus Publications digitized before January 2016 and already in the LDR will be identified and checked for completeness and accuracy according to the following protocol; .dc.xml files will be produced from the list of issues as part of internal LDR processing. Issues of Campus Publications digitized from January 2016 will be checked for completeness and accuracy, and .dc.xml files produced as above before accessioning into the LDR.

Note: From January 2016 on, issues will be accessioned only after a complete run of issues for a title has been assembled, using the list of issues described above to gauge the completeness of a run.