...
| 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,
...
Content Models and Relationships between Objects 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 , descriptor.xml, that has technical, administrative, and preservation metadata for the each object and any of its files. In order to be deposited, each batch also needs an xml file, batch.xml, that has information about all the objects in the batch. A batch can include objects of different content models. BatchBuilder recreates the descriptor.xml and batch.xml files every time it processes a batch so capture any edits to the objects since the last batch generation.
It is possible to define relationships between objects, as described above, even if the objects are being deposited in the same batch. The Object Owner Supplied Name (OSN) is used to identify the object that is related.
NOTE: In order to create relationships between objects in the same batch, the object that is the SOURCE of the relationship, e.g. HAS_SUPPLEMENT, has to be deposited after the object that is the TARGET of the relationship, e.g. the object with the SUPPLEMENT role. When using the CLI version of BatchBuilder, if the objects are names so that the SOURCE object is always alphabetically after the TARGET, BatchBuilder will create a batch that will have the correct relationships when deposited into DRS.
Information needed for each object
...