...
Div | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
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
- Obtain the Aleph record ID number.
- Display the object's metadata summary and select the Descriptive metadata tab.
- Open the Replace MODS pane by clicking the arrow.
- Enter the ID in the Upload MODS by Aleph ID field.
- 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 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:
- Create the MODS file and save it to a convenient location on your file system.
- Display the object's metadata summary and select the Descriptive metadata tab.
- Open the Replace MODS pane by clicking the arrow.
- Under Upload MODS File, click the Choose file button.
- Navigate to the MODS file on your file system and select it.
- 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.
- Identify the ID of the record you want to extract.
- 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} - 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.
- 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.
- Follow the import external MODS procedure above to import this MODS file into an object's descriptor.
Note |
---|
Note about VIA: A PRESTO request for VIA will return the record with all components (e.g., a work plus all surrogates). Typically, what you need for object-level description in DRS2 is an individual surrogate description. Before inserting a VIA MODS file into your batch, you may need to edit the file to remove surrogate descriptions that do not apply to the object you are depositing. |
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.
- Create a text file with a .xml extension. Make the file name whatever you want.
- Select a sample MODS record on the LC site: http://www.loc.gov/standards/mods/v3/mods-userguide-examples.html.
- Copy the entire LC MODS record and paste into your local MODS file.
- Add descriptions to the template as needed. Remove elements that are not needed.
- Save the file.
- 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.
Note |
---|
Note: If a PDS object lacks a METS label, the PDS user interface will substitute the author and title from MODS data associated with the object (if this data is available). |
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:
- Display the object's metadata summary and select the Descriptive metadata tab. Locate the Current METS label field.
- 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.
- To add a custom label, enter text directly in the Current METS label field.
- 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).
...
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.
...
- Display the object's metadata summary and select the Descriptive metadata tab. Locate the Related Links section.
- Click +add Related Links and a data entry pop up will display.
- 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". - Enter Related URI. This will be a fully qualified URN or URL.
- Click Add to add the Related Link.
- Click Save Changes to commit this change.
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.
Note |
---|
Note: If a PDS object lacks a METS label, the PDS user interface will substitute the author and title from MODS data associated with the object (if this data is available). |
...
- Display the object's metadata summary and select the Descriptive metadata tab. Locate the Current METS label field.
- 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.
- To add a custom label, enter text directly in the Current METS label field.
- Click the Save Changes button to commit this change.
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 |
---|
Note: DRS2 accepts files up to MODS version 3.4. MODS versions higher than 3.4 will be rejected. The MODS version delivered by Aleph import and the PRESTO service will always be acceptable. |
Uploading MODS by Aleph ID
- Obtain the Aleph record ID number.
- Display the object's metadata summary and select the Descriptive metadata tab.
- Open the Replace MODS pane by clicking the arrow.
- Enter the ID in the Upload MODS by Aleph ID field.
- 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 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:
- Create the MODS file and save it to a convenient location on your file system.
- Display the object's metadata summary and select the Descriptive metadata tab.
- Open the Replace MODS pane by clicking the arrow.
- Under Upload MODS File, click the Choose file button.
- Navigate to the MODS file on your file system and select it.
- 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.
- Identify the ID of the record you want to extract.Construct a PRESTO request url for the record:
For HOLLIS:
http://webservices.lib.harvard.edu/rest/mods/hollis
...
/
...
\{record_id_goes_here}
...
Note |
---|
Note about VIA: A PRESTO request for VIA will return the record with all components (e.g., a work plus all surrogates). Typically, what you need for object-level description in DRS2 is an individual surrogate description. Before inserting a VIA MODS file into your batch, you may need to edit the file to remove surrogate descriptions that do not apply to the object you are depositing. |
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.
...