[
http://jira.dspace.org/jira/browse/DS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10735#action_10735
]
Stuart Lewis commented on DS-257:
---------------------------------
Keeping backwards compatibility is a must for 1.6, yet moving to this combined
metadata.xml file is a positive step forward.
How about this as a solution:?
Importer:
1) Allow the FilenameFilter in ItemImport also accept metadata.xml as a valid
filename
2) Allow <metadata> as a valid root node in metadata files (as well as
<dublin_core>)
3) Allow <metadatavalue> (as well as <dcvalue>) for metadata nodes
4) If a schema='schema" is specified in a metadata node, use that, and override
any schema specified in the root node
5) If no schema is given in the root node or the metadatavalue, report an error
Exporter:
1) Default to exporting with metadata.xml
2) Provide a legacy flag in the CLI (and a configurable option in for the UIs)
that exports in the old dublin_core.xml format
My worry with this is that is the importer gets a bit messy and relaxed over
formats. Is that a good thing, or a bad thing? Alternatively, could we ship
with ItemImportV2.java, and use that by default, but allow users to specify in
dspace.cfg whether they want to work with v1 or v2 import/export format?
> Item Import and Export, use of multiple metadata schema
> -------------------------------------------------------
>
> Key: DS-257
> URL: http://jira.dspace.org/jira/browse/DS-257
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.6.0
> Reporter: Claudia Jürgen
> Assignee: Stuart Lewis
> Fix For: 1.6.0
>
> Attachments: ItemImExport.patch
>
>
> At the moment the item import of items with metadata from different metadata
> schemata requires an extra metadata file per schema.
> This patch enables the use of one metadata file which can hold metadata of
> all schema both for import and export.
> The new file is named (schema neutral) metadata.xml and got the structure
> <?xml version="1.0" encoding="utf-8" standalone="no"?>
> <metadata>
> <metadatavalue schema="SCHEMA" element="ELEMENT" qualifier="QUALIFIER/NONE"
> language="LANGUAGE">Foo
> </metadatavalue>
> ...
> </metadata>
> A new command line option is introduced
> -l for the use of the default language qualifier which defaults to not use it
> This will avoid assigning unintentionally wrongly qualified metadata, as it
> is often the case with DSpace instances which hold non en metainformation.
> Furthermore this patch fixes DS-256
> http://jira.dspace.org/jira/browse/DS-256.
> (The documentation will follow for the DSpace docs will follow.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
