it looks like the reason for the READ permission of an embargoed item being set
to the collections READ permission upon archival resides in the
DefaultEmbargoSetter implementation
https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/embargo/DefaultEmbargoSetter.java#L116
<https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/embargo/DefaultEmbargoSetter.java#L116>
List<Group> authorizedGroups =
getAuthorizeService().getAuthorizedGroups(context, owningCollection,
Constants.DEFAULT_ITEM_READ);
is that intentional ?
it seems to me that this should be DEFAUT_BITSTREAM_READ would be a better
choice
Monika
________________
Monika Mevenkamp
[email protected]
http://mo-meven.tumblr.com/
http://mcmprogramming.com/mo.meven/
> On Jun 27, 2017, at 3:35 PM, Monika Mevenkamp <[email protected]> wrote:
>
> Here is what happens
>
> I import an item from an AIP into a workflow, where the item has embargo term
> and lift dates in the future
>
> Looking at the authorizations of bitstreams after archival I see that the
> bundle and bitstreams get the DEFAULT_BITSTREAM_READ group as well as the
> items READ group.
>
> I want them to get the DEFAULT_BITSTREAM_READ group only.
>
> How can I do that ?
> Is there a setting to block assignment of the ITEM READ group ?
> Is there a way that I can run a curation task right after archival ?
>
> Thanks for any kind of tips
>
> Monika
>
> ________________
> Monika Mevenkamp
> [email protected]
>
> http://mo-meven.tumblr.com/
> http://mcmprogramming.com/mo.meven/
>
>
>
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
