[
https://jira.duraspace.org/browse/DS-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue resolved DS-950.
----------------------------
Resolution: Won't Fix
Fix Version/s: (was: 1.8.0)
Marking this feature as "Won't Fix" for the reasons listed in the above
comments.
Essentially, the Crosswalks that OAI-PMH relies upon are not compatible with
the MetadataExposure class (which handles the metadata.hide.* settings). Until
MetadataExposure is either enhanced or more likely replaced (see DS-800), this
ticket is too problematic.
If at a later time we determine this enhancement can be made safely (without
affecting other parts of DSpace), we can always reopen this ticket (or create a
new, more appropriate ticket).
> Update OAI-PMH to fully obey 'metadata.hide.SCHEMA.ELEMENT.QUALIFIER'
> configuration settings
> --------------------------------------------------------------------------------------------
>
> Key: DS-950
> URL: https://jira.duraspace.org/browse/DS-950
> Project: DSpace
> Issue Type: Improvement
> Components: OAI-PMH
> Affects Versions: 1.7.0, 1.7.1, 1.7.2
> Reporter: Tim Donohue
> Assignee: Tim Donohue
>
> This improvement came up as a sub-part of DS-708 (Deprecate & Remove old
> 'org.dspace.app.mets.METSExport' class)
> Essentially, most of the OAI-PMH interface does not obey the
> metadata.hide.SCHEMA.ELEMENT.QUALIFIER settings in dspace.cfg. This is even
> detailed in the dspace.cfg notes that say:
> ##### Hide Item Metadata Fields #####
> # Fields named here are hidden in the following places UNLESS the
> # logged-in user is an Administrator:
> # 1. XMLUI metadata XML view, and Item splash pages (long and short views).
> # 2. JSPUI Item splash pages
> # 3. OAI-PMH server, "oai_dc" format.
> # (NOTE: Other formats are _not_ affected.)
> # To designate a field as hidden, add a property here in the form:
> # metadata.hide.SCHEMA.ELEMENT.QUALIFIER = true
> #
> # This default configuration hides the dc.description.provenance field,
> # since that usually contains email addresses which ought to be kept
> # private and is mainly of interest to administrators:
> metadata.hide.dc.description.provenance = true
> The idea here is to actually make ALL of the OAI-PMH server's formats
> (oai_dc, mets, rdf, etc) obey this setting. In addition, this allows us to
> cleanup the old "oai.mets.hide-provenance" setting which was previously used
> by the METS/MODS format from OAI-PMH (see DS-708)
--
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
------------------------------------------------------------------------------
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC can
improve internal communications as well as offer faster, more efficient ways
to interact with customers and streamline customer service. Learn more!
http://www.accelacomm.com/jaw/sfnl/114/51426253/
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
