Events
Structure
The event names are structured in three parts
CONCEPT.TYPE.SUB-TYPE
Example
RECORDS.UPDATE.PUBLISH
Currently, the only available concept is “RECORDS”. In the future other concepts such as users, and profiles could be added → https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4400775176.
API versus Monitoring
In the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/64258058 the events are shown using the “Legacy Name” while in the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/2447769640 it is always shown using the fully qualified name.
Overview
The column difference indicates if a https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4058742786 is included for events of this type or subtype.
Family | Name | Legacy Name | Since | Metadata Update | Diff | Description |
|---|---|---|---|---|---|---|
|
|
|
|
|
| Transcode job is created |
|
|
|
|
|
| Transcode job is finished |
|
|
|
|
|
| Retranscode job is created |
|
|
|
|
|
| Custom keyframe job is created |
|
|
|
|
|
| Export job is created |
|
|
|
|
|
| Export job is finished |
|
|
|
|
| File has successfully acquired the | |
|
|
|
|
|
| SIP was resubmitted while it is already archived based on the ExternalId |
|
|
|
|
|
| SIP was resubmitted while it is already processing based on the ExternalId |
|
|
|
|
|
| TO DO |
|
|
|
|
|
| Because the MD5 was unknown when creating the record (when using |
|
|
|
|
|
| TO DO |
|
|
|
|
|
| TO DO |
|
|
|
|
| Record is created | |
|
|
|
| Metadata of record is updated | ||
|
|
|
|
| Record has been published from the ingest space or auto-published | |
|
|
|
|
|
| Record has followed its https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4137254971 to its end |
|
|
|
|
|
| Technical metadata has been extracted |
|
|
|
|
|
| Technical metadata and preview path are updated when the transcoding completes |
|
|
|
| The ingest of the record is now fully completed and now has record status | ||
|
|
|
| The record has been permanently rejected | ||
|
|
|
| Contains the updates to the non-descriptive and non-dynamic fields that are shared with all pure fragments --> https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4668391481/Fragments#Metadata-Inheritance. | ||
|
|
| 25.4 |
|
| This event is added on an original representation when the version status changes to head. See https://mediahaven.atlassian.net/wiki/spaces/CS/pages/5124980740 for details. |
|
|
| 25.4 |
|
| This event is added on an original representation when the version status changes to tail. See https://mediahaven.atlassian.net/wiki/spaces/CS/pages/5124980740 for details. |
|
|
| 25.4 |
|
| This event is added on a data object when a new version of the original representation is created See https://mediahaven.atlassian.net/wiki/spaces/CS/pages/5124980740 for details. |
|
|
| 25.4 |
|
| This event is added on a data object when a new version of the original representation is rejected. See https://mediahaven.atlassian.net/wiki/spaces/CS/pages/5124980740 for details. |
|
|
|
|
|
| TO DO |
|
|
|
|
|
| TO DO |
|
|
|
|
|
| TO DO |
|
|
|
|
|
| Record is logically deleted |
|
|
|
|
|
| Logically deletion of record is undone |
|
|
|
|
|
| Record is permanently deleted and this delete can no longer be undone, all storage is reclaimed shortly afterwards |
|
|
|
|
|
| Virus check is performed |
|
|
|
|
|
| MD5 generated from file is compared with the reference |
|
|
|
|
|
| Format validation of the ingested TIFF image is performed using JHOVE |
|
|
|
|
|
| Conformance level of ingested PDF file is analyzed using veraPDF and compared with the configured reference profile |
|
|
|
|
|
| Fixity of the file will be checked by exporting it |
|
|
|
|
|
| Fixity check is finished |
|
|
|
|
|
| Specifies which tool determined the format and whether it is allowed --> https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4340187164 |
|
|
|
|
|
| Generated when a https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3708682241 is done for the original (representation) |
|
|
|
|
|
| Generated when a https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3708682241 is done for the access representation or browse |
|
|
|
|
|
| Share is created |
Properties
The properties of events are structured according to the https://www.loc.gov/standards/premis/v3/ Premis event standard.
Property | Description | Type | Example |
|---|---|---|---|
Identifier | A monotonically increasing number, unique for each event | Long | 9212604 |
IdentifierType | Unless the event has been provided externally, it will always have the value | String |
|
Concept, Type, Subtype | The event name has 3 constituents: | String |
|
Date | When the event occurred |