Showing (or hiding) the search box for IIIF content search

[anarchivist]

In discussing the service concerns around varying OCR quality regarding our rollout of the IIIF search API with @caaster (see sul-dlss/content_search#8), we discussed the possibility of there being contexts in which we can selectively enable or disable the search box that appears. These scenarios include the following:

• Until we have the opportunity to feel confident that content_search works well enough of OCR of varying quality, potentially hide the search box on PURL and in Searchworks (or other contexts here)
• Allow exhibit curators to explicitly enable (or disable) the search box from within the exhibit dashboard, even when full text is available for those resources

The discussion/analysis to complete here should probably include the VT team and both @ggeisler and @jvine. Specific questions to discuss include:

• What are all the specific cases in which we want to display or hide the search boxes?
• What is the impact of having differing behavior here from a UX perspective?
• Where do we need to add hooks to enable/disable this? UV, sul-embed, Spotlight, and where else?

[anarchivist]

Per the 1/31 follow up meeting with myself, @ggeisler and @caaster, we've decided that this is not an issue for the time being, as the production index will rely on the object-level data model changes that we identify in sul-dlss/content_search#47 - manifests will not have a discoverable search service unless the implemented changes are included in an object's contentMetadata.