MetadataExposure hides fields except for System Admins - this should extend to
Community and Collection Admins
--------------------------------------------------------------------------------------------------------------
Key: DS-655
URL: http://jira.dspace.org/jira/browse/DS-655
Project: DSpace 1.x
Issue Type: Improvement
Components: DSpace API
Affects Versions: 1.6.2, 1.6.1, 1.6.0
Reporter: Bill Hays
Priority: Minor
MetadataExposure provides an exclusion for SystemAdmins but not Community and
Collection admins who are actually more likely to need access to metadata that
is restricted to public view. For instance, the default metadata field for
hiding is dc.description.provenance which is in the purview of Community and
Collection admins at my location.
Caveat: The comments in the class state that it is important to have a very
efficient mechanism and to extend the class by calling
AuthorizeManager.isAdmin(context, dso) would have a much greater overhead than
the current AuthorizeManager.isAdmin(context). And for OAI this
recommendation is not applicable.
The hidden metadata is still available to all admins using the EditMetadata
capability, yet this is a burden with the provenance field since it can be
quite large.
--
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
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
