Difference between revisions of "Talk:ViRR Metadata"

From MPDLMediaWiki
Jump to navigation Jump to search
(Removing all content from page)
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Mappings and Transformations =


== MAB to MODS mapping ==
The MPIER provided us with [https://zim01.gwdg.de/repos/smc/trunk/03_Functional_Description/02_Scenarios_Concepts/Concepts/Virtueller%20Raum%20Reichsrecht/02_Exemplary_Data/ 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 [http://dfg-viewer.de/fileadmin/groups/dfgviewer/MODS_Application_Profile_2008-01-09b.pdf ZVDD MODS profile]. The result ([https://zim01.gwdg.de/repos/smc/trunk/03_Functional_Description/02_Scenarios_Concepts/Concepts/Virtueller%20Raum%20Reichsrecht/01_Documentation/MAB_MODS_v32_mapping.xml MAB_MODS_v32_mapping]) is available in the repository.
'''Results & Discussion:'''
# Hierarchical record structure
#* One record for each parent and each child record exists. The child record has an element <code><relatedItem type="host"></code> pointing to the parent record by using an identifier (URL/URN) <br> The current MODS file only includes identifiers of type string (e.g. <code><identifier type="local">66237</identifier></code>). These identifiers should be replaced by the appropriate uri, after the digital objects have been ingested
#* Alternative implementation (not recommended by zvdd) I: create only one object for the work and all its parts (element <code><part type="constituent"></code>)
#* Alternative implementation (not recommended by zvdd) II: provide information for parent in child record without creating an individual record for the parent (element <code><relatedItem type="host"></code>).
# Handling of subject strings ("Schlagwortketten")
#* In MAB subject strings are represented in the element 710 as strings. Further on, each subject is saved in one separate element 902.
#* 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.
# The "MODS application profile" used by the DFG viewer demands identifiers in form of [http://en.wikipedia.org/wiki/Uniform_Resource_Name URNs]. The Deutsche Nationalbibliothek provides a service to assign [http://www.persistent-identifier.de/?link=860&lang=en URN (NBN)].
# 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? --[[User:Kristina|Kristina]] 16:52, 14 February 2008 (CET)
:: I would suggest to map this information to <code><location><physicallocation></code>, see example in [https://zim01.gwdg.de/repos/smc/trunk/03_Functional_Description/02_Scenarios_Concepts/Concepts/Virtueller%20Raum%20Reichsrecht/01_Documentation/MAB_MODS_v32_mapping.xml MAB_MODS_v32_mapping] --[[User:Inga|Inga]] 11:36, 18 February 2008 (CET)
= Discussion on data formats for Metadata =
== [[Metadata_Encoding_and_Transmission_Standard|METS]] ==
* METS enables the mark up of front, cover, etc.
* METS is an international standard. It displays the hierarchical structure, the name and the location of the data storage and the metadata of objects. --> METS can be used for descriptive metadata as well as container format.
* Im Interesse weiterer Projekte (fuer die ggf. eine Foerderung der DFG beantragt werden koennte) ist METS nahezu zwingend. Alternativ zu diesem seitenorientierten Format kaeme TEI als dokumentorientiertes Format in Frage. Das MPI praeferiert eindeutig METS, da es den gegenwaertigen Anforderungen genuegt und einen geringeren Aufwand nach sich zieht. s. auch DFG-Praxisregeln, S. 17. 18.10.2007, S. Amedick
'''--> A METS import and export is needed.'''
== eSciDoc native format ==
* It will be checked together with FIZ, if the METS data will be stored in METS or transfered and stored in eSciDoc native format.
== Discussion ==
In general, an external format (like METS/eSciDoc) can be used in three different ways:
# importing digital objects in eSciDoc's native format
# importing from METS format - might be very problematic from Natasa's point of view, e.g. because METS is very broad and only a specific import for ViRR METS can be done
# supporting METS as native format in eSciDoc -> this would require a lot of redesign in the basic services. According to Malte there are related requirements coming from the GBV
# exporting to METS -> export is probably not very problematic
'''Questions:'''
# is the eSciDoc native format rich/flexible enough to represent the [structure of the] digital objects as required by MPIeR?
# If yes, does this mean we need to provide an offline editor for the eSciDoc native format ourselves?
'''Result:''' This question is the mayor decision in the project and will influence the required/chosen implementation essentially. The decision needs to be taken until January 2008! We decided to prepare an detailed evaluation together with FIZ.

Latest revision as of 12:26, 27 February 2009

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Talk:ViRR_Metadata&oldid=29077"