Content Staging

Staging Content

• Content that is going to be staged with this application needs to be made available on storage mount to which the accessioning system has access. The full list of storage mounts for accessioning can be found on Consul at: content mount paths.

• There is only one supported method for staging of content on these storage mounts, and all projects (regardless of whether they are image, book, or media projects) should follow this pattern: /{stagingMount}/{projectFolder}/{content}/

• And within each content folder, every object should have its own sub-folder (in the example below, these are named by druid, but that is not required - and each sub-folder can contain one or many files in a flat directory structure). Files should be named in alpha sort order for the sequence in which they are expected to be delivered.

/{stagingMount}/{projectFolder}/{content}/
├── jh486mk1405
│   └── ErbWE.tif
├── manifest.csv
├── mw438sy2326
│   └── AkremiF.tif
├── sv928qy8859
│   └── BerrySmithJ.tif
├── vb063xr4527
│   └── RoachJM.tif
├── vz805mb3344
│   └── ShillinglawDT.tif
├── ww805gw8199
│   └── RobertsCE.tif
└── yg789dz9935
    └── RobertsCET.tif

• To prepare content from the command line on the mounted drive, create two files in the folder that contains the content folder, either by uploading them or by using a command-line text editor such as nano. The first file should be called druids.txt and contain a list of the druids being prepared, one per line. The second should be called filenames.txt and contain one druid-filename pair per line, separated by a tab.

  • To create the sub-folders: while read druid; do mkdir content/"$druid"; done <druids.txt

  • To move the files from the content directory into the corresponding druid directories, substitute the file path to the folder containing the files in the following: while read druid filename; do mv /{stagingMount}/{projectFolder}/{fileFolder}/"$filename" content/"$druid"; done <filenames.txt