...
| File from ETD | DRS Object Role | Relationship from THESIS object |
|---|---|---|
| Thesis PDF | THESIS | - |
| Supplementary files | THESIS_SUPPLEMENT | HAS_SUPPLEMENT |
| License files | LICENSE | HAS_LICENSE (In Rights section of Thesis Object) |
| mets.xml | DOCUMENTATION | HAS_DOCUMENTATION |
DRS
...
Batches, Objects, and Content Models in BatchBuilder
BatchBuilder is the main tool used to organize content for deposit into DRS. A 'batch' is the group of files and directories that is sent to DRS for deposit. Each batch has at least one 'object' of some content model along with a descriptor file for each object that has technical, administrative, and preservation metadata for the object and any of its files. In order to be deposited, each batch also needs a file, batch.xml, that has information about all the objects in the batch. A batch can include objects of different content models, but more often than not, all the objects in a batch are all the same content model.
Preparing a batch
- Get the file information for all files from the mets.xml FileSec
- Filename
- Mime-type
- Use category - CONTENT or LICENSE
- AMDID - amd_primary, amd_supplemental, amd_license
- Create Object OSNs based on ProQuest ID, school code and Role
- Create File OSNs based on ProQuest ID and Role
- Create mapping.txt file to associate files with appropriate Object OSN and File OSN
- Get DASH URN from MARCXML if present
- Get Alma MMSID by using query with ProQuestETD ID
...