Overview

I developed an Omeka S module that adds IIIF Content Search API URIs to IIIF manifests.

github.com

By using the IIIF Content Search API, text search becomes possible in viewers such as Universal Viewer, as shown below.

OwZuM7ELsdXuDEOdpio0UyCGmgF58t1y2tghcqPoyuxJlnYE_3olorlYGPE0Zn5VvfwzkSD6YBgfDEtpPLf2a1D9_CBzPTcPjeVH0ixokaPP2PcZ8G429VXB0MkxFJDOIz6OE5uWqvo (1600x876)

This module uses an IIIF Content Search API that is provided independently of Omeka S. Therefore, to use this module, you need to separately set up an environment that provides this API. While there remains the challenge of the cost of building this environment, I hope this is helpful for those who already have an IIIF Content Search API environment and are considering using it with Omeka S.

(I hope to write a separate article on building an IIIF Content Search API environment.)

Background

The Omeka S IIIF Server module generates IIIF manifest files from metadata registered in Omeka S. It is primarily developed by Daniel-KM, who has developed various Omeka modules.

omeka.org

Instructions for using this IIIF Server module are introduced below:

youtu.be

This module provides various features related to the IIIF Presentation API, including support for IIIF Presentation API 3.0, IIIF collection output, and table of contents generation. However, as of the time of writing (2022-02-11), it does not provide functionality related to the IIIF Content Search API.

Separately from the module developed here, there is another IIIF Content Search API-related module below. While this is a very useful module that builds an IIIF Content Search API environment within Omeka S, it is limited in scope as it assumes the use of OCR text for PDF files.

github.com

Feature Introduction

The feature provided by this module is simple: as shown below, it provides a configuration option to specify the property that stores the IIIF Content Search API URI. For items that have a URI-format value in the configured property, the module appends the IIIF Content Search API service information to the IIIF manifest.

image

An example of the generated IIIF manifest is shown below. You can confirm that the IIIF Content Search API service information is included in the IIIF manifest (generated by the Omeka S IIIF Server module).

https://iiif.dl.itc.u-tokyo.ac.jp/repo/iiif/d507a810-cff7-4168-bc10-70a32a55920f/manifest

An example of display in Universal Viewer is also available below:

https://universalviewer.io/examples/uv/uv.html#?manifest=https://iiif.dl.itc.u-tokyo.ac.jp/repo/iiif/d507a810-cff7-4168-bc10-70a32a55920f/manifest

Notes

I am currently learning how to develop Omeka S modules. I plan to write an article about this in a tutorial-like format.

From the perspective of module development, this module provides functionality to append information to existing modules (e.g., the IIIF Server module). I hope this repository also serves as a reference when developing modules for similar purposes.