Hi all,
I’m testing bulk / batch access control updates in DSpace 9.x.
My goal is to grant READ access at the Collection level and have it propagate through the repository objects include all bitstreams. After running the process, I found:
This becomes a problem in our UI customization, because the bitstream URL is not visible to user even the READ privileges already granted to the collection, item and bitstream. It is so time consuming to go into every item and grant the BUNDLE READ privilege one by one.
I’d like to confirm:
Thanks in advance.
Regards,
Martin So
HKUST Library
Hi Martin,
I'm not sure what the expected behavior is regarding bundles, but I had a similar problem before the bulk/batch mechanism was implemented.
At that moment I implemented it as a curation task to give READ permissions to collections and all nested elements to anonymous users.
We're still using it (instead of the built in bulk mechanism) since it works for us.
See
https://github.com/sistedes/dspace.server/blob/dspace-7.6.1-sistedes/dspace-api/src/main/java/org/dspace/ctask/general/MakePublic.java
https://github.com/sistedes/dspace.server/blob/dspace-7.6.1-sistedes/dspace/config/modules/curate.cfg
Hope it helps,
Abel
--
All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/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...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/0d6e1379-fe5b-4c8e-a83f-0a1494c80373n%40googlegroups.com.
-- Abel Gómez Llana, PhD ab...@gomez.llana.me https://abel.gomez.llana.me