Difference between revisions of "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

Revision as of 14:02, 21 July 2009

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"	not needed by Institute
720	Record Identifier	Local and stable record identifier (as 001 always changes after updating the data)	recordInfo recordIdentifier id="MAB720"	needed for display purpose (NO editing!). Label would be: Katalognummer
3	010	RelatedItem.Identifier	Identifier of the parent	relatedItem type="host" identifier type="local"
037	Language	Language	language languageTerm type="text" ger	encoding schema RFC 4646
089 or 451 (only the numeral)	Order	Volume number	part type="host" order="…" detail number
100, 104, 108 … 196	Creator (normed)	Verfasser (normiert)	<name type="personal" authority="pnd"> <namePart type> <role> <roleTerm type="code" authority="marcrelator"> aut
100b, 104b, 108b … 196b	Creator (normed)	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">	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
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):

MAB Format

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.

@@ Line 7: / Line 7: @@
 {| border="1" align="center" class="sortable"
 |- bgcolor = "#F5FFFA"
-!'''Order'''!!'''MAB Field'''!!'''Label (of [[ViRR_Application_Profile|AP]])'''!!'''Description'''!!'''MODS'''!!'''Comment'''
+!'''MAB Field'''!!'''Label (of [[ViRR_Application_Profile|AP]])'''!!'''Description'''!!'''MODS'''!!'''Comment'''
 |-
-| 1
 | 001
 | Record Identifier
@@ Line 16: / Line 15: @@
 | '''not needed by Institute'''
 |-
-| 2
 | 720
 | Record Identifier
@@ Line 30: / Line 28: @@
 |
 |-
-| 4
 | 037
 | Language
@@ Line 37: / Line 34: @@
 | encoding schema RFC 4646
 |-
-| 5
 | 089 or 451 (only the numeral)
 | Order
@@ Line 44: / Line 40: @@
 |
 |-
-| 6
 | 100, 104, 108 … 196
 | Creator (normed)
@@ Line 53: / Line 48: @@
 |
 |-
-| 7
 | 100b, 104b, 108b … 196b
 | Creator (normed)
@@ Line 62: / Line 56: @@
 |
 |-
-| 8
 | 304
 | Title
@@ Line 69: / Line 62: @@
 |
 |-
-| 9
 | 310
 | Title
@@ Line 76: / Line 68: @@
 |
 |-
-| 10
 | 341
 | Title
@@ Line 83: / Line 74: @@
 |
 |-
-| 11
 | 331
 | Title
@@ Line 90: / Line 80: @@
 |
 |-
-| 12
 | 335
 | Subtitle
@@ Line 97: / Line 86: @@
 |
 |-
-| 13
 | 359
 | Note
@@ Line 104: / Line 92: @@
 |
 |-
-| 14
 | 361
 | RelatedItem.Title
@@ Line 111: / Line 98: @@
 |
 |-
-| 15
 | 403
 | EditionStatement
@@ Line 118: / Line 104: @@
 |
 |-
-| 16
 |
 <br/>
@@ Line 132: / Line 117: @@
 * '''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
 |-
-| 17
 |
 <br/>
@@ Line 142: / Line 126: @@
 | <originInfo> <publisher>
 |-
-| 18
 | 425
 | DateIssued
@@ Line 149: / Line 132: @@
 |
 |-
-| 19
 | 433
 | NumberOfPages
@@ Line 156: / Line 138: @@
 |
 |-
-| 20
 | 451 (all)
 | RelatedItem.Title
@@ Line 163: / Line 144: @@
 |
 |-
-| 21
 | 501
 | Note
@@ Line 170: / Line 150: @@
 |
 |-
-| 22
 | 544
 | Location
@@ Line 177: / Line 156: @@
 |
 |-
-| 23
 | 902, 907, 912 … 947
 | Subject

Difference between revisions of "Mapping MAB to MODS"

Revision as of 14:02, 21 July 2009

MAB - MODS Mapping[edit]

Example Data[edit]

General Information[edit]

Navigation menu

Search