[ 
https://jira.duraspace.org/browse/DS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21066#action_21066
 ] 

Tim Donohue edited comment on DS-708 at 7/11/11 9:03 PM:
---------------------------------------------------------

I've now split Peter's suggestion off into a separate issue: DS-950.

So, what I'd propose to do is the following:

(1) Fix DS-708 (this issue) for 1.8.0 by applying the attached patches above 
(unchanged).  This will cause the fix to DS-196 to temporarily "break", as the 
'dc.description.provenance' info will reappear in the OAI-PMH 'mets' format.

(2) Follow that up with a fix to DS-950 before 1.8.0, which will switch OAI-PMH 
to fully obey the 'metadata.hide.SCHEMA.ELEMENT.QUALIFIER' settings, as a 
replacement for DS-196.  This, in a sense will *replace* the old 
'oai.mets.hide-provenance' setting with the 
'metadata.hide.dc.description.provenance' setting.  This would also mean that 
the MODSDisseminationCrosswalk would now obey the 'metadata.hide.*' settings. 
(This is a variant of my "Option A" above).

Comments or further suggestions are welcome.  This seems like the most logical 
way to move forward, and to also ensure OAI-PMH obeys 'metadata.hide.*' 
settings, just like XMLUI &  JSPUI.

      was (Author: tdonohue):
    I've now split Peter's suggestion off into a separate issue: DS-950.

So, what I'd propose to do is the following:

(1) Fix DS-708 (this issue) for 1.8.0 by applying the attached patches above 
(unchanged).  This will cause the fix to DS-192 to temporarily "break", as the 
'dc.description.provenance' info will reappear in the OAI-PMH 'mets' format.

(2) Follow that up with a fix to DS-950 before 1.8.0, which will switch OAI-PMH 
to fully obey the 'metadata.hide.SCHEMA.ELEMENT.QUALIFIER' settings, as a 
replacement for DS-192.  This, in a sense will *replace* the old 
'oai.mets.hide-provenance' setting with the 
'metadata.hide.dc.description.provenance' setting.  This would also mean that 
the MODSDisseminationCrosswalk would now obey the 'metadata.hide.*' settings. 
(This is a variant of my "Option A" above).

Comments or further suggestions are welcome.  This seems like the most logical 
way to move forward, and to also ensure OAI-PMH obeys 'metadata.hide.*' 
settings, just like XMLUI &  JSPUI.
  
> 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
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to