Infrastructure Integration

Glycerine modules supports a range of implementation patterns where: 

  • Glycerine Server provides a back-end model and APIs for integration with existing digital asset management infrastructure. 
  • Glycerine Editor  can be embedded into existing collections management workflows, or indeed in the organisation’s content management system for external contributors.
  • Glycerine Viewer can be themed and embedded in a content management system.  Of course, one can deploy any IIIF viewer. 
Picture1

Implementation Patterns 

Existing IIIF Infrastructure 

This use case presumes the organisation has existing IIIF infrastructure. In the flow chart this is captioned as the ‘data management system’: 

  • The existing data management system (digital asset or collections management) has its own IIIF implementation which can generate manifests from its data models. 
  • Glycerine Editor is installed and configured in this data management system. 
  • Glycerine Editor gets the manifests (without annotations) from the data management system and reads and writes annotations from and to the Glycerine Server using our Web Annotation API. 
  • When serving up IIIF for Glycerine Viewer in a website, the data management system aggregates the annotations from Glycerine Server into a full manifest.
2 2

No Existing IIIF Infrastructure  

In this use case there is no existing IIIF implementation, Glycerine Editor is installed in the Data Management System and is integrated out of the box with Glycerine Server, which acts as both IIIF and annotation server. Glycerine Viewer gets manifests directly from Glycerine server. 

1 4

Existing IIIF and Annotation Infrastructure 

At the other end of the spectrum this is where the organisation prefers to use their own annotations data store as well as their own IIIF infrastructure. Glycerine Editor installed in the Data Management System and read/writes the existing data store using WAP. Glycerine Viewer gets manifests from the existing Data Management System.

3 2

Open Source

Glycerine Server and Editor are run as open-source projects, developed and managed by Systemik.  They are sustained through annual subscription which enables Systemik to provide subscribers with support and updates. Systemik provides full integration and implementation support consulting to embed Glycerine in your infrastructure and workflows, and both GitHub and service-level support options.  Contact us for a pilot implementation guide and GitHub access.