Paged Content Open Seadragon broken on Bartik

[seth-shaw-unlv]

Kathryn Gucer reported an issue on Slack with the Open Seadragon block not appearing on their paged content node.

We checked all the usual suspects and then noticed something odd. The block was looking for the manifest @ /node/%node/book-manifest even though the endpoint was set to /node/%node/manifest and the Open Seadragon settings was configured with the correct view.

We temporarily fixed it by changing the end-point.

Then @bseeger found that the paged content context configuration reaction for the Batik theme was set to the book-manifest variant whereas the carapace theme manifest URL was set correctly.

So, the simple fix is a PR to update the context config to fix the manifest URL for Bartik. In the mean-time site admins can update the context reaction block config for Bartik manually with the block edit form.

That stated, what do we use the IIIF Manifest setting in the OpenSeadragon settings form if not for the block?