Events
Structure
The event name 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, profiles could be added.
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 | Difference | Description |
|---|---|---|---|---|---|---|
|
|
|
|
|
| Transcode job is created |
|
|
|
|
|
| Transcode job is finished |
|
|
|
|
|
| Retranscode 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 |
|
|
|
|
|
|
|
|
|
|
|
|
| Because the MD5 was unknown when creating the record (when using |
|
|
|
|
| Record is created | |
|
|
|
| Metadata of record is updated | ||
|
|
|
|
| Record has been published from the ingest space or auto-published | |
|
|
|
|
|
| Record has followed its to its end |
|
|
|
|
|
| Technical metadata and preview path are updated when the transcoding completes |
|
|
|
|
|
| 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 |
|
|
|
|
|
| Fixity of the file will be checked by exporting it |
|
|
|
|
|
| Fixity check is finished |
|
|
|
|
|
| Generated when a is done for the original (representation) |
|
|
|
|
|
| Generated when a is done for the access representation or browse |
Metadata Update
The column “Metadata Update” indicates that, when true, this event will also cause the record to be updated in the index and the metadata field
Administrative.LastModifiedDateto be changed accordingly →The timestamp of the event and
Administrative.LastModifiedDatecan have the exact same value or differ on the order of milliseconds.The field
Administrative.LastModifiedDateis changed for the record and all its fragments when the metadata is updatedWhen in case of an update only
DescriptiveorDynamicfields are changed, then only that particular fragment is updated insteadWhen changing metadata fields outside the families
DescriptiveandDynamic, e.g. when publishing the fragment (familyAdministrative) or changing the permissions (familyRightsManagement), then the record and all its fragments are updatedSee for information about the different families