Bulk Access Control on D7.6.3 - Process missed updating policy for some items in the collection

[Julia Gilmore]

Hi there, 

We are working with an institution who recently ran a Bulk Access Control job from the UI to add an item-level embargo for ~400 items in a collection. The process ran successfully (completed with no errors - screenshot attached) however only half of the items actually had the policy applied. 

Sample excerpt from the log file: 

2025-06-12 15:03:10.803 INFO bulk-access-control - 170 @ Replacing Item {UUID1} policy to access conditions:{embargo, start_date=2025-06-15} 2025-06-12 15:03:10.855 INFO bulk-access-control - 170 @ Replacing Item {UUID2} policy to access conditions:{embargo, start_date=2025-06-15} 2025-06-12 15:03:10.900 INFO bulk-access-control - 170 @ Replacing Item {UUID3} policy to access conditions:{embargo, start_date=2025-06-15} 2025-06-12 15:03:10.948 INFO bulk-access-control - 170 @ Replacing Item {UUID4} policy to access conditions:{embargo, start_date=2025-06-15}

Reviewing the logs, only half of the UUIDs from the collection are in the list. These items received the updated policy. The missing items did not. 

Is there a reason or known issue why the process would miss half of the items in the collection? Should we rerun the process to update the remaining items? 

Thanks very much, 

Julia

[Carolyn Sullivan]

I wonder if this is connected to the problems described here:  https://github.com/DSpace/DSpace/issues/9208 .  They mention some items not receiving a policy in a bulk update operation, while others received duplicate policies

 If so, it looks like it was fixed a month ago for 7.6.4.  Let me know how it pans out.

Carolyn.