[
http://jira.dspace.org/jira/browse/DS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10830#action_10830
]
Larry Stone commented on DS-386:
--------------------------------
It's OK, although I would like to see a comment in the source noting that it's
a liberalization of the standard. Just in case anyone trusts running code more
than documents.
> Allow user to specify which <dmdSec> is used by the METS Ingester when
> importing METS from Packager script
> ----------------------------------------------------------------------------------------------------------
>
> Key: DS-386
> URL: http://jira.dspace.org/jira/browse/DS-386
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.6.0
> Environment: Any command line environment
> Reporter: Tim Donohue
> Assignee: Tim Donohue
> Priority: Minor
> Attachments: METSIngesterParams.patch
>
>
> Currently, the DSpaceMETSIngester makes the choice of which <dmdSec> to
> crosswalk when a METS file is ingested by the Packager script. The current
> algorithm is as follows (as documented in DSpaceMETSIngester.chooseItemDmd()
> method):
> (1) Crosswalk the MODS <dmdSec> if found
> (2) If MODS not found, crosswalk the DC <dmdSec> if found
> (3) If neither are found, crosswalk the first <dmdSec> encountered
> I'd like to propose that we also allow the user to specify the primary
> <dmdSec> to be crosswalked, via a commandline parameter. So, instead, the
> new algorithm would be:
> (1) Crosswalk the <dmdSec> specified by the "dmd" parameter to the Packager
> script (if specified)
> (2) If "dmd" param not specified, crosswalk the MODS <dmdSec> if found
> (3) If MODS not found, crosswalk the DC <dmdSec> if found
> (4) If none are found, crosswalk the first <dmdSec> encountered
> The reasoning for this change is that it could be possible that there are
> multiple <dmdSec>'s and the MODS or the DC may not actually be the best
> choice to crosswalk (to avoid metadata loss). A simple example could be if a
> user had exported a METS file from DSpace containing both DIM and MODS. With
> the old algorithm, the MODS <dmdSec> would be choosen....even though in this
> special case the DIM <dmdSec> would be more appropriate as DSpace doesn't
> even need to crosswalk it.
> A patch is attached for review.
--
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
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
