Metadata Mapping refers to aligning your current metadata schema(s) and fields with a new format(s) and deciding how each field will be transformed and represented in the migrated content. This may or may not be required depending on your use cases. 

Objectives

  • Determine whether metadata mapping is needed
    Complete mapping if necessary

Suggested Collaborators

  • Project Lead
  • Technical Lead
  • Developers
  • Functional Specialists, i.e. metadata librarians, digital preservation teams etc.
  • SME on data and data migration

Available Template

Example

Instructions

  1. Review the Metadata Mapping Guidelines. 

  2. Decide whether you are keeping your metadata records in XML or mapping them to RDF.

  3. Follow instructions in the Metadata Mapping Guidelines to complete mapping.


Some considerations for mapping:

  1. It is easier to map your metadata after a remediation or a clean up.
  2. It is not likely that an exact mapping from your current schema to the new schema exists. You will have to build off mapping examples like that of the MIG to create your own.
  3. Be mindful of accidental map merging (i.e. Genre and Type both mapping to dc:type)
  4. Pay attention to the rules of the new fields (i.e. when mapping dates, if they are free text, make sure you select a date field that is also free text).


Tips and Recommendations

Having a clear list of all your fields and the structure of the metadata in those fields as well as what that field maps too will help prevent field loss. It will also help ease the process of selecting a field that will serve your metadata needs.

Next Steps: 

If you decide to restructure your metadata, consider exporting and reviewing your Fedora 3.x content again for a final review before a migration test run or a full migration.

Content by label

There is no content with the specified labels



All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.