MediaHaven Record Status

Introduction

An object has a lifecycle going through multiple phases and statuses starting from ingest, through evaluation and finally its publication. From version 24.1 we have added an extra step in the lifecycle: archive.

Graph

Record Phase

	Record Phase	Description	Required function Functions for Accessing Records \| Functions	Example	Since

	Record Phase	Description	Required function Functions for Accessing Records \| Functions	Example	Since
1	Concept	The concept phase is the initial phase for all objects during which there are ingested . Even autopublished obejcts still go through these steps after which there published.	`ACCESS_PHASE_CONCEPT`	`Draft.Valid` `Rejected`
2	Published	The published phase is the main phase for object. During this phase objects are optionally shared through https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3915186208 or portals to the outside world. Once published the objects can no longer return to the concept phase.	`ACCESS_PHASE_POBLISHED`	`Published` `Destructed`
3	Archive	This optional terminal phase is meant to make objects no longer broadly available to the outside world or the typical users. Administrators or other authorized users can still access these objects. Once archived the objects can no longer return to the published phase.	`ACCESS_PHASE_ARCHIVE`		`24.1`

Record Status

	Record Status	Record Phase	Description	Module	Since

	Record Status	Record Phase	Description	Module	Since
1	`New`	`Concept`	Initially, all objects have this status, until they are picked up by the workflow during ingest. Intellectual objects created with no initial children directly have status `Draft.Valid` or `Draft.Invalid`.	Core
2	`Uploading`	`Concept`	When using https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4555931652, the data object and its original representation will have this status, until the resumable upload is completed, after which the status becomes `New`.	Core	`25.1`
3	`Processing`	`Concept`	Objects acquire this status as first step during the ingest workflow. Hence if many objects are queued for ingest they will remain in the status `New` until picked up by the ingest workflow.	Core
4	`Draft.Valid`	`Concept`	After ingest is completed, the object acquires this status if all its metadata is valid. Only such valid objects can go to the next phase `Published`.	Core
5	`Draft.Invalid`	`Concept`	After ingest is completed, the object acquires this status if some of its metadata is invalid (e.g. missing required field)	Core
6	`Rejected`	`Concept`	When the validation of the object fails during ingest (e.g. blacklisted format), it requires the terminal status `Rejected`. Rejected objects are automatically logically deleted after 30 days.	Core
7	`Published`	`Published`	This is the adult phase & status in the lifecycle of the object. Only published objects are available for embedding and sharing.	Core
8	`ApprovedForDestruction`	`Published`	The object is now approved for destruction and will be destructed at some time in the future by using one of the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3949297684named `Governance.AutomaticDestruction`.	MediaHaven as e-Depot	`24.1`
9	`Destructed`	`Published`	https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4137254971 is a terminal status from which there is no return. It is achieved by deleting all (grand)children that are representations after which the object acquires this status.	Core	`24.1`