Surfaces
Offline Snapshot History
Export and import evidence for EMS LAN snapshot reconciliation.
First created Last updated
auditems-lanevent-managementsnapshot
Overview
Offline Snapshot History is the audit trail for LAN snapshot exports and imports. It helps event leads answer which file was taken offline, which file returned, when it was processed, and what state was expected after reconciliation.
Use this page during closeout whenever the event used an offline LAN system or prepared one as a backup.
Dashboard route
/ems/manage/offline-snapshot-history?id=:eventId
The page only works for a signed-in operator with an event ID. Without an event ID, it shows No event ID in URL. Without dashboard auth, it sends the operator to sign in.
Page controls
| Control or element | Type | What it does | Operational impact | Check before using |
|---|---|---|---|---|
| Open LAN snapshot tools | Link button | Opens /ems/manage/offline-snapshot and keeps the current event ID attached. | Lets staff move from audit history back to export/import tools without losing event context. | Confirm the URL still contains the same id query value. |
| Audit history status | Generated status text | Shows loading state, load failure, or how many LAN snapshot audit records were loaded. | Tells closeout staff whether the list is current and whether an error blocked evidence review. | Refresh if another operator may have exported or imported after the page loaded. |
| Refresh | Button | Reloads the history from /api/events/:eventId/check-in/offline-snapshot/history. | Pulls new export/import records without leaving the page. | Use before final closeout, especially after an import was just performed. |
| Empty state | Generated message | Shows No LAN snapshot exports or imports have been recorded for this event yet. | Confirms there is no recorded LAN snapshot activity for this event. | If staff expected LAN use, investigate whether they are on the wrong event or whether the export/import never happened. |
| Live refresh | Background refresh | While the page is visible, the dashboard live feed reloads history about every 20 seconds. | Keeps the audit list current when another operator performs export/import work. | Do not rely on background refresh alone for closeout; press Refresh before final signoff. |
Audit record fields
Each history item is rendered from the snapshot audit record returned by the API.
| Field or badge | What it shows | Meaning | How to use it |
|---|---|---|---|
| LAN snapshot exported | Record title for an export action. | A snapshot was generated from the online event for LAN use. | Confirm this happened before offline operations started. |
| LAN snapshot imported | Record title for an import action. | A LAN-generated snapshot was imported back into the online event. | Confirm this happened after onsite LAN operations ended. |
| Created time | When the audit record was created. | Establishes the order of export/import activity. | Compare against doors-open time, outage notes, LAN handoff time, and closeout time. |
| Actor email | Staff email shown beside the timestamp when available. | Identifies who performed the export or import. | Use when a reviewer needs to ask why a snapshot was generated or imported. |
| Action badge | export or import. | Shows the direction of the snapshot movement. | Exports and imports are separate; both may be required for a complete LAN handoff. |
| Format badge | json, gzip, or zip. | Shows which snapshot format was used. | Normal operator exports should usually be ZIP. GZIP/JSON may indicate support or alternate LAN tooling. |
| Schema badge | Snapshot schema version, or - when missing. | Identifies the snapshot format version. | Escalate if the LAN app and dashboard appear to use incompatible schema versions. |
Detail panels
| Panel | What it contains | Why it matters |
|---|---|---|
| Snapshot source | Source metadata recorded with the snapshot, shown as key-value lines. | Helps prove which event or LAN source produced the file. |
| Snapshot contents | Counts from changeSummary.snapshotCounts, shown as key-value lines when available. | Shows what the snapshot contained at export/import time. |
| What changed | Counts from changeSummary.applied, shown as key-value lines when available. | Shows what the import applied back into the online event. |
| No structured summary recorded | Fallback text when a summary object is missing. | Means the record exists, but the detailed counts are unavailable. |
| No source metadata recorded | Fallback text when source metadata is missing. | Means staff should rely on timestamp, actor, action, format, and related handoff notes. |
Flowchart context
Run Check-In references snapshot history during exception and closeout handling. Close Out an Event should link here when verifying that offline changes returned to the online dashboard.
Common mistakes
- Do not assume an exported snapshot means the offline system was reconciled. Export and import are separate events, and both need to be visible in history when LAN operations were used.
- Do not treat an empty history as proof the LAN system was unused until the event ID is confirmed.
- Do not ignore schema or format differences when import results look wrong. They are useful clues for support.
- Do not close out the event until the latest expected LAN import appears in history or a responsible owner records why no import is needed.