On Fri, 2018-11-02 at 11:56 +0100, Michael Plate wrote: > Hi Tony, > > > Am 02.11.18 um 10:45 schrieb Tony Brian Albers: > > No, not about actual living beings, but Write Once Read Many. > > > > Is it possible to make a collection only accept deposits and not > > let > > the owner delete what he/she has deposited? > > […] > > it is possible, if I understand you correct. > We use a LDAP-based group wich can only submit to one collection and > there is no read access by default. > > I think it was this way, but you have to fiddle around a bit... > - create a collection > after that, assign roles - you should have a COLLECTION_XXX_SUBMIT > and > COLLECTION_XXX_DEFAULT_READ group after > - add some steps for the people to work with the workflow > - use Access Control / Authorizations and add a new policy "ADD" for > the > group or users who should submit > - set DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ to the people > doing > the workflow > - remove READ for Anonymous > > after submission and workflow you have to move the item to the target > collection, check "Inherit policies" and move it. > > I hope this is the right way, I struggled a bit with it. > >
Thanks Michael, That looks doable, but pretty inconvenient -I'll have a closer look. /tony -- -- Tony Albers Systems Architect Systems Director, National Cultural Heritage Cluster Royal Danish Library, Victor Albecks Vej 1, 8000 Aarhus C, Denmark. Tel: +45 2566 2383 / +45 8946 2316 -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
