[
https://jira.duraspace.org/browse/DS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26792#comment-26792
]
Mark H. Wood commented on DS-1173:
----------------------------------
So, let's move the registry loader out of the metadata importer. Then
load-registry can use it.
Bitstream formats and metadata registries should be not only conceptually
separate, but where we put their external representations should be physically
separate. Good support for multiple registries should include the ability to
easily add a registry without having to hack it specifically into the
installation and test code, but right now that's what is done. Better to be
able to load every file in a given directory without worrying about other stuff
in the same place. Maybe /config/registries should split into
/config/registries/formats and /config/registries/metadata.
While we are at it, the type registry XML schema (not that we actually *have*
one -- another bit to do) has various dc-this, dc-that elements, which is fine
(but redundant) for the single registry we currently distribute but confusing
for anything else. If we do continue to use custom XML then we should remove
its DC-centricity.
There is a lot that could (and should) be done to make metadata handling in
DSpace more flexible, but at least making multiple 2-level hierarchies fully
general and well-supported would be a nice first step.
As long as I'm piling on things to do, we could also do with a way to *export*
metadata schemas. That way one could use the administrative UI as a GUI tool
for creating and adjusting metadata definitions, and then backup or even share
them.
> registry loader does not employ the more flexible MetadataImporter
> ------------------------------------------------------------------
>
> Key: DS-1173
> URL: https://jira.duraspace.org/browse/DS-1173
> Project: DSpace
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.8.2
> Environment: All
> Reporter: Richard Jones
>
> There is a registry loader command:
> ./dspace load-registry -dc [file path]
> which loads dspace metadata registry format files into the registry. There
> is a superior implementation of the metadata registry loader in
> org.dspace.administer.MetadataImporter, and the registry loader does not use
> this, but replicates old functionality which the MetadataImporter was written
> to replace. The current registry loader, for example, dies if schema or
> metadata entries are repeated, while the MetadataImporter simply skips
> repeated options.
> This is useful if you have a number of applications for your DSpace instance,
> and metadata schemas for each of these applications (e.g. theses management,
> research information data feeds, etc). With the MetadataImporter you can
> maintain separate complete schemas for each application, load them all
> sequentially (on top of the default dspace registry), and be sure that your
> resulting registry is the super-set of all required metadata. With the
> existing registry loader you must maintain exactly one de-duplicated schema
> which covers all possible uses, which is inconvenient.
> The ideal thing to do would be to wire the registry loader into the
> MetadataImporter
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
