Repository navigation
Make collection photo removal work end to end #560
Description
Part of #558.
Outcome
An owner can remove a selected photo from a collection entry, and it stays removed after reload. The existing remove control currently only displays “Image deletion will be implemented in a future update”.
Acceptance criteria
- Replace the stub with a confirmed, authenticated action that verifies entry ownership and the photo's membership in that entry on the server.
- Identify the photo by its stored stable key, not array position or an arbitrary client-supplied storage path. Repeated/stale requests must not remove a different photo.
- Persist removal without losing other photos or concurrent entry changes. The gallery and edit dialog reflect the result after reload, including removal of the last photo.
- On failure preserve a coherent visible state and offer a usable retry. Make the remove control keyboard and touch accessible.
- Follow the repository's existing media retention and reference policy. Inspect references before any storage deletion; never delete an object still referenced by a Submission or CARES registration. Document whether this action detaches metadata or also cleans up exclusively owned variants.
- Cover successful removal, last photo, unauthorized/foreign key, stale/repeated request and persistence failure in focused tests; exercise the dialog on public staging with chikin-farm.
Blocked by
None.
Related: #115 covers general image-system enhancements, not this collection control; #468 covers a separate collection PATCH test/read improvement.
Activity
Make collection photo removal work end to end (#560)
Make collection photo removal work end to end (#560) (#591)