Story: Image cache polish
Table of Contents
This page documents a story in Sprint 10. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Fix the image cache surfaced by DQ publication: it didn't reload on new datasets, and a full reload was expensive.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 10 |
| Now | Completed 2026-01-23. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-01-23 |
Acceptance
- Cache reloads on image dataset publication.
- Reload is incremental via
modified_since. - No UI flashing on reload.
- Backward-compatible protocol change.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Image cache reloads on new datasets | DONE | 2026-05-19 | 2026-01-22 | When publishing images the image cache must reload; current behaviour leaves it stale. |
| Incremental image cache loading with modified_since | DONE | 2026-05-19 | 2026-01-22 | Protocol: add optional modified_since to list_images_request and recorded_at to image_info; client tracks last_load_time and only fetches changed images. |
Decisions
modified_sinceas the incremental keyrecorded_atwas already on every image;modified_sinceis the natural pairing.- Optional protocol field, server defaults to all
- backward compatible by construction.
Out of scope
- Generalising the pattern to other caches — handled when the next cache needs it.
See also
None.