Gallery view discussion

[camillevilla]

@snydman mentioned wanting to implement gallery view this sprint. Revisiting the interactive designs, it seems like there are some questions that shake out:

• Should we display single canvases by default?
  • Or is there something about inferring v3 behavior from the manifest?
• How does view type affect sidebar panel behavior?
  • Should canvas metadata NOT be available while in gallery mode?
  • Can you select canvases in this mode? Does clicking on a canvas switch the viewer mode type? Does the notion of a canvasIndex exist in this mode?
  • Should the Canvas Navigation panel be accessible in this viewing mode?

[jvine]

I think it's valid to start with single canvases. At some point, it would be useful to display openings for paged manifests.

In Mirador2, the gallery view was simply a navigation tool: View all the thumbnails at once, pick one and view it in either single or book view, depending what has been active previously. During research for Mirador3, several use cases required a more functional gallery view, a mode where a user can do work.

Gallery requirements

1. zoom & pan the gallery as a whole
2. enhance all items (e.g. toggle all to greyscale, increase brightness, etc.)
3. open one or more canvases in the gallery into independent windows (similar to the advanced catalog functionality)
4. annotate, presumably across canvases
5. toggle a selected layer on/off across all canvases
6. reorder canvases

Obviously some of these are far down the road.

Sidebar sections will have modified content/behaviour depending on the state of the gallery.

• Metadata: If no individual canvas is selected, canvas metadata should not be displayed. Manifest and collection metadata should be displayed. If the user highlights an item in the gallery, display the canvas metadata for that item.
• Index: User can view the list of items beside the gallery of items; clicking on an item in the list should highlight it in the gallery (scrolling it into the viewport if it's not already there). (Highlighting an item in the gallery might also highlight the item in the index.)
• Search: Search still TBD but it should be possible to view results in gallery view, even potentially seeing the distribution of canvases that include the search term.
• Annotations: Likely not displayed until an individual canvas is highlighted.
• Layers: There is a user requirement to turn on/off a given layer for all canvases in gallery view - e.g. to show a particular spectral layer. Not clear yet how this might work.

Select behaviour

• [ ] click/set focus on an image in the gallery to see its content in the side panel; item will be highlighted
• [ ] switch to alternate view to see the selected item in single/book mode
• explore other options (double-click/long touch; hover affordance; looking for ideas) to revert more directly to single/book view.

No item selected, manifest metadata displayed

Item selected in gallery, canvas metadata inserted

No item selected, ToC displayed

Item selected, either from ToC or gallery

[camillevilla]

First ticket has been split out to projectmirador/mirador#2032. After revisiting the intention of this feature with @mejackreed @jvine @ggeisler, we have concluded that OSD's Collection Mode will not be suitable for implementation.

An HTML-based implementation will provide better affordances for the features described above that require interacting with individual canvases.

Ideal next steps to split out would be:

• sidebar panel behaviors described above (will depend on how far along implementations of each are)

• open one or more canvases in the gallery into independent windows (similar to the advanced catalog functionality)

• enhance all items (e.g. toggle all to greyscale, increase brightness, etc.)