Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

Change logic that determines object status #221

Open
blalbrit opened this issue Jul 26, 2016 · 7 comments
Open

Change logic that determines object status #221

blalbrit opened this issue Jul 26, 2016 · 7 comments

Comments

@blalbrit
Copy link
Contributor

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

@LynnMcRae
Copy link

LynnMcRae commented Jul 26, 2016

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.

@atz
Copy link
Contributor

atz commented Mar 21, 2018

@LynnMcRae You are not intending to differentiate the typo'd version of resistrered, right?

@LynnMcRae
Copy link

nope, "registered" by any other name should not exist anywhere but in my hasty typing sans spell-check.

@ndushay
Copy link
Contributor

ndushay commented Aug 9, 2019

@peetucket did PR #644 or @jmartin-sul did your PR address this ancient ticket?

@jmartin-sul
Copy link
Contributor

@ndushay, i don't recall putting up any PRs that addressed this issue.

@ndushay
Copy link
Contributor

ndushay commented Aug 9, 2019

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.

@jmartin-sul
Copy link
Contributor

totally understandable, @ndushay! i had to go look at my closed dor-services PRs to make sure i hadn't forgotten something myself 🙂

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants