Mapping MAB to MODS

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

Order	MAB Field	Label (of AP)	Description	MODS	Comment
1	001	Record Identifier	Local, but not stable record identifier (always changes after updating the dataset)	recordInfo recordIdentifier id="MAB001"
2	720	Record Identifier	Local and stable record identifier (as 001 always changes after updating the data)	recordInfo recordIdentifier id="MAB720"
3	010	RelatedItem.Identifier	Identifier of the parent	relatedItem type="host" identifier type="local"
4	037	Language	Language	language languageTerm type="text" ger	encoding schema RFC 4646
5	089 or 451 (only the numeral)	Order	Volume number	part type="host" order="…" detail number
6	100, 104, 108 … 196	Creator	Verfasser (normiert)	<name type="personal" authority="pnd"> <namePart type> <role> <roleTerm type="code" authority="marcrelator"> aut
7	100b, 104b, 108b … 196b	Creator	Associated Name (normed)	<name type="personal" authority="pnd"> <namePart> <role> <roleTerm type="code" authority="marcrelator"> asn
8	304	Title	Uniform title	<titleInfo type="uniform"><title>
9	310	Title	Other variant title	<titleInfo type="alternative"><title>
10	341	Title	Parallel title	<titleInfo type="translated"><title>
11	331	Title	Main Title	<titleInfo> <title>
12	335	Subtitle	Subtitle	<titleInfo> <subtitle>
13	359	Note	Statement of responsibility	<note type="statementOfResponsibility">
14	361	RelatedItem.Title	Work in a collection without collective title	<relatedItem type="constituent"> <titleInfo> <title>
15	403	EditionStatement	Edition Statement	<originInfo> <edition>
16	410 410a	Place	Place of publication Place of printing	<originInfo> <place> <placeTerm type="text">
17	412 412a	Publisher	Publisher Printer	<originInfo> <publisher>
18	425	DateIssued	Date of publication	<originInfo> <dateIssued keyDate="yes" encoding="w3cdtf">
19	433	NumberOfPages	Collation	<physicalDescription> <extent>
20	451 (all)	RelatedItem.Title	Series Title	<relatedItem type="series"> <titleInfo> <title>
21	501	Note	Note	<note>
22	544	Location	Shelfmark	<location> <physicalLocation>
23	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

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

• MAB Format

General Information

• 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

• 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

Maschinelles Austauschformat für Bibliotheken

Metadata Object Description Schema

Request For Comment