Hello, Lucas, You might want to take a look at the Resource Policy endpoint for the REST API: https://github.com/DSpace/RestContract/blob/dspace-7_x/resourcepolicies.md
One way to solve this is by creating a script to authenticate with a DSpace service user with admin privileges and batch change your collections policies based on one or several rules. Diego F. Ucha Reach Solutions <https://www.reachsolutions.com.br/en/institutional-repositories/> On Tuesday, April 2, 2024 at 2:08:38 PM UTC-3 Hutchinson, Alvin wrote: > Hello, Lucas. > > > > If I’m not mistaken, the ability to retroactively change policies for > items held in Dspace collections is not something that is possible. > > > > I have asked about this before (although it’s been a couple of years) but > learned that it can’t (or at least couldn’t at the time) be done. > > > > Please let us all know if you learn otherwise, > > > > Alvin Hutchinson > > Smithsonian Libraries and Archives > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *[email protected] > *Sent:* Tuesday, April 2, 2024 12:06 PM > *To:* DSpace Community <[email protected]> > *Subject:* [dspace-community] Assistance with Retroactive Collection > Policies in DSpace > > > > *External Email - Exercise Caution* > > Dear DSpace community, > > I am writing to request your assistance and guidance with a challenge we > are facing regarding the application of retroactive collection policies in > our DSpace repository. > > Currently, we are working with version 7.5 of DSpace and manage a > repository with approximately 50,000 deposits. We are seeking to implement > new access and restriction policies in our collections to ensure the > security and compliance of our repository. However, we have encountered > difficulties in applying these policies to old items already deposited in > our collections. > > While the policies are functioning as expected for new deposits, we have > been unable to find an effective way to retroactively apply these policies > and consistently enforce them on existing items in our collections. Our > attempts thus far have not been successful, and we are facing technical > hurdles in this process. > > We would like to leverage the expertise and experience of our DSpace > community to better understand best practices and possible solutions for > addressing this issue. If anyone has faced a similar challenge or has > insights on how to approach the application of retroactive collection > policies efficiently, we would greatly appreciate if you could share your > experiences and knowledge with us. > > Additionally, any documentation, guides, or related resources that could > assist us in this process would be extremely helpful. > > We sincerely appreciate your help and collaboration. We look forward to > hearing your suggestions and guidance on this matter. > > Warm regards, > > Lucas. > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" 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-community/f0de3f03-6c08-41ed-bca0-8517a8dfeed2n%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-community/f0de3f03-6c08-41ed-bca0-8517a8dfeed2n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Community" 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-community/a016f011-ab84-4b88-a281-076eca30401fn%40googlegroups.com.
