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 Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ae44f103-1e77-4b0e-87c3-386a8729fc31n%40googlegroups.com.

Reply via email to