Now that I fully understand the use case below - I have the following questions
a) is it correct that this is not possible ? b) do you still collect use cases/user stories for the new UI ? - this is something that would be a good addition Monika — Monika Mevenkamp Digital Repository Infrastructure Developer Princeton University Phone: 609-258-4161 Skype: mo-meven > On Sep 14, 2016, at 3:14 PM, Evgeni Dimitrov <[email protected]> wrote: > > Yes Monika, I know - this is what I am doing now. And what I want is to > delegate ONLY this to somebody else. My reason to hope that it could be > possible is this: > - the policies are attached to resources > - the policies say who can perform an action on the resource (e.g. ADD/REMOVE) > - the resource can be any of the DSpace object types: Bitstream: 0; Bundle: > 1; Item: 2; Collection: 3; Community: 4; Site: 5; Group: 6; Eperson: 7. > > This is the theory. This is what the DSpace-Manual says. And I am asking now > - does this exist in reality? Can I attach a policy to a group (saying who is > authorized to ADD/REMOVE to this group). > > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/dspace-tech > <https://groups.google.com/group/dspace-tech>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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.
