Campus Publications Workflow: Detail

1. Preservation creates a file structure in their own working disk space
2. Preservation decides some unit of file structure is correctly formatted and "done"
3. Preservation transfers the file structure into the validation environment
4. The validation environment begins creating reports on the status of the file structure
5. Preservation evaluates the contents of reports
   • If reports are clean continue.
   • If reports are not clean, and
   • if required changes are small (e.g., moving/renaming files) they are performed in the validation environment.
   • If required charges are large (file creation, large overhauls) they are performed in preservations working space, the results are recopied into the validation environment.
   • Return to 5.
6. Preservation alerts the DAS to the presence of a validated working unit

In the event automation of a fix may be required, the repository managers are contacted, an automated fix is evaluated and potentially implemented.

1. DAS evaluates contents of records
2. If necessary DAS performs any "cleanups" (e.g., removing superfluous files not appropriate for pruning)
3. DAS stages contents into the staging directory
4. DAS confirms staged files are backed up
5. DAS removes files from validation environment and alerts preservation
6. DAS performs one of two actions:
   • holds submitted unit in staging until a title is complete
   • accessions the staged unit
7. Once sign-offs have been procured, DAS alerts the DLDC that a title has been accessioned

1. DLDC generates SIPs for the new title (see Specifications for Processing deposits from 2015)
2. DLDC generates DIPs from the SIPs
3. DLDC uses the DIPs to add the new title to the test interface
4. After the stakeholders sign off, DLDC adds the new title to the production site
5. DLDC informs cataloging of the persistent URL for the new title (see 909 Registry).