search

sul-dlss-deprecated / dor-services

Common services, models, and utility classes used by the Stanford Digital Repository (DOR == Digital Object Registry)
Other
8 stars 4 forks source link

Argo status reporting does not match with actual workflow status #650

Open vivnwong opened 4 years ago

vivnwong commented 4 years ago

Ben noticed that there are still issues with Argo status reporting does not match with actual workflow status when timestamps are the same: https://argo.stanford.edu/catalog?all=true&f%5Bprocessing_status_text_ssi%5D%5B%5D=Unknown+Status

A specific example: https://argo.stanford.edu/view/druid:bm064hp654, it is in "unknown status" but it is able to be opened for modification.

May be related to https://github.com/sul-dlss/dor-services/issues/642

jcoyne commented 4 years ago

@vivnwong I can't go to https://argo.stanford.edu/view/druid:bm064hp654 does it work for you?

blalbrit commented 4 years ago

@jcoyne - should be https://argo.stanford.edu/view/druid:bm064hp6548 (missing final digit previously)

jcoyne commented 4 years ago

That says "v4 Unknown Status", but there are no v4 workflow steps. Could that be the problem?

blalbrit commented 4 years ago

I suspect you're right, and also suspect that the 60 or so objects currently in Unknown status are as a result of https://github.com/sul-dlss/argo/issues/1147 . I don't have the bandwidth to do the analysis on those, but should anyone be able to investigate further, start from this search: https://argo.stanford.edu/catalog?all=true&f%5Bprocessing_status_text_ssi%5D%5B%5D=Unknown+Status and examine the objects that are NOT version 1 (those are truly Unknown Status b/c they are ETD parts that get assembled into valid objects elsewhere).

Screenshot 2019-08-05 20 50 33

Those may all be the same issue described in #1147.

jcoyne commented 4 years ago

So, can we call this a duplicate of sul-dlss/argo#1147 and close it?