Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Field*Schema Mapping*DomainExpected Value or Range*DefinitionObligation*Usage NotesSourceRemediation NotesExposure or Other Representation Element
This is the name of the field for ease of referring to it in documentation, communication, etc.This field should represent where the field is mapped to in the metadata records in the application, system, or service. It should also be the field mapped to a shared standard, namespace, or specification. This helps clarify the understanding of what the field means, as well as facilitates mapping that field to other metadata and MAPs.The expect resource or object type this metadata field is asserted against. Required if you're not going to split MAPs but need to specify fields that apply to only certain types of described resources.This is the expected metadata value for this field. Here you can specify data types (string, integer, datetime, etc.), specify value sources (controlled vocabularies, authorities, free-text entry, other), and any other specifications around the expected metadata (is identifier for an Agent resource; is a date following EDTF; is a Cornell email address; etc.)This is the definition for the field. This is helpful if it doesn't map (or doesn't map entirely) to a Namespaced Mapping or a Standard.

Indicates if the field is required and repeatable in the format:

{number of times expected, number of times can be present}

i.e.

{0,1} == Not required (can appear 0 times), Not repeatable (can only appear at most 1 time)

{1,1} == Required (must appear 1 time), Not repeatable (can only appear at most 1 time)

{0,n} == Not required, repeatable (can appear at most n times)

{1,n} == Required, repeatable.

You can also break this out into "Required?" and "Repeatable" columns with TRUE/FALSE values if easier. 

Any notes on using this field in the metadata generated.The source of the field - transformed from existing data in XYZ store or format, user-entered in the application, pulled from a shared database, etc.Any notes on cleanup, normalization, or enhancement of this field.This is the element or place this field gets captured in alternate exposure points, i.e., here is the element this field is presented as in the application's OAI-PMH stream. Here is the element the field appears in a backup copy of the metadata. Here is the field as the it appears in Solr. Etc.
          
          
          

Need Help with your MAP?