-
Notifications
You must be signed in to change notification settings - Fork 4
Change logic that determines object status #221
Comments
This would correct an instance where something like dpgImageWF, if added later with a new lifecycle=registered, would not pre-empt the original lifecycle=registered. |
@LynnMcRae You are not intending to differentiate the typo'd version of |
nope, "registered" by any other name should not exist anywhere but in my hasty typing sans spell-check. |
@peetucket did PR #644 or @jmartin-sul did your PR address this ancient ticket? |
@ndushay, i don't recall putting up any PRs that addressed this issue. |
sorry @jmartin-sul i probably garbled something or other in my mind. I've been looking at a lot of repos and issues and PRs and it all runs together sometimes. |
totally understandable, @ndushay! i had to go look at my closed dor-services PRs to make sure i hadn't forgotten something myself 🙂 |
the current logic is that the latest lifecycle wins … but maybe it should be earliest instance of "registered” then the latest instance of of submitted/accessioned/opened
per @LynnMcRae
The text was updated successfully, but these errors were encountered: