Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Events captured by the Bridge as part of the snapshot's history (CURRENT)

EventData*

Who/What initiates it?

Snapshot Complete

alternateIds: ['id1', 'id2', 'id3',...]

TODO: add snapshot-action: SNAPSHOT_COMPLETE method

Node
Request Restore Snapshot

initiating-user: <user email>

restore-action: RESTORE_REQUESTED

Bridge User
Restore Initiated

restore-id: <restore-id>

restore-action: RESTORE_INITIATED

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

...

Additionally, nodes can append node specific events to the snapshot history at any time  via the /snapshot/{snapshot-id}/history  REST call.

Actions we should be capturing in snapshot history

...

(TO DO)

EventData*

Who/What initiates it?

Snapshot Initiated
  • snapshot-action: SNAPSHOT_INITIATED
  • user-email: (or user-id:)
  • snapshot-id: <snapshot-id>
Bridge
Snapshot Transfer to Chronopolis Complete
  • snapshot-action: SNAPSHOT_STAGED
  • snapshot-id: <snapshot-id>
Bridge
Snapshot Replication to DPN Nodes
  • snapshot-action: SNAPSHOT_REPLICATED
  • bag-ids: <list of bag IDs>
  • node: <node name or ID>
Intake Service
Snapshot Complete
  • snapshot-action: SNAPSHOT_COMPLETE
  • alternate-ids: <list of bag IDs>
Intake Service

...

Bridge status events which are not captured in snapshot history

...