Independent IIIF Content Search Components #440
Labels
Annotation API
Paint and scratch, share your feelings with SVG
Drupal 10
Upgrade economy
enhancement
New feature or request
Field Formatter
The thing that glues the pieces and adds glitter
IIIF
Specs/Manifests/Implementations
Javascript
Favourite language of a PHP developer
metadata
Meta(l) data
Search and Discovery
Mess around and find out
Search API
UI driven hints
Show stuff on screen so people have less guessing to do
UX
Like UI but with an X
Working Group's 💜
Imagined, curated and loved by the Working Group
Milestone
What?
Without enough viewers supporting IIIF Content Search a big part of our enabled features are only usable by machines.
The idea here is to generate custom/template based/core element reusable components that can be dropped to allow other non IIIF viewers (or IIIF viewers that don't have search capacity) to benefit from
This issue requires
-> template/custom elements with arguments (pre-process)
-> JS capable of hitting an API, returning results and feeding back via Ajax these components with results
-> JS capable (a small generic Plugin system others could then follow) of using this Archipelago data to feed into (black box) internals for other viewers. Thinking of OSD and HTML5 Video/Audio for now
There is an extra benefit to this. Accessibility and unified UI/UX
The text was updated successfully, but these errors were encountered: