Story
A parent work with no files of its own (only child works carry files) should render a working IIIF manifest so the viewer on the public show page displays the children's images. Child work metadata (the "page" level) should appear in the manifest alongside the parent's top-level metadata.
This is a presenter concern: no reindex expected, not migration-blocking. Applies to all seven work types.
Sample Data
compoundMultiWorkExample.csv
Acceptance Criteria
Screenshots / Video
Testing Instructions and Sample Files
- Create a parent work (any type) with no attached files
- Attach one or more child works that have files
- Visit the parent's public show page and confirm the viewer loads and displays child images
- Inspect the IIIF manifest to verify both parent and child metadata are present at their respective levels
Notes
Current behavior untested; may already partially work. The viewer itself (UV) is a separate concern from manifest generation.
Story
A parent work with no files of its own (only child works carry files) should render a working IIIF manifest so the viewer on the public show page displays the children's images. Child work metadata (the "page" level) should appear in the manifest alongside the parent's top-level metadata.
This is a presenter concern: no reindex expected, not migration-blocking. Applies to all seven work types.
Sample Data
compoundMultiWorkExample.csv
Acceptance Criteria
Screenshots / Video
Testing Instructions and Sample Files
Notes
Current behavior untested; may already partially work. The viewer itself (UV) is a separate concern from manifest generation.