Skip to content
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.

Allow pre-defining sync groups #10

Open
markmatney opened this issue Aug 16, 2018 · 1 comment
Open

Allow pre-defining sync groups #10

markmatney opened this issue Aug 16, 2018 · 1 comment

Comments

@markmatney
Copy link
Contributor

My understanding is that this would entail allowing the maintainer of a Mirador instance to specify that certain sync groups should be automatically created for users on initialization. Those groups could optionally be associated with window objects (i.e., elements of Mirador's windowObjects setting).

@jpadfield
Copy link

An old iipimage based example of this functionality can be seen at: https://cima.ng-london.org.uk/iip/examples/newcomp.html

The use case is a set of registered images of the same object/subject (potentially different images types (UV, X-ray IR, Vis, etc) or stages of conservation treatment, etc.) have been prepared, so they are all the same size and line up correctly. Users would them want to be able to compare and contrast any combinations (and number, limited by resources and screen size) of the registered images in order to study and learn more about the

In a general viewer a user might not know that the images are a prepared set, unless they are prsented with a dedicated page, so it would be useful to be able to display them as such by default. All of the images in the set may not need to be displayed at the same time. So the notion might be to be able to automatically sync all images from a specific manifest.

I am not sure in your current code how you would cope with this as each window is loaded as a separate item with its own manifest - perhaps a process of adding manifests to the sync rather than specific windows? Hence all new windows added with the same manifest(s) are automatically added (or removed) from the sync group.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants