Overview

DRS2 lets you associate descriptive metadata with deposited objects. These descriptions are stored in the object descriptor. Adding descriptive metadata can be done at the point of deposit using Batch Builder or after the object is deposited using Web Admin. This section describes options available in Web Admin.

Use options on an object's Descriptive metadata tab to edit descriptive information about the object. A user with the metadata_editor role can perform the following actions:

• Upload MODS descriptive metadata: by supplying an external MODS xml file or by importing descriptions from Aleph.
• Add a METS label: by using MODS data or by adding custom text.
• Reference related metadata: by adding Harvard Metadata or Related Links. (These fields were previously displayed on the Admin Metadata tab.)

Uploading MODS

Uploading MODS by importing from Aleph or by uploading an external MODS file will replace any MODS descriptions already in place. Uploading MODS will also replace the MODS-generated label but will not change the existing METS label.

Note: DRS2 accepts files up to MODS version 3.45. MODS versions higher than 3.45 will be rejected. The MODS version delivered by Aleph import and the PRESTO service will always be acceptable.

Uploading MODS by Aleph ID

1. Obtain the Aleph record ID number.
2. Display the object's metadata summary and select the Descriptive metadata tab.
3. Open the Replace MODS pane by clicking the arrow.
4. Enter the ID in the Upload MODS by Aleph ID field.
5. Click the Replace MODS button to import the MODS and save this change. You may need to click once anywhere on the form to activate the Replace button.
6. The new MODS is imported at this point. There may be a few minutes delay before the MODS display is refreshed with new data.

Uploading an external MODS file

Descriptive metadata for an object can be imported from a locally-supplied MODS file. This section describes how to extract MODS from HOLLIS or VIA using the PRESTO service and how to create a MODS file from scratch using a template.

To import an external MODS file:

1. Create the MODS file and save it to a convenient location on your file system.
2. Display the object's metadata summary and select the Descriptive metadata tab.
3. Open the Replace MODS pane by clicking the arrow.
4. Under Upload MODS File, click the Choose file button.
5. Navigate to the MODS file on your file system and select it.
6. Click the Replace MODS button to import the MODS and save this change. You may need to click once anywhere on the form to activate the Replace button.

The new MODS file is imported at this point. There may be a few minutes delay before the MODS display is refreshed with new data.

Using PRESTO to extract MODS from HOLLIS or VIA: 

If there is cataloging for an object in HOLLIS or VIA, you can use the Harvard Library PRESTO service to extract a MODS version of the record.

1. Identify the ID of the record you want to extract.
2. Construct a PRESTO request url for the record:
   
   For HOLLIS: http://webservices.lib.harvard.edu/rest/mods/hollis/\{record_id_goes_here}
   For VIA: http://webservices.lib.harvard.edu/rest/mods/via/\{record_id_goes_here}
   
   
3. Paste the PRESTO request url into a browser. The MODS XML file for the record will display. If you don't see the XML, view source.
4. Use the browser's Save As option to save the xml file to a local directory. Web Admin has no particular requirements for file name, but the file extension should be xml.
5. Follow the import external MODS procedure above to import this MODS file into an object's descriptor.
    

Full details about using PRESTO are available in the PRESTO Data Lookup User Guide: http://hul.harvard.edu/ois/systems/webservices/lookup-userguide/.

Creating MODS from scratch using a template:

It is easiest to create a MODS file from scratch by starting with a valid MODS template and inserting your descriptions. You can use a MODS full record example from the Library of Congress MODS web site: http://www.loc.gov/standards/mods/v3/mods-userguide-examples.html.

1. Create a text file with a .xml extension. Make the file name whatever you want.
2. Select a sample MODS record on the LC site: http://www.loc.gov/standards/mods/v3/mods-userguide-examples.html.
3. Copy the entire LC MODS record and paste into your local MODS file.
4. Add descriptions to the template as needed. Remove elements that are not needed.
5. Save the file.
6. Follow the import external MODS procedure above to import this MODS file into an object's descriptor.

Updating the METS Label

The METS label provides a short descriptive label that identifies an object delivered by the Page Delivery Service (PDS). The METS label displays in the top pane of the PDS user interface. You can add a METS label at the point of deposit using Batch Builder or after an object is deposited via the object's Descriptive Metadata tab in Web Admin. 

You can create a METS label by copying in the MODS-generated label that is provided by default (if MODS data is associated with the object). Or you can create a custom label by entering text into the editor. Contents of the METS label is limited to 1,000 characters.



To add or update the METS label:

1. Display the object's metadata summary and select the Descriptive metadata tab. Locate the Current METS label field.
2. To update the METS label with the MODS-generated label, press the Replace with MODS-generated label button. If the MODS-generated label is blank, MODS metadata is not associated with the object. Follow instructions in the Uploading MODS section (below) to add MODS descriptions to the object.
3. To add a custom label, enter text directly in the Current METS label field.
4. Click the Save Changes button to commit this change.

Adding Harvard Metadata

There are two descriptive metadata fields that let you reference associated metadata in another system: Harvard Metadata and Related Links (see below). 

What is the purpose of the Harvard Metadata field? Use the Harvard Metadata field to reference Harvard metadata about an object that resides in another system. The most common use of this field is to add a live link to a cataloging record in Aleph or a finding aid in OASIS. Or use this field to reference a record number (but no live link) in OCLC or several other mostly legacy systems (e.g., HULPR, RLIN). These legacy Harvard metadata types were carried over from DRS1 in order facilitate the migration of DRS1 PDS document objects. 

How is the Harvard Metadata field used? For PDS objects, Harvard Metadata links will display in the Related Links window of the PDS public interface. For objects in other content models, Harvard Metadata links currently display only in Web Admin. 

To add a Harvard Metadata reference:

1. Display the object's metadata summary and select the Descriptive metadata tab. Locate the Harvard Metadata section.
2. Click +add Harvard Metadata and a data entry pop up will display.
3. Select a Type value from the dropdown and then enter an appropriate Identifier.

• Aleph:
  Produces a live link to a bibliographic record in the HOLLIS catalog. The Identifier for this link type must be a 9-digit Aleph system number. 
  In the PDS Related Links window, this link type is labeled "HOLLIS".

• Finding Aid:
  Produces a live link to a finding aid document. For OASIS finding aids, the identifier can be an EADID (a finding aid identifier, e.g. "hou01822") or an OASIS urn (e.g. http://nrs.harvard.edu/urn-3:FHCL.Hough:hou01822). For a finding aid in another system, provide a URN. Note: The Finding Aid type is not a live link when displayed in Web Admin. This is a known bug that will be addressed in a future release.

• Gale:
  Produces a reference to the OCLC identifier for a page-turned object from the Making of the Modern Economy online library produced by Thomson Gale (a DRS1 data loading project executed on behalf of Baker Library/Harvard Business School). The Identifier should be a valid OCLC value, such as 17346710.

• HULPR (called Old HOLLIS in DRS1)
  Produces a reference to a bibliographic record in the HOLLIS Catalog by way of a HULPR record number (HULPR was Harvard Library's cataloging system prior to Aleph). The Identifier must be a HULPR system number in the form ABC1234.

• Local
  The Local type is designed to reference information associated with the object that is not accessible by URI (such as a local system number or other note). The Identifier should be an identification number or note that explains the entry.

• OCLC
  Produces a reference to a record in the OCLC system (http://www.worldcat.org/). The Identifier should be a valid OCLC identifier, such as 2505627.
  
  
• RLIN
  Produces a reference to a record in the old RLIN system. The Identifier should be a valid RLIN number. 

4.  Click Add to add the Harvard Metadata reference.
5.  Click Save Changes to commit this change.

Adding Related Links

There are two descriptive metadata fields that let you reference associated metadata in another system: Harvard Metadata (see above) and Related Links. 

What is the purpose of the Related Links field? Use the Related Links field to link to a URL that provides information related to the object. You might use this field to reference a record in VIA (since the Harvard Metadata field does not yet support VIA references) or another online system or web site at Harvard or beyond. 

How is the Related Links field used? For PDS objects, Related Links will display in the Related Links window of the PDS public interface. The Relationship value will be used as link text, preceded by the label "Link". For objects in other content models, Related Links currently display only in Web Admin. 

To add a Related Link:

1. Display the object's metadata summary and select the Descriptive metadata tab. Locate the Related Links section.
2. Click +add Related Links and a data entry pop up will display.
3. Enter a Relationship value. This is a string of text that in the case of PDS objects, will be used as link text in the PDS Related Links window.
   Note: In the PDS Related Links window, there is a bug that will truncate a Relationship value that contains a space. For example, the Relationship value "Previous Issues" will be truncated to "Previous" when the link displays in PDS. This will be fixed in a future release. To avoid truncation, use a dash, underscore or other character to connect separate words; e.g., "Previous_Issues".
4. Enter Related URI. This will be a fully qualified URN or URL.
5. Click Add to add the Related Link.
6. Click Save Changes to commit this change.

http://webservices.lib.harvard.edu/rest/mods/hollis/\{record_id_goes_here}