Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sharing a link for opening two or more Canvases #540

Open
giacomomarchioro opened this issue Sep 6, 2024 · 2 comments
Open

Sharing a link for opening two or more Canvases #540

giacomomarchioro opened this issue Sep 6, 2024 · 2 comments
Assignees

Comments

@giacomomarchioro
Copy link
Contributor

giacomomarchioro commented Sep 6, 2024

Recipe Name

Sharing a link for opening two or more Canvases

Use case

I want to compare pages from two different manuscripts and share a link to open both of them on the same view. I want to share a link to a colleague showing two similar paintings in two different collections. I want to save my current workspace (open Canvases in the current viewer) for later users. I want to open my current workspace with another viewer.

Mirador already implements a format for exporting the current workspace for sharing or later users. Content State API could be used for the same purpose, adding the advantage of direct loading of the workspace using a crafted link with the iiif-content query parameter. The multiple targets for a comparison view section describes a method for targetting two Canvas at the same time; each Canvas could be from a different Manifest.

Other considerations

We can also assume that viewers that implement the Content State API section regarding the targeting of a Canvas region will be able to open the Canvas and also draw attention to the selected region.

We assume that the two Canvas will be displayed side by side, but could viewers concatenate the two Manifests or open two separate instances of the viewers?

Should we concerned about the length of the final base64URL encoded URL? (it seemed Apache and Internet Explorer were the bottlenecks, with approx. 4000 and 2000 characters, while other technologies usually support up to 40000).

@giacomomarchioro giacomomarchioro self-assigned this Sep 6, 2024
@giacomomarchioro giacomomarchioro changed the title Share a link for opening two or more Canvases each from a different Manifest Sharing a link for opening two or more Canvases each from a different Manifest Sep 6, 2024
@giacomomarchioro giacomomarchioro changed the title Sharing a link for opening two or more Canvases each from a different Manifest Sharing a link for opening two or more Canvases Sep 6, 2024
@giacomomarchioro
Copy link
Contributor Author

I was thinking to use these two images for creating two different manifests to be loaded at the same time:

https://fixtures.iiif.io/info.html?file=/images/Yale/ycba/The_Colosseum_Rome.jpg

https://fixtures.iiif.io/info.html?file=/images/Yale/ycba/The_Colosseum_Rome2.jpg

Any other suggestion is welcomed.

@giacomomarchioro
Copy link
Contributor Author

As discussed in the cookbook meeting I'll use this manifest from another recipe :

https://preview.iiif.io/cookbook/0485-contentstate-canvas-region/recipe/0318-navPlace-navDate/manifest-2.json

and I'll create another one showing another view of the Colosseum that will be store with the Content State example.

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

No branches or pull requests

1 participant