-
Notifications
You must be signed in to change notification settings - Fork 2
Content Staging
blalbrit edited this page Oct 16, 2018
·
12 revisions
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 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 - and each sub-folder can contain one or many files in a flat directory structure).
/{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
- Getting started
- Deposit workflow overview
- Content staging
- Using Globus to stage files
- Filling out the Preassembly web form
- Running the Discovery Report and Preassembly Jobs
- Updating existing items
- Accessioning complex content
- Accessioning images with captions
- Explanation of possible errors found by a discovery report
- What Happens After My Job Completes?
- My Job Seems to Be Taking A Really Long Time (like... days!)
- My files did not show up on the PURL as expected
- Using preassembly for self-deposited content