CRUD User Interface

[metaweidner]

Use cases:

1. I want to mint an ARK and add ERC info for a vocabulary term created in Cedar.
2. I want to update the ERC info for a vocabulary term in Cedar.
3. I want to update the ERC info for a digital object in Armand: e.g. an object that was redacted, reuploaded, and now has a new URL.
4. I want to delete a batch of ARKs. Perhaps a search interface with the ability to sort by date uploaded and check boxes to select ARKs to delete. (The Delete part might not be a good idea in the long run, as it is generally bad linked data practice to destroy a URI after it's been minted.)

[seanlw]

Since Cedar is the one managing vocabularies, it would be possible to have it integrated to work with Greens using the API. This will leave one system responsible, instead of a workflow that involves working in multiple places. Same goes with Armand. #4 worries me for the same reasons listed in the enhancement. If a ARK should ever be removed it is because the object itself was removed, correct? Wouldn't it be handled by the management system integrated with Greens to handle the ARKS properly and avoid human error?

My opinion is that Greens should have very little UI elements and be controlled through the APIs from other systems managing the objects.

[metaweidner]

I like the idea of having the access systems hook into the minter via the API. Split into three separate issues.

Armand:

• update ERC: https://github.com/uhlibraries-digital/armand/issues/1

Cedar:

• mint ARK: https://github.com/uhlibraries-digital/cedar/issues/1
• update ERC: https://github.com/uhlibraries-digital/cedar/issues/2