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

Joseph Rhoads commented on DS-819:
----------------------------------

I meant to add that I have time and am willing to work on this but I will need 
a bit of guidance.

> Metadata Masking
> ----------------
>
>                 Key: DS-819
>                 URL: https://jira.duraspace.org/browse/DS-819
>             Project: DSpace
>          Issue Type: New Feature
>          Components: DSpace API
>            Reporter: Joseph Rhoads
>
> Dear Dspace community,
> I'm working on a project that needs to have different layers of access to 
> metadata fields.  (ie.  Only certain people/groups should have access to 
> certain metadata fields).  I'm wondering if any in the dspace community have 
> any ideas or experiences with this sort of thing?  I'm gonna throw out some 
> ideas to see if anyone is interested.
> I know that there are currently a couple of options related to items access,
> +  You can let anonymous users view some info in the search/browse results
> +  Then approved users/groups can have full-item read access (minus fields 
> that are designated for administrators)
> +  Administrators can see all fields (including those designated 
> metadata.hide..... in the dspace.cfg file.)
> What I'm thinking about includes the following:
> + Adding the ability to create masks or streams of masks that can be applied 
> at the community or collection level, and to specific groups.
> + Each mask would simply be a set of (metadata key, boolean value) pairs
> + I think collection administrators should be able to edit the masks though 
> the web interface
> + And that the OAI indexing should be viewed as another group or person for 
> this purpose.
> I have some questions:
> + Should the mask be on the display end(post SQL request) or the request 
> end(pre SQL request)?
> + Presumably these masks would be persistent, where should they be stored?
> This topic is related to the following JIRA issues
> https://jira.duraspace.org/browse/DS-800
> https://jira.duraspace.org/browse/DS-716
> https://jira.duraspace.org/browse/DS-655

-- 
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 modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to