IIIF autocomplete service returns invalid JSON

[tarjelavik]

I am testing the IIIF search service that Goobi viewer offers. Searching the text in an object in the Goobi viewer interface returns hits, but using the IIIF Manifest of the same object in Mirador or other IIIF viewer does not.

This image show the search returning hits:

Using the Goobi viewer Mirador i get this error:

Mirador says it is invalid JSON, but i could not find the response it is referring to :-/

This https://www.digi-hub.de/viewer/api/v1/records/BV042594700/manifest/autocomplete?q=grosse returns:

{
    "@context": null,
    "@id": "https://www.digi-hub.de/viewer/api/v1/records/BV042594700/manifest/autocomplete?q=grosse",
    "@type": "search:TermList",
    "ignored": [],
    "terms": []
}

Is this some unfinished part of IIIF in Goobi? Or a bug or misconfiguration?

[tarjelavik]

Hi, i guess this is caused by the missing @context. The lastest version of the Viewer still has this error.

[Keelhaul]

Hi @tarjelavik ,

Sorry, it seems we haven't really received any e-mail notifications when issues got opened here on Github at that point in time...

The API endpoint you're referring to is for the search autocomplete functionality in the Goobi viewer's own UI, it's not part of the IIIF search service.

[tarjelavik]

Hi @Keelhaul,
Sry, see now that it only applies to the autocomplete service, and i generalized to be about the whole search service. My bad.

I get that it probably originated for the viewer UI, but you have added it as a IIIF autocomplete service in the IIIF manifest. The service identifies as a IIIF Content search service, and viewers are attempting to use it. The response is almost following the IIIF Content Search spec, so i assumed it was intended as a autocomplete search also in external IIIF viewers.

"service": [
  {
    "@context": "http://iiif.io/api/search/1/context.json",
    "@id": "https://www.digi-hub.de/viewer/api/v1/records/BV042594700/manifest/search/",
    "profile": "http://iiif.io/api/search/1/search",
    "@type": "SearchService1",
    "service": [
        {
          "@id": "https://www.digi-hub.de/viewer/api/v1/records/BV042594700/manifest/autocomplete/",
          "profile": "http://iiif.io/api/search/1/autocomplete",
          "@type": "AutoCompleteService1"
        }
      ]
  }
],

The snippet above looks very much like the v1 spec: https://iiif.io/api/search/1.0/#service-description-1

Solutions could be:

1. Remove the autocomplete service from the manifest
2. Make the autocomplete service IIIF compliant

The second options strongly preferred, of course :-), but i haven't easily found manifests with autocomplete in the wild.