Hi Tuan, The "WITHDRAW_READ" policy action has a constant value of 12 defined here: https://github.com/DSpace/DSpace/blob/dspace-7_x/dspace-api/src/main/java/org/dspace/core/Constants.java#L168
So, I think you can query the database for all objects with that policy by doing: SELECT * from resourcepolicy where action_id=12; The "resource_type_id" column will be an object type constant, as defined here: https://github.com/DSpace/DSpace/blob/dspace-7_x/dspace-api/src/main/java/org/dspace/core/Constants.java#L21-L46 (e.g. Bundles will have resource_type_id=1) The "resource_id" column will give you the UUID of that object. Hopefully that helps, Tim On Tuesday, August 22, 2023 at 3:18:07 PM UTC-5 [email protected] wrote: > Thank you, Tim. I found out a little more details about our old data. > > It turns out folks were using the Authorizations feature, and they added a > WITHDRAWN_READ policy on the bitstream bundle. > > Is it possible to query the database for all the items with such policy > attached to them? If we can identify them, then we can migrate them > manually to the new Embargo function of DSpace. > > Thanks for you help, > Tuan > On Wednesday, August 16, 2023 at 3:11:27 PM UTC-4 DSpace Technical Support > wrote: > >> Hi Tuan, >> >> This same embargo functionality existed also in DSpace 6. You can see >> that area of the documentation is unchanged since DSpace 6: >> https://wiki.lyrasis.org/display/DSDOC6x/Embargo#Embargo-DSpaceEmbargoFunctionality >> >> That said, if you have really old style embargoes (from version 3 or >> earlier), there was/is a migration script to move them into the new embargo >> structure: >> https://wiki.lyrasis.org/display/DSDOC7x/Embargo#Embargo-Pre-3.0EmbargoMigrationRoutine >> >> That script has existed since around version 3 or 4. >> >> Tim >> >> On Thursday, August 10, 2023 at 6:35:05 AM UTC-5 [email protected] >> wrote: >> >>> Hi Tim >>> I've gone through that document. What about the records with embargo >>> from DSpace 6.x? We upgraded from 6.4 and items with embargo are not >>> lifted. Is there something we need to do to migrate those? >>> >>> Thanks, >>> Tuan >>> >>> On Wednesday, August 9, 2023 at 4:42:58 PM UTC-4 DSpace Technical >>> Support wrote: >>> >>>> Hi Tuan, >>>> >>>> The Embargo Lifter is no longer necessary. Embargoes are lifted >>>> automatically in DSpace. To understand how embargoes work in DSpace 7, >>>> please see this section of the documentation: >>>> https://wiki.lyrasis.org/display/DSDOC7x/Embargo#Embargo-DSpaceEmbargoFunctionality >>>> >>>> >>>> Tim >>>> On Wednesday, August 9, 2023 at 2:48:35 PM UTC-5 [email protected] >>>> wrote: >>>> >>>>> Hi everyone >>>>> >>>>> I can't seem to find any information on how to configure the embargo >>>>> lifter in DSpace 7.6. Is there something that need to run in cron or >>>>> something to lift expired embargo? The only thing I found is >>>>> https://wiki.lyrasis.org/display/DSDOC7x/Embargo >>>>> >>>>> Thanks, >>>>> Tuan >>>>> >>>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/a80ca6b8-46e6-4f87-b574-f1605f2923d8n%40googlegroups.com.
