Mapping MAB to MODS
|
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 | Comment |
001 | Record Identifier | Local, but not stable record identifier (always changes after updating the dataset) | recordInfo recordIdentifier id="MAB001" | :why to map this data if it is unstable? --Natasa 15:24, 9 March 2009 (UTC) Not needed by institut |
720 | Record Identifier | Local and stable record identifier (as 001 always changes after updating the data) | recordInfo recordIdentifier id="MAB720" | :why to map this data if it is unstable? --Natasa 15:24, 9 March 2009 (UTC) Should not be editable via GUI |
010 | RelatedItem.Identifier | Identifier of the parent | relatedItem type="host" identifier type="local" | :the identifier of the parent related item in escidoc is expressed as a structural relation. It is questionable if this still has to be mapped in the metadata?--Natasa 15:26, 9 March 2009 (UTC) |
037 | Language | Language | language languageTerm type="text" ger | is in here possible to use any of standard list of languages? --Natasa 15:58, 9 March 2009 (UTC) AP defines encoding schema RFC 4646 |
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> |
|
100b, 104b, 108b … 196b | Creator | Associated Name (normed) |
<name type="personal" authority="pnd"> <namePart> |
|
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 |
Place |
Place of publication |
<originInfo> <place> <placeTerm type="text"> | Not destinguishable after mapping :if we use originInfo type, we can create 2 separate metadata in the profile of originInfo type where one is for publisher and other for printer.--Natasa 16:07, 9 March 2009 (UTC) |
412 |
Publisher |
Publisher |
<originInfo> <publisher> | Not destinguishable after mapping : if we use originInfo type, we can create 2 separate metadata in the profile of originInfo type where one is for publisher and other for printer.--Natasa 16:07, 9 March 2009 (UTC) |
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.
- MAB001 not needed by Institute
- MAB720 needed for display purpose (NO editing!). Label would be: Katalognummer
Comments[edit]
- Problems with MAB fields 410 /412 and 410a/412a:
- 410 (place of publication) as well as 410a (place of print) can both only be mapped to mods:origininfo:place:placeterm, ending up with an array of placeterms, but unable to determine which one is place of publication or place of print
- the sane applies to 412 (publisher) and 412a (printer), which both are mapped to mods:origininfo:publisher.
- Solution: As discussed in meeting, we will create two originInfo entries, if the entry contains date value it representes a publisher, otherwise it represents a printer