IIIF Implementation

The TextGrid Repository is able to deliver images and metadata according to the IIIF specifications. Namely this are the IIIF Image API and the IIIF Presentation API. This allows the usage of METS or TEI files stored in the TextGrid Repository with IIIF based tools like the Mirador Viewer. For more information on IIIF have a look at http://iiif.io/.


Enable IIIF for your Data

For now IIIF usage from textgridrep.de is enabled on chosen projects, as it makes most sense for digitized objects like manuscripts or books, where scans of pages are available. The TextGrid IIIF compatibility layer reads the page order and links to images from DFG Viewer METS or TEI files. In TEI files the facs-attribute of the <pb> Element ist used to determine the images. If you publish data into the TextGrid Repository which matches this criteria of either being DFG Viewer METS or TEI files linking to digitized pages, drop a note to textgrid-support@gwdg.de, so we could activate IIIF and the link to the Mirador viewer for your project. After activation all METS/TEI Data published in this project will automatically use the IIIF feature.


There is some demonstration material published to the public TextGridRep Sandbox, to show the integration and usage of IIIF.

A listing of such objects is available here: https://textgridlab.org/1.0/iiif/manifests/

Mirador Viewer

TextGrid hosts an own version of the Mirador Viewer, that enables a few parameters to integrate published manifests or single items in the viewer. It is available via https://textgridlab.org/1.0/iiif/mirador/ and can parse the following parameter:

The source code is available at mirador_sources.

For published IIIF enabled data within the TextGrid Repository website a link to Mirador is offered in the sidebar.

Technical Documentation

The IIIF implementation for TextGrid has two components, the TextGrid version of the digilib image server and a service to deliver the IIIF metadata.

Source Code

The GIT repositories are located at digilib_sources and iiif-metadata_sources (sharedcanvas)


digilib and the sharedcanvas services both are built with maven. Building the .war files is done with

mvn package

The war files from the /target/ subdirectory could afterwards be deployed in an application server like tomcat.


The metadata service configuration is normally living in /etc/textgrid/screpview.properties . This service is using spring, so advanced configuration could also happen in the webapp/beans.xml file, in this place also the path to the properties files could be changed.


See iiif-metadata_bugtracking