The first sections of the attached diagram which pertain to Digital Services are delineated in Preparing_Collections_on_the_S_Drive_for_Online_Delivery_and_Storage.
Here's the steps for creating derivatives and moving content off the share drive:
- Make sure content is in the Completed directory, and that all quality control scripts have been run, and all corrections made.
- Create the MODS from the exported text spreadsheet (Making_MODS), and place them in a MODS directory within the Metadata directory.
- Log onto libcontent1 and change into the UploadArea/scripts directory. (see Command-line_Work_on_Linux_Server)
- Type in 'makeJpegs' and answer the questions that arise. If errors appear on the commandline or in the output file, repair them. The output file will be located in the UploadArea/output directory, and the script will tell you its name, which is timestamped.
- The makeJpegs script will do some minor QC, including checking to see if there is a MODS for each item-level object and an object for each item-level MODS.
- If there are no problems, it will copy the MODS files to the UploadArea/MODS directory on the server, copy the transcripts to the UploadArea/transcripts directory on the server, and will generate JPEG derivatives (a thumb ending in _128.jpg and a large image ending in _2048.jpg) and place them in the UploadArea/jpegs directory on the server.
- If there were no errors and the script completed these tasks, check the results on the server in the above-named directories. If all is well, proceed to the next step.
- In the UploadArea/scripts directory, type in 'relocate_all'. This script will move all the content just uploaded into the correct directories in Acumen. If anything remains in the above-mentioned directories after the script has completed, there's a problem which must be repaired. One thing to check, if there's no errors in the output, is Server Permissions.
- Check the indexing of the uploaded content after about 24 hours to verify.
makeJpegs will be upgraded to include the creation of OCR files for either entire collection contents or item-level materials as specified in a text file containing a list of one item number per line (no file extensions).
The moveContent script will copy content to the deposits directory on the storage server, where it will be prepared for archiving at a later date.
Additionally, it will check the collection-level xml file (in the Admin directory), then add it to the online database which feeds the collection list online. Thus, this script should NOT be run for new collections until the content is indexed (as described in the previous section); otherwise, the link from the collection listing will be dead.
After making the copy, it will verify that each file copied without alteration, and then delete the copy on the share drive.
If any files remain in the directories on the share drive, they did NOT copy to the server!! Run the script again, as there may have been a failure of the copy across the network. If this fails, the file will need to be moved manually, and the problem encountered by the script must be resolved.
The section where Jody processes for the archive, and where she creates derivatives, is spelled out in Moving_Content_To_Long-Term_Storage
We have yet to determine at what point MODS (and server-side generated OCR) are ready for archiving, but that will be sorted out soon.