Digilib is a versatile image viewing environment for the internet. It is a web based client/server technology for images. The image content is processed on-the-fly by the eSciDoc Digilib service on the server side so that only the visible portion of the image is sent to the web browser on the client side. Digilib supports a wide range of image formats and viewing options on the server side while only requiring an internet browser with javascript and a low bandwidth internet connection on the client side.

The eSciDoc Digilib service works with contents stored in eSciDoc items. You should choose a content model in which your images are stored as components, which is the standard storage approach. You can access an image via the normal API calls (e.g., /ir/item/escidoc:ex5/components/component/escidoc:ex6/content). As soon as you append Digilib-specific parameters to the URL, the eSciDoc Digilib service is invoked, and the requested Digilib action is performed on the server-side before the image is transferred to the client.


eSciDoc Digilib-Server (as WAR file)

eSciDoc Digilib-Client (as WAR file)


Deploy the WAR (web archive) to the Tomcat in which your Fedora installation runs. In a typical eSciDoc Infrastructure installation, Fedora is deployed to a stand-alone Tomcat server. Either copy the war file into the webapps directory of Fedora ($FEDORA_HOME/tomcat/webapps/) or deploy it via Tomcat's Deployment service (usually http://<my-server>:8088/manager/html).


Typically, a configuration of the Digilib service should not be necessary. The eSciDoc infrastructure is pre-configured to directly work with the DigilibServer.

If your Fedora installation runs on a non-standard port (which is localhost:8082), then please change in the escidoc-core.properties file the parameter digilib.scaler to the hostname and port of your Fedora instance.

The DigilibClient.war is to deploy into the JBoss and not the Fedora Tomcat. The Client can run also on other hosts, in this case is the new location to configure within the escidoc-core.properties.


With the exception of the parameter request_path and fn, which are unused, all parameters are identical to Digilib's Scaler Web API description.

To request a transformed image via the REST interface, build the path to the interest content of an Item extend the path with /digilib (the supported content transformation service for images) and add the digilib Scaler parameter.

The following example requests the content of component escidoc:ex6 of item escidoc:ex5:


(remove line breaks)

You can find the above mentioned objects in the example objects pack . A link to the digilib client is set within the Rest interface. You can reach it via: http://<my-server>/ir/item/escidoc:ex5