aaron-collier
commented
1 month ago @andrewjbtw The first object in DSA has the following RepositoryObject (opened_version_id is set)
#<RepositoryObject:0x00007feda6bcbab0
id: 3096523,
object_type: "dro",
external_identifier: "druid:hd886sp9284",
source_id: "branner:collins_MCE_OM4G_2015.tif",
lock: 0,
created_at: Tue, 22 Nov 2022 19:29:29.184754000 UTC +00:00,
updated_at: Wed, 09 Aug 2023 21:39:31.171153000 UTC +00:00,
head_version_id: 7181007,
last_closed_version_id: 7181002,
opened_version_id: 7181007>Looking at a different object that isn't showing open:
#<RepositoryObject:0x00007feda711d9a0
id: 4555287,
object_type: "dro",
external_identifier: "druid:rm242zg2446",
source_id: "rbi:BRUNET",
lock: 0,
created_at: Tue, 06 Nov 2018 22:32:48.616000000 UTC +00:00,
updated_at: Tue, 23 Apr 2024 20:42:03.530989000 UTC +00:00,
head_version_id: 11402884,
last_closed_version_id: 11402884,
opened_version_id: nil>opened_version_id is nil. I wonder if it's as easy as setting opened_version_id to nil and the last_closed_version_id to head_version_id on these objects
andrewjbtw
There are 234 geo items that have 1 version in DSA but 2 versions in preservation. This will result in a version mismatch error if these are reaccessioned because DSA will try to send the next version as version 2 and preservation expects the next version to be 3. See #5128 for 27 items where this issue has already occurred.
Example: https://argo.stanford.edu/view/druid:hd886sp9284
Oddly, Argo shows these items as "v2 Accessioned" even though a report from DSA says there's only 1 version for each item:
And the workflow service has data for when version 2 was accessioned:
However, the items show with the "lock" icon unlocked, which implies that the item should have a status of Opened.
If you try to close the version by "locking" it, the version that will be closed is version 2. Closing will kick off accessionWF, which will then throw the version mismatch error.
Remediation steps
I suspect that all we need to do is increment the version in DSA and make sure these items get a status of "Accessioned". Then the next accessioning update will create version 3.