Hi all, I was unaware that folks are seeing issues with the "Inherit policies of the destination collection" when moving an Item between Collections. I'd recommend someone report this to our ticketing system so that we can look for a volunteer to address it: https://jira.duraspace.org/projects/DS/ . When creating a ticket, please give a step-by-step example of what isn't working, as that will help someone reproduce & debug the issue.
If creating a collection and moving all the items isn't working, you also could use the "Advanced Policy Manager" from the DSpace Admin UI to do a bulk replacement of the policies on those 100 items. This Advanced Policy Manager isn't the most "user friendly" feature, but it will work to allow you to bulk remove existing policies and bulk add the new ones. Here's a step-by-step guide that our team wrote for the DSpaceDirect service (hosted by DuraSpace): https://wiki.duraspace.org/display/DSpaceDirectKB/Getting+Started+How-To#GettingStartedHow-To-Bulk/BatchPermissionsChanges(Advanced) Hopefully that helps give another option on how to resolve this, since it sounds like the inheritance of collection policies when moving items isn't working as expected. Tim On Sat, Jul 6, 2019 at 10:00 AM Evgeni Dimitrov <[email protected]> wrote: > I think that up to DSpace 6.2 "Inherit policies of the destination > collection" does not work. > I don't know how it is in DSpace 6.3. > > > On Friday, July 5, 2019 at 12:11:36 PM UTC+3, Arunendra M. Biswas wrote: >> >> A reply would be helpful. >> >> On Wednesday, July 3, 2019 at 7:36:04 PM UTC+5:30, Arunendra M. Biswas >> wrote: >>> >>> Using Dspace 5.9. >>> I created a collection with default authorization and uploaded 100 items >>> with the default authorization. >>> But then, the client decided to allow the READ policy only and remove >>> the DEFAULT_BITSTREAM_READ policy for Anonymous group. >>> >>> Reading across the forum, I learnt that the easiest way would be to >>> create another collection with this required authorization and move the 100 >>> items from old to this newly created collection, selecting "Inherit >>> policies of the destination collection". >>> >>> I did, but the older DEFAULT_BITSTREAM_READ policy for Anonymous group >>> did not get overridden. The items can be still opened as Anonymous. >>> >>> Help please. >>> >>> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/9cbc95be-ccc0-499a-972c-9a6ac9e45caf%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/9cbc95be-ccc0-499a-972c-9a6ac9e45caf%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CACKSJ9OYmdSY8KiSTaSZUW8V_m_RH1hkhvuxK4AVf-yk%2B%3DNHPg%40mail.gmail.com.
