Page Comparison

...

9.4 Depositing a thesis object

DRS supports deposit of digital theses and dissertations and associated supporting content.

The thesis object can consist of a single PDF file or multiple PDFs representing the same thesis (for example, an original PDF and a PDF/A file derived from it, an archival version and a reduced size delivery version, or the redacted and unredacted versions of a thesis). Every file with the role DELIVERABLE will be assigned a delivery URN. The deliverable files in thesis objects are delivered by the File Delivery Service (FDS). The delivery restrictions are governed by DRS access flags (P = public; R = restricted to Harvard community; N = no delivery).

The optional supporting content can consist of thesis certificates (if supplied as separate from the thesis file), thesis supplements, embargo documentation, and licenses. See more about preparing supporting content for DRS in the section "Preparing supporting content" below.

What follows are instructions on how to prepare a thesis object and supporting content for deposit.

Preparing a thesis object Preparing supporting content
Anchor_Preparing_a_thesis_Preparing_a_thesis

Preparing a thesis object
To deposit a thesis object, follow the regular manual or automatic workflow for creating a Document batch. Use these metadata values:

• Object-level Role: THESIS.
• File-level Processing value: leave blank, except for a redacted version of the thesis, which should be coded as REDACTED.
• File-level Role: assign DELIVERABLE to get a Delivery URN for the PDF file. Optionally, assign role ARCHIVAL_MASTER to the original file. If there is only one file in the thesis, then assign both roles to the file (Ctrl-Click in Batch Builder to assign multiple roles).

...

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:

1. 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.

1. Deposit supporting content and regular content in the same batch (does not apply to license and embargo objects).
   1. • 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.
   2. 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.

...