-
Notifications
You must be signed in to change notification settings - Fork 0
Creating the mapping.yml files
Consult the Oregon Digital to Hydra Collection Checklist spreadsheet in the linked data_working folder on Google drive to see the deadlines for submitting the mappings and linked terms.
Map metadata fields as Linked Data (YAML file)
a. Find fields and equivalent properties
-
View the fields for each collection in CONTENTdm (CDM) by accessing the administrative client (https://contentdm.oregondigital.org/cgi-bin/admin/), choosing the collection you want to view in the drop-down box, and clicking “Fields” in the upper right-hand toolbar.
-
Find corresponding terms in the Field Names columns to equivalent properties (not classes) in other metadata schemas. Dublin Core Metadata (http://dublincore.org/documents/dcmi-terms/) is the default for CDM and will suffice in there isn’t a more fitting property.
-
See the Metadata Resources document for links to sources for searching for schemas, properties, and controlled vocabularies.
b. Map fields in .yml file
-
Download and open the mapping.yml file template in the linked data_working folder on Google drive.
-
List the CISONICK of each field followed by a “:” (for example- ident: ). The CISONICKS can be found at the end of the URL of the field in CDM when you click “edit” to the right of the field name.
-
After the “:”, add the approved abbreviation for the schema that’s being used to map the field. Please refer to the Metadata Dictionary (https://docs.google.com/document/d/1pudn5bDMikQ0xlNv6cEnscDkakCyeRjPwVkFNNVp0JM/edit#heading=h.4xjto5aqul0) and/or the Metadata Standards spreadsheet in the linked data_working folder on Google drive for the correct spelling/format of the abbreviation. For example, you would now have identi: dct: (dct for Dublin Core).
-
After the mapping abbreviation, add the property you chose. Be sure to use the correct spelling and syntax that the ontology/vocabulary uses. It should now look like identi: dct: identifier (for http://dublincore.org/documents/dcmi-terms/#elements-identifier).
-
If any fields are skipped, list # SKIP in that field.
c. List the URLs of the schemas in the section above the collection mappings. List the abbreviation of the schema followed by a : with the URL in listed afterwards in “ “. For example, dct: "http://purl.org/dc/elements/1.1/"
Upload the file to the linked data_working folder on Google drive as month to map_mapping_abbreviation of collection. Example: June_mapping_oimb.yml.
Upload to git as a branch
Next: Linking collection terminologies with LOD: https://github.com/kestlund/UO-meta-oregon-digital/wiki/Linking-collection-terminologies-with-LOD