Question: how can we deprecate the "Hydrus" APOs?

[andrewjbtw]

All H2 deposits use the Hydrus Ur-APO. Legacy Hydrus-origin deposits are still generally linked to the Hydrus-specific APOs, unless they've been updated from H2, in which case they are now associated with the Hydrus Ur-APO.

The Hydrus-specific APOs were used to control user permissions and other settings that are now taken care of within the H2 application. They also had a close relationship with "Hydrus collections": each Hydrus collection had its own "Hydrus APO" behind the scenes.

During the H2 build out, we concluded that there was no longer a reason to keep the Hydrus APOs as an active part of self-deposit system. But we still have hundreds, possibly over a thousand, items (and some collections) associated with Hydrus specific APOs. In the interest of making our data more consistent and manageable, we should take steps to remove the Hydrus APOs entirely and then decommission them, provided that we do not see other reasons to keep them.

I think we can do this by:

• changing the APOs on anything with a Hydrus-specific APO to the Hydrus Ur-APO
• decommissioning the Hydrus-specific APOs using the normal decommission process

However:

• we have to avoid modifying items in a way that will put them out of sync between SDR and H2. So we can't just open a new version in Argo and change the APO for each one, as the H2 items will run into version conflicts if updated in the future.
• it would be good to do a reality check if there is any other reason to use those specific APOs. Within SDR, the APO does still govern user access in Argo. Moving everything to the Hydrus Ur-APO would mean that anyone who can see self-deposit content can see all self-deposit content. That is the current situation with Argo access to Hydrus objects, but if we have use cases for silo-ing certain self-deposit collections to specific user group access in Argo, we would need a new way to do that.

[andrewjbtw]

This ticket is related to but not the same as removing the Hydrus APO facet. That can be done with an indexing change without changing the APO relationship.