[
https://jira.duraspace.org/browse/DS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-708:
---------------------------
Attachment: DS-708-dspace-oai-api.patch
DS-708-dspace-api.patch
Was able to look into this today after all, and the fix is easier than
anticipated. The above patches to the dspace-api and dspace-oai-api should
resolve this issue for 1.8.0.
These patches do the following:
(1) 'dspace-api.patch' -- Removes METSExport class. Makes small tweaks to the
METSDisseminationCrosswalk so that it can be used as the replacement for
METSExport class. Also makes a minor tweak to the makeBitstreamURL() method of
all *METSDisseminator classes, to ensure they all can create a
"semi-persistent" Bitstream URL in their disseminated METS. (This is necessary
because someone harvesting METS via OAI-PMH would want that METS file to
reference Bitstreams via a valid URL)
(2) 'dspace-oai-api.patch' -- Changes the org.dspace.app.oai.METSCrosswalk to
just wrap a call to the METSDisseminationCrosswalk (rather than calling
METSExport)
I've done some basic testing with the latest Trunk Code, and I've been able to
verify that these patches are able to disseminate METS metadata via OAI-PMH
(and that the disseminated METS metadata contains links back to where
bitstreams can be downloaded from DSpace).
I'll commit these changes to Trunk shortly, as I don't think anything I've done
here is very controversial. (The largest change is the cleanup of the
*METSDisseminator classes, where I just copied the makeBitstreamURL() method
from DSpaceAIPDisseminator up to the AbstractMETSDisseminator, so that the
method could be inherited to all *METSDisseminator classes)
Once committed, anyone should be able to perform additional testing by
performing requests to OAI-PMH similar to:
http://localhost:8080/oai/request?verb=ListRecords&metadataPrefix=mets
I'll also make sure to update our Documentation, and replace all references to
the METSExport class before closing this issue.
> 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
>
>
> 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
