Retention custom field #66
Description
Rather than managing retention data externally, could we update items with a cca:retention custom field? Is this the most appropriate way to handle that rather than, say, an external spreadsheet or a separate search index?
We can hide the field on the deposit form so it can only be updated programmatically.
- RESEARCH - can we conditionally display a field's value only to administrators? Recall that the field will be visible in exported metadata
FIeld Structure
Open-ended dict? This might make retrieval more difficult that it needs to be, since we might want to index some fields as text and some as keyword. Simplest:
updated: Optional[datetime] = None
status: Optional[Literal[None, 'reviewed', 'to be deleted', 'retained', 'error']] = None
note: str = ""More complex, we could retain a log of actions, though I fear it'd grow large with many repeat "reviewed" actions. More standardized, we could implement PREMIS.
We may want the status to be an integer code to hide its meaning from end users.
This is low priority and not on any milestone because it will be years before we undergo a round of retention actions in the new system.