Tip:
Highlight text to annotate it
X
Hello, and welcome to this instructional screencast on the Curator's Workbench. This is Jennifer
Martin from the Carolina Digital Repository.
In this screencast, I will show you how to create metadata mappings within a crosswalk.
To add components, select the component you want to add from the palette on the right
and then click in the canvas to drop it.
Dropping a MODS element onto blank canvas takes you to a list of top-level MODS elements,
where you select the element you want.
Dropping a MODS element into an existing MODS element takes you to a list of the sub-elements
available for that specific element.
MODS attributes are added by dropping them into the appropriate MODS elements.
For both elements and attributes, the software uses the MODS schema to determine what options
to offer.
Both elements and attributes hold assigned values.
To assign these values, you can either map the user-created metadata to the field or
you can assign a default value.
Mapping the user-created metadata connects a field in the delimiter-separated values
document to the MODS field; for each object, the software will populate the MODS field
with the value from the appropriate row in the supplied metadata.
To create such a mapping, click on the connector element in the palette, then click on the
circle next to the MODS field you want to map to, and drag to the supplied field you
want to map from.
If you are mapping a date, then it must be mapped via the date maker.
This transforms the date from the supplied text to the MODS-required ISO date format.
To use the date maker, drop it onto the canvas, and then connect the MODS field to the date
maker and the date maker to the supplied field.
If you are mapping an access condition, use the ":mixed" field in the attribute list to
add text or a mapped value.
This allows XML values to be included in the element, per the MODS schema.
Default values serve two purposes: they are used to assign constant values to a field,
and they are used to provide a default value for mapped fields.
To assign a default value, click on the MODS field you want to set the value for and navigate
to the properties pane.
In the default value field, type the value you want.
You'll notice that some elements have defined lists of allowed values.
For mapped fields, if you don't provide a default value, the element will be omitted
whenever the supplied field is empty.
In order to connect the crosswalk-created records with the digital objects, you must
use the original file matcher.
To do so, drop it onto the canvas and map it to the supplied metadata field which gives
the names of the files.
To remove an element, attribute, or mapping, select its graphical representation and delete
it.
To remove a default value, right-click on the default value field in the properties
pane and select "Restore Default Value".
Note that simply deleting the text will not return the value to null; instead, it will
give a default value of a space.
Remember to periodically save the changes to your crosswalk, as it doesn't save automatically.
And that's how you map crosswalks.
For more information about the Workbench and further instructions on how to use it, please
see our other screencasts.
You can also visit the CDR site to see live examples of Workbench-created collections,
the GitHub repository for code, or our blog for release information.
Thank you for listening, and have a nice day!