OpenAtlas

• It is open source (GPL 3), and on GitHub
• Debian packages are available
• Already used at the ACDH-CH
• Seems to be actively developed and well documented

Just some notes for myself (and maybe later for install notes)
IIPImage server install documentation: https://iipimage.sourceforge.io/documentation/server

# apt install iipimage-server

Test with http://localhost/iipsrv/iipsrv.fcgi

• Only supports IIIF API v1 and v2
• Only pip package available

But it is available for every OpenAtlas instance without additional configuration. I made a branch: feature/iiif-server where it is available. After you installed flask-iiif via pip just start the application and go to this url and change ID to an existing image id:

http://127.0.0.1:5000/iiif/ID/full/500,600/180/bitonal.jpg

• how to handle image identifiers. They need to be unique for IIIF, but if multiple OpenAtlas instances uses IIPImage, duplicated image identifiers can happen
• for installation, solid knowledge about web server administration is required.

Just a quick feedback from me about the latest considerations:

how to handle image identifiers. They need to be unique for IIIF, but if multiple OpenAtlas instances uses IIPImage, duplicated image identifiers can happen
I would assume that should be solvable, e.g. a different prefix per OpenAtlas instance

• A check if needed software is installed
• If needed software is installed also a setting to turn it on/off in the backend admin area (saved in db table web/settings)

For the IIPServer, we have to choose between mod_fcgi or mod_fastcgi. While each server administrator can take what he wants, we should agree on a standard for our servers. mod_fcgid is, as far as I understand, automatically installed with apache2, so I got mod_fcgid.

Could config server to use clean URL, e.g.

/iiif/output.tif/full/400,400/90/grey.jpg

One thing is, that I don't know if the current version of iipimage (1.1 in bookworm) can serve IIIF API v3.