[
https://jira.duraspace.org/browse/DS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20501#action_20501
]
Mark Diggory commented on DS-912:
---------------------------------
Immediate answer, no, you would have to write something that does the business
logic of rewriting the policies (for instance, maybe try to track
DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ changes an capture them in a
consumer that will update the permissions in all the Items of the Collection.
--- Notes for Architecture / Developers ---
If "DEFAULT_XXX" were implemented properly, the Item/Bitstream would inherit
default policies of the collection in AuthorizationManager, thus not needing to
attach the policy explicitly to all the items in the collection and/or rewrite
the policies related to the item when updating the collection default
policies...
Why we would want this:
1.) We want to still allow items in a collection to "override" defaults.
(Embargo etc)
2.) We don't want to have to worry about "overwriting" locally customized item
policies like ones enforcing "embargo" and we do not want to have to worry
about tracking these local settings explicitly in the code that might change or
enforce collection policies on the item (this even applies at the point the
Item is Installed into the Archive, they should have been assigned earlier in
the workflow/workspace so that the Reviewer has clear knowledge of the policies
enforced/wanted by the submitter)
3.) It we are always going to say that an Item has to be in a Collection...
then delegation makes sense because we've enforced container-ship in the first
place.
> Authorization policy
> --------------------
>
> Key: DS-912
> URL: https://jira.duraspace.org/browse/DS-912
> Project: DSpace
> Issue Type: Improvement
> Environment: Definition of authorization policies
> Reporter: Biblioteca Digital do Superior Tribunal de Justiça
>
> When applying a new policy for authorization of a collection of DSpace, this
> policy just going to be applied only to new items included in the collection.
> Items deposited before setting new policy remain with the policy previously
> defined. I wonder if it is possible to deploy the application for
> establishing a policy for all collection items, even items that were
> deposited before setting the new policy.
--
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
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
