[
https://jira.duraspace.org/browse/DS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21019#action_21019
]
Tim Donohue commented on DS-708:
--------------------------------
Hi Mark,
I'm not sure I understand what you mean? Are you saying add a new 'dspace.cfg'
configuration that the to the MODSCrosswalk which turns off the mapping of the
dc.description.provenance field?
Maybe it will help to look at how this request from OAI-PMH makes it down to
the MODSDisseminationCrosswalk. Currently, the processing would look like this:
* To create METS, OAI-PMH calls the METSDisseminationCrosswalk
* METSDisseminationCrosswalk calls DSpaceMETSDisseminator (to actually generate
the METS)
* DSpaceMETSDisseminator calls the MODSDisseminationCrosswalk (to generate MODS
section in the METS)
* MODSDisseminationCrosswalk uses the mods.properties file to map DIM to MODS
(since dc.description.provenance is listed in this mods.properties mapping
file, it is always mapped into the MODS output of this crosswalk)
Unfortunately, the MODSDisseminationCrosswalk has no idea whether the request
is coming from OAI-PMH, or from command-line, or from XMLUI, LNI, etc. So,
right now it just obeys whatever mappings are listed in 'mods.properties'. One
of the issues here is that DisseminationCrosswalks don't accept any parameters
(other than the DSpaceObject they are crosswalking), so there's no real way to
easily tell the MODSDisseminationCrosswalk to "skip" the mapping of
'dc.description.provenance' for requests from OAI-PMH.
Did I misunderstand your suggestion here?
> Deprecate & Remove old 'org.dspace.app.mets.METSExport' class, as it is
> obsolete
> --------------------------------------------------------------------------------
>
> Key: DS-708
> URL: https://jira.duraspace.org/browse/DS-708
> Project: DSpace
> Issue Type: Code Task
> Components: DSpace API, OAI-PMH
> Affects Versions: 1.7.0
> Reporter: Tim Donohue
> Assignee: Tim Donohue
> Fix For: 1.8.0
>
> Attachments: DS-708-dspace-api.patch, DS-708-dspace-oai-api.patch,
> sample-mods-properties.patch
>
>
> With the improvements that have happened to the METS Ingest and Dissemination
> packager classes in DSpace 1.7.0 (see DS-466), we should deprecate & remove
> the old 'org.dspace.app.mets.METSExport' class, as it is now considered
> obsolete.
> This older METSExport class is currently used in the following places:
> * OAI-PMH interface (by the org.dspace.app.oai.METSCrosswalk class)
> My proposal is to deprecate this class in DSpace 1.7.0, and then work to
> remove & replace its usage within the OAI-PMH interface in the next major
> version of DSpace (1.8.0).
> The replacement for METSExport is the following classes:
> * org.dspace.content.packager.DSpaceMETSDisseminator
> * org.dspace.content.packager.DSpaceMETSIngester
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
