Events captured by the Bridge as part of the snapshot's history (CURRENT)
Event | Data* | Who/What initiates it? | Initiated By |
---|---|---|---|
Snapshot Initiated |
| Bridge | |
Snapshot Transfer to Chronopolis Complete |
| Bridge | |
Snapshot Complete | Snapshot Complete | alternateIds: ['id1', 'id2', 'id3',...] TODO: add
| Call to complete snapshot made by Intake Service Event captured by Bridge Node |
Request Restore Snapshot | initiating-user: <user email> restore-action: RESTORE_REQUESTED | Bridge User | |
Restore Initiated | restore-id: <restore-id> restore-action: RESTORE_INITIATED initiating-user-email: <request initiating user email> | Bridge Admin | |
Restore Completed | restore-id: <restore-id> restore-action: RESTORE_COMPLETED expiration-date: yyyy-MM-dd | Bridge System | |
Restore Expired | restore-id: <restore-id> restore-action: RESTORE_EXPIRED | Bridge System |
*All events have a date stamp associated with them.
Additionally, nodes can append node specific events to the snapshot history at any time via the /snapshot/{snapshot-id}/history REST call.
...
Events captured by the Bridge Intake Service (CURRENT)
Event | Data | Initiated By | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Bagging Completed | *Who/What initiates it? | Snapshot Initiated
| INITIATED
| user
| email: (or user-id:)
| Bridge | Snapshot Transfer to Chronopolis Complete | snapshot-action: SNAPSHOT_STAGED
| BridgeIntake Service | |
Snapshot Replication to DPN Nodes |
| name
| Intake Service | Snapshot Complete |
| Intake Service
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
...