Difference between revisions of "Talk:ViRR and METS"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) m (→Discussion) |
|||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= | == [[Metadata_Encoding_and_Transmission_Standard|METS]] == | ||
== | ===General Information=== | ||
* METS enables the mark up of front, cover, etc. | * 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. | * 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 | * 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 | ||
===Open Discussion=== | |||
* VIRR needs to handle METS for: | |||
*# Import | |||
*#:Therefor a Mapping from VIRR METS to TOC is needed. | |||
*# Export | |||
*#:See closed discussion | |||
*We should define a VIRR METS application profile | |||
=== Discussion === | ===Closed Discussion=== | ||
In general, an external format (like METS/eSciDoc) can be used in three different ways: | * A METS import and export is needed. Therefore, an Mapping from the eSciDoc Container Format to METS is needed. This has to be written in XSLT (for exemple see the Mapping [https://subversion.mpdl.mpg.de/trac/wiki/eSciDoc_to_DCXSLT eSciDoc to DC]. | ||
# importing digital objects in eSciDoc's native format | *: Mapping for [[ViRR_and_METS | TOC - DFG METS ]] is already implemented.--[[User:Kleinfercher|Friederike]] 09:02, 11 February 2009 (UTC) | ||
# 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 | *In general, an external format (like METS/eSciDoc) can be used in three different ways: | ||
# exporting to METS -> export is probably not very problematic | *# 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:''' | '''Questions:''' | ||
# is the eSciDoc native format rich/flexible enough to represent the [structure of the] digital objects as required by MPIeR? | # 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? | # If yes, does this mean we need to provide an offline editor for the eSciDoc native format ourselves? | ||
: --> 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. | |||
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 13:08, 25 April 2012
METS[edit]
General Information[edit]
- 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
Open Discussion[edit]
- VIRR needs to handle METS for:
- Import
- Therefor a Mapping from VIRR METS to TOC is needed.
- Export
- See closed discussion
- Import
- We should define a VIRR METS application profile
Closed Discussion[edit]
- A METS import and export is needed. Therefore, an Mapping from the eSciDoc Container Format to METS is needed. This has to be written in XSLT (for exemple see the Mapping eSciDoc to DC.
- Mapping for TOC - DFG METS is already implemented.--Friederike 09:02, 11 February 2009 (UTC)
- 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?
- --> 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.