...
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 Destruction 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 Direct Downloads is done for the original (representation) | |||
|
|
| Generated when a Direct Downloads is done for the access representation or browse |
...