Difference between revisions of "Mapping MAB to MODS"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 19: Line 19:
| Record Identifier   
| Record Identifier   
| Local and stable record identifier (as 001 always changes after updating the data)
| Local and stable record identifier (as 001 always changes after updating the data)
| recordInfo.recordIdentifier.id="MAB720"
| recordInfo recordIdentifier id="MAB720"
|-
|-
| 010
| 010

Revision as of 12:47, 4 March 2009

Virr Medium Multivolume 31 Static.gif Virtueller Raum Reichsrecht

Overview
Functionalities
Support
Copyright and Disclaimer
Scope

Metadata:
Application Profile · Content Models
Metadata Display · ViRR Metadata
Action Matrix

Transformations:
virr 2 mets · mab 2 mods
mods 2 oai dc · mods 2 marc21

Specification

Intern:
Meetings · GUI · Miscellaneous
Development · Planning · Feedback
Related Projects:
Judicial Journals · Late Scholasticism
Digitization Lifecycle

edit


On this page a small mapping from MAB to MODS based on the requirements for the ViRR project will be provided.

MAB - MODS Mapping[edit]

MAB Field Label (of AP) Description MODS
001 Record Identifier Local, but not stable record identifier (always changes after updating the dataset) recordInfo recordIdentifier id="MAB001"
720 Record Identifier Local and stable record identifier (as 001 always changes after updating the data) recordInfo recordIdentifier id="MAB720"
010 RelatedItem.Identifier Identifier of the parent relatedItem type="host" identifier type="local"
037 Language Language language languageTerm type="text" ger
089 or 451 (only the numeral) Order Volume number part type="host" order="…" detail number
100, 104, 108 … 196 Creator Verfasser (normiert)

<name type="personal" authority="pnd"> <namePart type>
<role> <roleTerm type="code" authority="marcrelator"> aut

100b, 104b, 108b … 196b Creator Associated Name (normed)

<name type="personal" authority="pnd"> <namePart>
<role> <roleTerm type="code" authority="marcrelator"> asn

304 Title Uniform title <titleInfo type="uniform"><title>
310 Title Other variant title <titleInfo type="alternative"><title>
341 Title Parallel title
<titleInfo type="translated"><title>
331 Title Main Title <titleInfo> <title>
335 Subtitle Subtitle
<titleInfo> <subtitle>
359 Note Statement of responsibility <note type="statementOfResponsibility">
361 RelatedItem.Title Work in a collection without collective title <relatedItem type="constituent"> <titleInfo> <title>
403 EditionStatement Edition Statement <originInfo> <edition>

410
410a

Place

Place of publication
Place of printing

<originInfo> <place> <placeTerm type="text">

412
412a

Publisher

Publisher
Printer

<originInfo> <publisher>
425 DateIssued Date of publication <originInfo> <dateIssued keyDate="yes" encoding="w3cdtf">
433 NumberOfPages Collation <physicalDescription> <extent>
451 (all) RelatedItem.Title Series Title <relatedItem type="series"> <titleInfo> <title>
501 Note Note <note>
544 Location Shelfmark <location> <physicalLocation>
902, 907, 912 … 947 Subject Keyword <subject> <topic>

All subjects of one similar field (e.g. 902) shall first be mixed to a subject chain with / between each word so that the values will be handled as one subject, not as several ones.

Example Data[edit]

Following bibliographic metadata is currently available (only for the exemplary books):

General Information[edit]

  • As a rule we can state that every element is mapped with the full path. That means that for every MAB entry a full MODS element will be created. E.g.: every creator will have his own name tag.
  • The bibliographic metadata will be transferred to MODS to follow the recommendation from the zvdd.