[
https://jira.duraspace.org/browse/DS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19032#action_19032
]
Robin Taylor commented on DS-655:
---------------------------------
With regards to making either DCValue or MetadataValue a DspaceObject - Ideally
we would choose MetadataValue since its viewed as a replacement for the
deprecated DCValue, but MetadataValue is not used anywhere. Even Item only has
methods that return DCValues rather than MetadataValues. Until such time as
DCValue is truly replaced by MetadataValue throughout the code its not a viable
option. So what about DCValue ? It doesn't have all the required methods to be
a DSpaceObject eg. find(...). I could add these methods but its a deprecated
Class. We need to resolve the DCValue vs MetadataValue issue before deciding
which one should be a DSpaceObject.
> MetadataExposure hides fields except for System Admins - this should extend
> to Community and Collection Admins
> --------------------------------------------------------------------------------------------------------------
>
> Key: DS-655
> URL: https://jira.duraspace.org/browse/DS-655
> Project: DSpace
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.6.0, 1.6.1, 1.6.2
> Reporter: Bill Hays
> Assignee: Robin Taylor
> Original Estimate: 16 hours
> Remaining Estimate: 16 hours
>
> 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:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
