[
https://jira.duraspace.org/browse/DS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Taylor updated DS-880:
----------------------------
Fix Version/s: 1.8.0
> Better documentation for permissions
> ------------------------------------
>
> Key: DS-880
> URL: https://jira.duraspace.org/browse/DS-880
> Project: DSpace
> Issue Type: Documentation
> Components: Documentation
> Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1,
> 1.8.0
> Reporter: Alex Lemann
> Fix For: 1.8.0
>
>
> Questions:
> How are permissions inherited from community->sub
> community->collection->item->bitstream
> Both from the perspective of how permissions stacks effect
> and how do permissions for parents affect default permissions for children
> if at all?
> What does read/write/add/remove/admin mean at each level?
> Can I list items in a collection I don't have read access to?
> Can I see sub communities of a community I don't have read access to?
> What does it mean to be able to add or write to a collection?
> Are there tricks for bulk updating security policies for items, communities,
> collections, bitstreams, etc.
> Could some of this be made clearer by hiding nonrelevant permissions at some
> levels?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
