Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: draw.io diagram "RecordStatuses" edited

...

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

Drawio sketch
mVer2
simple0
zoom1
inCommentsimple0
pageIdinComment40829583550
custContentId4082565160
diagramDisplayNamepageIdRecordStatuses4082958355
lbox1
diagramDisplayNameRecordStatuses
contentVer15
revision15
baseUrlhttps://mediahaven.atlassian.net/wiki
diagramNameRecordStatuses
pCenter0
width9941127
links
tbstyle
height470472

Record Phase

Record Phase

Description

Required function

https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3607855105/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

Rejceted

Rejected

2

Published

The published phase is the main phase for object. During this phase objects are optionally shared through /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.

Destructed

ACCESS_PHASE_ARCHIVE

24.1

Record Status

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 /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

34

Draft.InvalidValid

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

45

Draft.ValidInvalid

Concept

After ingest is completed, the object acquires this status if some of its metadata is invalid (e.g. missing required field)

Core

56

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

67

Published

Published

This is the adult phase & status in the lifecycle of the object. Only published objects are available for embedding and sharing.

Core

78

ApprovedForDestruction

ArchivePublished

The object is now approved for destruction and will be destructed at some time in the future through by using one of the /wiki/spaces/CS/pages/3949297684named TimersGovernance.DestructionAutomaticDestruction.

MediaHaven as e-Depot

24.1

89

Destructed

Archive

Destruction Published

/wiki/spaces/CS/pages/4137254971 is a terminal status from which there is no return. It is achieved by either deleting all (grand)children that are representations or flat data objects, after which the object acquires this status. As of 24.1 the only way to reach this status is through the module “MediaHaven as e-Depot”.

Core

24.1