Talk:Mapping MAB to MODS

Manual mapping
The MPIER provided us with 5 MAB records for the two books (two parent records plus three child records). These 5 records will be mapped to MODS by using the rules defined in the ZVDD MODS profile. The result (MAB_MODS_v32_mapping) is available in the repository.

Results & Discussion:
 * 1) Hierarchical record structure
 * 2) * One record for each parent and each child record exists. The child record has an element  pointing to the parent record by using an identifier (URL/URN) The current MODS file only includes identifiers of type string (e.g.  ). These identifiers should be replaced by the appropriate uri, after the digital objects have been ingested
 * 3) * Alternative implementation (not recommended by zvdd) I: create only one object for the work and all its parts (element )
 * 4) * Alternative implementation (not recommended by zvdd) II: provide information for parent in child record without creating an individual record for the parent (element ).
 * 5) * Please Note: It is not necessary that the parent record points to its child records, because this information will already be stored in the eSciDoc container.
 * 6) Handling of subject strings ("Schlagwortketten")
 * 7) * In MAB subject strings are represented in the element 710 as strings. Further on, each subject is saved in one separate element 902.
 * 8) * In MODS we transfered each subject string in one element, several "Schlagwortketten" would be transferred to separate elements. But it would be also possible to put the subjects in separate elements.
 * 9) The "MODS application profile" used by the DFG viewer demands identifiers in form of URNs. The Deutsche Nationalbibliothek provides a service to assign URN (NBN).
 * 10) Missing Metadata in the MAB file
 * 11) * The "Bandtitel" from the Sisis file was not exported to MAB and can therefore not part of an automatic mapping to MODS. The MAB files have to be created properly so that no data will get lost.
 * 12) MODS offers no property for the local signature of the book (MAB element 544). Can we loose this information or is there another possibility to represent this? --Kristina 16:52, 14 February 2008 (CET)
 * I would suggest to map this information to, see example in MAB_MODS_v32_mapping --Inga 11:36, 18 February 2008 (CET)


 * You map 403 (MAB) to Edition Statement (AP) but this element does not exist in the application profile, should this be integrated?--Friederike 15:10, 3 March 2009 (UTC)
 * Will be added to AP--Friederike 10:32, 4 March 2009 (UTC)

011

 * why to map this data if it is unstable? --Natasa 15:24, 9 March 2009 (UTC)
 * Not needed by institut
 * Actually, I always expected MAB001 (= IDENTIFIKATIONSNUMMER DES DATENSATZES) to be stable. Is this due to a specific SISIS implementation? ... at least using MAB720 (STICHWOERTER) is! I would suggest to follow Natasa's suggestion and map MAB720 only --Inga 23:09, 10 March 2009 (UTC)

720

 * why to map this data if it is unstable? --Natasa 15:24, 9 March 2009 (UTC)
 * Should not be editable via GUI

010

 * 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)
 * And which identifier of the parent record is used? MAB001 or MAB720? --Inga 23:15, 10 March 2009 (UTC)
 * Only consider 720!--Friederike 08:10, 11 March 2009 (UTC)

410/412

 * 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)
 * Solution: see comments on content page

037

 * 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