-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Support IIIF Search 1.0 #705
Comments
It's probably just a matter of recognising the @context for Search 1. |
apparently already implemented by @edsilv in IIIF-Commons/manifold@6b3b843 |
Yeah. If/when we merge the webpack PR (having a call with @stephenwf, @demiankatz,and @Geoffsc about this today) we will get the latest manifold. |
All issues will be triaged for further investigation or closure by the 28 September 2023. If your issue is still relevant and would like for it be investigated further please comment by 14 September 2023. |
UV version:
All
I suspect this supersedes #132
@nicolasfranck mentioned in IIIF Slack:
I replied:
Yes, unfortunately. The Search functionality at Wellcome is basically 0.9.3 and the server part of that was never updated for 1.0 after it went live, and it's that search functionality that the UV's implementation was designed for. As njfranck says it wouldn't take much to make it 1.0-compliant but that's never been at the top of anyone's backlog. As ever, PRs welcome.
It's probably a good first bug.
The text was updated successfully, but these errors were encountered: