Difference between revisions of "Talk:ViRR Metadata"
Jump to navigation
Jump to search
(New page: = Discussion on data formats for Metadata = === Possible formats === ==== 1. eBind ==== [http://sunsite.berkeley.edu/Ebind/ eBind] was developed in (1996) but has never been finished as ...) |
|||
| Line 1: | Line 1: | ||
= Discussion on data formats for Metadata = | = Discussion on data formats for Metadata = | ||
== | == METS == | ||
* 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 | |||
''' | '''--> An 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/eBinds/eSciDoc) can be used in three different ways: | In general, an external format (like METS/eBinds/eSciDoc) can be used in three different ways: | ||
# importing digital objects in eSciDoc's native format | # importing digital objects in eSciDoc's native format | ||
| Line 36: | Line 18: | ||
# exporting to METS -> export is probably not very problematic | # 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? | ||
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 | '''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. | ||
Revision as of 12:19, 31 January 2008
Discussion on data formats for Metadata[edit]
METS[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
--> An METS import and export is needed.
eSciDoc native format[edit]
- 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[edit]
In general, an external format (like METS/eBinds/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.