[ https://jira.duraspace.org/browse/DS-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Masár updated DS-909:
--------------------------
Status: Volunteer Needed (was: Received)
> Collection DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ handling
> ----------------------------------------------------------------
>
> Key: DS-909
> URL: https://jira.duraspace.org/browse/DS-909
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.7.1, 3.0
> Environment: Tested on 1.7.1 xmlui Mirage on demo.dspace.org
> Reporter: Claudia Jürgen
> Priority: Major
>
> During the creation of a collection and the edit there is only one option in the rights panel to limit the access to a collection, this will affect both the DEFAULT_ITEM_READ and the DEFAULT_BITSTREAM_READ.
> One can edit the settings seperately via the rights management.
> Ok, this might be considered as different behaviour between the jspui and the xmlui, but there is one more issue.
> If a collection got different settings, which one can achieve via the rights management or might have inherited, e.g.
> DEFAULT_ITEM_READ none
> DEFAULT_BITSTREAM_READ group or eperson
> then there is no possibility to edit the setting at all via the collection edit panel.
> Furthermore it is displayed that the item got no access restrictions even if the bitstream access is restricted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|