Events captured by the Bridge as part of the snapshot's history (CURRENT)
Event | Data* | Initiated By | Implementation Status |
---|---|---|---|
Snapshot Initiated |
| Bridge | complete, included in 1.6.0 release |
Snapshot Transfer to Chronopolis Complete |
| Bridge | complete, included in 1.6.0 release |
Snapshot Complete |
| Call to complete snapshot made by Intake Service Event captured by Bridge | complete, included in 1.6.0 release |
Request Restore Snapshot | initiating-user: <user email> restore-action: RESTORE_REQUESTED | Bridge complete, included in 1.4.0 release | |
Restore Initiated | restore-id: <restore-id> restore-action: RESTORE_INITIATED initiating-user: <request initiating user email> | Bridge complete, included in 1.4.0 release | |
Restore Completed | restore-id: <restore-id> restore-action: RESTORE_COMPLETED expiration-date: yyyy-MM-dd | Bridge | complete, included in 1.4.0 release |
Restore Expired | restore-id: <restore-id> restore-action: RESTORE_EXPIRED | Bridge | complete, included in 1.4.0 release |
*All events have a date stamp associated with them.
...
Events captured by the Bridge Intake Service (CURRENT)
Event | Data | Initiated By | Implementation Status|
---|---|---|---|
Bagging Completed |
| Intake Service | complete, included in 1.2.0 release|
Snapshot Replication to DPN Nodes |
| Intake Service | complete, included in 1.2.0 release
Actions we should be capturing in snapshot history (TO DO)
Event | Data* | Initiated By | Implementation Status |
---|---|---|---|
Snapshot Bit Integrity Check Complete |
| ACE webhook? | TBD: Michael Ritter |
Bridge status events which are not captured in snapshot history
...