IIIF workflow

[Cecilia Pitta]

Dear all,

As research purpose, I'm looking for a general description of the IIIF implementation workflow. Any suggestion?

Many thanks,

Cecília

[Ben Bakelaar]

Hi Cecilia, without any other detail, I'll try to summarize the process very generally... and will state the obvious just to be clear.

In order to implement IIIF, you will of course need your item metadata and digital objects organized in some way. In most cases, these are already in a digital system of some sort, perhaps a digital archive or repository, etc. And in those cases, the implementation question is more about how to add IIIF capability/support to an existing system, which is more or less a technical question for IT and developers.

However, when the project is producing new data or transitioning from some sort of legacy environment - perhaps even just a spreadsheet and folders of image assets - the general workflow is that 1) the images need to be loaded to a IIIF-compatible image server; 2) the IIIF images and item metadata need to be merged and compiled into a JSON manifest; and then 3) the items/objects need to be made visible through a discovery or presentation layer of some sort which has a IIIF-compatible "viewer".

So, three requirements (generally speaking):

Server

Manifest

Viewer

The server holds the images. The manifest references the images in IIIF format. The viewer presents the manifest. And in most implementations, the viewer itself sits inside a website, which may be a content management system, a discovery layer, or any of dozens of other possible technology solutions :)

I'm not sure if I've described a workflow the way you meant it, but this is my version of "what you would need to understand to get started with IIIF".

--
Ben Bakelaar

Digital Humanities Architect

Thomas A. Edison Papers, Rutgers University

Vatican Film Library, St. Louis University

--
-- You received this message because you are subscribed to the IIIF-Discuss Google group. To post to this group, send email to iiif-d...@googlegroups.com. To unsubscribe from this group, send email to iiif-discuss...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/iiif-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "IIIF Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iiif-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/2f2cadba-e9e5-41c1-8a47-ab74dc75bf68n%40googlegroups.com.

--

--

Ben

http://www.linkedin.com/in/benbakelaar

[Tristan Roddis]

Hi Cecilia,

If you are referring to image preparation, myself and others wrote a bit about this in the "Image preparation workflow" section of the IIIF At Scale paper we presented at MuseWeb last year:

https://mw20.museweb.net/paper/iiif-at-scale/#:~:text=Along%20with%20strategies%20for%20delivering%20images

The summary version is that it varies a lot according to institution, and the number of images involved!

Hope that helps,

-Tristan.

--
-- You received this message because you are subscribed to the IIIF-Discuss Google group. To post to this group, send email to iiif-d...@googlegroups.com. To unsubscribe from this group, send email to iiif-discuss...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/iiif-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "IIIF Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iiif-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/2f2cadba-e9e5-41c1-8a47-ab74dc75bf68n%40googlegroups.com.

--

                                                                     

cogapp
building a better online world

                                                                     

Tristan Roddis
Director of Web Development
www.cogapp.com

[Cecília Pilar C. Pitta]

Thank you!

You received this message because you are subscribed to a topic in the Google Groups "IIIF Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/iiif-discuss/fVmftZvEJ-0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to iiif-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/e245e9a6-9e75-952a-f56a-7544e2884fb7%40cogapp.com.

[Cecília Pilar C. Pitta]

I went to read and study about these technical specifications. As I understand it, it works like this:(1) Images and metadata must be prepared, (2) Images must be converted to JPEG or PTIFF, (3) Images must be integrated in a IIIF Image API compliant server, (3) Images and metadata are merged in a Json file (manifest), (4) The manifest are integrate in an IIIF Presentation API compliant server (some images servers also support Presentation API specifications), (5) A client server request from both Image server and manifest server. 

I draw this diagram as I was trying to understand:

Is it more or less correct? Many thanks,

Cecília

[Tristan Roddis]

Yes, Cecilia that is correct!

The only clarification I would add is:

(2) Images must be converted to JPEG2000 or PTIFF

That's because JPEG2000 is Pyramidal format like PTIFF, whereas regular JPEG is not.

Also, note that the Manifest Server is just a standard web server: i.e. anything that can serve JSON files over HTTP. This contrasts with the Image Server that must run specialist software such as IIPImage or Cantaloupe to convert the source pyramidal images into regular JPEGs for delivery over HTTP.

That last point doesn't affect your diagram: it is more an implementation detail in that most organisations will already have one or more web servers that could be repurposed to serve the manifests, whereas they are unlikely to have the Image Server part if they have not used dynamic image delivery before.

Hope that helps.

-Tristan.

To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/CALgzfN-7XYhQrhBss0iPoo76bBu5L2do0DVD-spiQCUycjKpmw%40mail.gmail.com.

[HIGGINS, RICHARD I.]

Yes, it is possible to serve your manifests from your image server – it may make things easier.

You could consider a permanent URL system for images, manifests etc. (such as handles or arks or anything that you already have in place) if it is to grow into a large system.

Depending on how your images are going to be presented you should also decide if you need to write links to the manifest back into your original descriptive metadata, which would be necessary if these catalogues are going to provide access to material available online.

Best regards

Richard

 

From: iiif-d...@googlegroups.com <iiif-d...@googlegroups.com> On Behalf Of Tristan Roddis
Sent: 12 May 2021 12:19
To: iiif-d...@googlegroups.com
Subject: Re: [IIIF-Discuss] IIIF workflow

 

[EXTERNAL EMAIL]

To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/85c37537-1e62-6d92-2f1c-679f18b1ff05%40cogapp.com.

[Cecília Pilar C. Pitta]

Thank you  all for the help and information! I really appreciate it :)

Kind regards,

Cecília

To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/LO0P265MB2780D610050BDDB19E14B3988F529%40LO0P265MB2780.GBRP265.PROD.OUTLOOK.COM.

[Cecília Pilar C. Pitta]

Hello,

i would like to ask one more question. This is about the Image information request. 

The image server delivers image content when requests to the image are made. Is the image information response made at the same time? How is the image information document created?

Kind regards,

Cecília