...
Preparing supporting content
A thesis object may be accompanied by any of the following supporting content: thesis certificate, thesis supplement, embargo documentation, license documentation.
Supporting content must be deposited to DRS and associated with the thesis object through relationship and/or rights metadata. There are three options for depositing supporting content:
- Deposit supporting content to DRS first, in a separate batch (applies to all supporting content, including license and embargo objects).
After supporting content is deposited, the supporting Object URN can be used to link it to the regular content. Use the corresponding relationships fields in Batch Builder to link regular objects to supporting content when creating a regular content batch. - Deposit supporting content and regular content in the same batch (does not apply to license and embargo objects).
In this case, Object Name rather than Object URN is used for linking. When placing supporting content and regular content in the same batch, make sure that the supporting objects are named in such a way that the Object Name of the supporting object (the target of the relationships) occurs alphabetically before the Object Name of the regular content object (the source of the relationship). This is needed because in order for the relationship to be created correctly, the supporting object needs to be ingested into DRS before the regular object. - Deposit supporting content after regular content (applies to all supporting content, including license and embargo objects).
If depositing supported content after the regular content objects have been deposited to DRS, the relationships between the supporting content objects and regular content objects will need to be created in DRS Web Admin after both types of objects have been deposited. This option is not currently recommended for large volume workflows.
See the procedure for depositing supporting content in Section 19 "Adding Licenses, Documentation and Other Supporting Content."
...