-
Notifications
You must be signed in to change notification settings - Fork 4
Version loss after closing new version. #148
Comments
Verified that the broken versionMD was at the root of this particular object problem. I have found no other Hydrus objects in a similar state and assume that this was an ephemeral problem. We'll track versioning in Hydrus for a bit, but have seen no other errors in the last few days. |
Actually - this looks like an ongoing problem now. See https://argo.stanford.edu/view/druid:vq436sq9834 and https://argo.stanford.edu/view/druid:hm222bn8688 for instance. Both done today, between 12 and 1. To characterize the problem, when a new version gets opened in Hydrus, it is getting an incomplete versionMetadata stanza which puts it into an "unknown status". The user in the Hydrus app gets a HTTP ERROR 500. When we try to repair the object on the Argo side, we then see the behavior noted above. @cbeer and @jcoyne - I would imagine that 500 is being logged somewhere. |
Given: An existing Hydrus object with multiple versions
When: I open a new version on the object in Hydrus, and make no changes, then close the version
Then: all the version entries in versionMetadata are erased
What should happen: ???
It this is believed to be a regression, when was the last time it worked correctly?
The text was updated successfully, but these errors were encountered: