Allow IABookreader to use IIIF Search API too + Make Mirador react to URI Fragments + OSD Search

[DiegoPino]

What?

For CWS and complex manifests that Simplistic Flavor driven IABookreader controller is not enough. By allowing (when present) IABookreader to use the smart IIIF Search API endpoints (driven by IIIF Manifest level hints/elements) we can have a unified experience between viewers. This needs to be a config option bc the smart endpoint is computationally speaking more intensive and does not even make sense if an ADO contains a single PDF or shows single pages (each child object is a single Image) of a CWS.

To make all better (and some people happier &&|| in peace) we need to also compute fragments in the shape of what the IABookreader accepts on mirador, that way both Viewers can be used to link directly to full text hits and pages

[DiegoPino]

@alliomeria thinking out loud here *sorry I am loud
What if I also do the same of OSD? (open sea dragon) and allow search to be made via the IIIF Search API there and show as annotations?

[alliomeria]

That would be great to have for OSD if feasible, @DiegoPino, definitely a strong use case for that.

[roromedia]

If there would be a unified toolbar approach it would be great. Day-dreaming along: Even better if it would support multiple profiles like the Drupal text filters for different use cases and we could just select those at Display-modes and the user gets the corresponding toolbar (a slim one for Display Mode A, a more complex one for Display Mode B). The backend for it could (re-)use the drag and drop interface from the text filters?