[
https://jira.duraspace.org/browse/DS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18882#action_18882
]
Joseph Rhoads commented on DS-819:
----------------------------------
Here's my understanding of the current state of things:
The current (as of Dspace 1.7) form of metadata masking is controlled by the
static class MetadataExposure
located at
[dspace_source]/dspace-api/src/main/java/org/dspace/app/util/MetadataExposure.java
The class populates a nested static HashMap of the structure
<schema,<element,qualifier>>
whose structure is obtained from the dspace.cfg file.
Once the static class has been initialized, it's primary method, isHidden(), is
called repeatedly by each of the following interfaces to see if a metadata
field is hidden
It's used in the XMLUI at
[dspace_source]/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/objectmanager/ItemAdapter.java
Line: 261
JSPUI at
[dspace_source]/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java
Liness: 444, 623
and the OAI harvester at
[dspace_source]/dspace-oai/dspace-oai-api/src/main/java/org/dspace/app/oai/OAIDCCrosswalk.java
Line 196
> 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
