Tiered Ingest allows you to group all of the files corresponding to an a simple asset's datastreams (including archival files, publication files, other derivatives created outside of Islandora, with the exception of RELS-EXT) into a sub-directory.Use Case: As a DAMS user, I need to ingest a set of digital objects (including archival files, publication files, other derivatives created outside of Islandora) as one Fedora asset with multiple datastreams so that my workflow is streamlined and related objects are stored together in one place
| Note |
|---|
This tiered batch ingest method is NOT suitable for paged content (complex/compound assets with children). See Batch ingest complex assets (paged content) for instructions on how to ingest assets comprised of multiple pages. The tiered ingest allows you to store additional files with a digital asset, and you can use this method to ingest externally created derivative datastreams (e.g. for streaming audio). See Content models for a breakdown of the expected datastreams per content model, and for information which datastreams can be published to e.g. the Collections Portal. |
| Multiexcerpt include | ||||
|---|---|---|---|---|
|
...
| Multiexcerpt include | ||||
|---|---|---|---|---|
|
The tiered ingest batch module uses filenames to identify the files that correspond to specific datastreams. All of the files you are ingesting as part of one asset should go will be staged in one directory per asset, as a sub-directory of the batch job folder.
path you identify in the queue form. Each sub-directory corresponds to one asset and must have at least a file for the "key datastreams" (datastreams.txt). This file will list the datastream ID and corresponding filename, for instance the MODS datastream (MODS.xml), OBJ datastream (ex: filename.tif for large image), or other datastreams with derivatives.
...
...
Sample folder structure
...
| Code Block |
|---|
eid1234_example-batch-submission/ (batch job folder)
├── asset1/
│ ├── datastreams.txt
│ ├── modsfile.xml
│ ├── primaryfile.tif
│ ├── anyarbitraryderivativefile.ext
│ ├── anyarbitrarycomponentfile.ext
│ └── anymediaphotographfile.ext
├── asset2_audio_example/
│ ├── datastreams.txt
│ ├── modsfile.xml
│ ├── audiofile.wav
│ ├── derivative_audiofile_for_streaming.mp4 (e.g. for creating PROXY_MP4 datastream, which is required for streaming audio)
│ └── audio_transcript.txt
└── asset3_video_example/
├── datastreams.txt
├── modsfile.xml
├── videofile.mp4
├── video_captions.vtt
└── video_transcript.txt
└── page02_custom_ocr.txt |
Notes:
- set1 & set2 Folders for asset1, asset2, asset3 as shown above would be are nested under the batch directory and each set . Each subfolder represents an individual asset with its datastreams.
- The batch job folder can be contain just one set asset folder, but would still need the extra nestingthere is no upper limit on number of sets/objects or filesize