Incorporating IIIF Gallica images into a TEI publisher edition

[Laura Morreale]

Hello IIIF community!

I am very very close to being able to publish several texts on TEI publisher, all of which use IIIF-compliant images that I would like to display alongside the transcriptions and translations I have prepared. The one roadblock is getting the correct "base url" and image link in my xml file.

Here is the question I asked on the TEI publisher (e-editions) slack:

I’m trying to get the base-uri for my IIIF manuscript, but I keep getting an error for the image display, which makes me think the base-uri I have is incorrect. The manuscript is from Gallica (BNF) and the manifest is: https://gallica.bnf.fr/iiif/ark:/12148/btv1b107206728/manifest.jsonI have in my template : base-uri=“https://gallica.bnf.fr/iiif/”  and in my .xml document <pb facs=“iiif:ark:/12148/btv1b107206728/f2/full/full/0/native.jpg”/> but I get the error message 

And this is the response I received:

"You need to point to the info.json of the image, i.e. use base-uri="https://gallica.bnf.fr/iiif/" and as actual link to an image: facs="ark:/12148/btv1b107206728/f2"

I followed this advice, but to no avail. Might anyone in this group have advice about how to get to the IIIF-served image into my edition?

Many thanks,

Laura Morreale

[Andrew Hankinson]

Hi Laura,

I don't think it's your fault -- I can't seem to get an info.json response from the Gallica Image API for that source. I tried another one as well and it seems it's not working. I'm guessing that your tool relies on this response.

I can get a very basic one here: https://gallica.bnf.fr/iiif/ark:/12148/btv1b107206728/f2/info.json. Requesting "https://gallica.bnf.fr/iiif/ark:/12148/btv1b107206728/f2" *should* automatically redirect to this, but it does not work.

-Andrew

> --
> -- 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/b1bff212-ef98-4ab9-a728-4f2b70271c09n%40googlegroups.com.

[Laura Morreale]

Dear Andrew,

Thanks so much for the feedback. This is a pity since many of the sources I am using for my work come from the BNF. Not sure what my next steps will be.

It has been a long and difficult road, bringing all of these technologies together.

Laura

To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/8057CE9B-91BF-4FB1-AE00-D6B9674E36DE%40gmail.com.

--

Laura K. Morreale, PhD

Adjunct Faculty, History;Visiting Scholar, Department of Italian,

Georgetown University

Associate in the Department of History, Harvard University 

Affiliated Scholar, Center for Medieval Studies, Fordham University 

Medieval Academy of America:

Councillor, 2020-2023

CARA Executive Committee

Chair, Digital Humanities and Multimedia Studies Committee, 2020-2021

[Andrew Hankinson]

It's certainly not easy, being an "early adopter!"

A couple things you could try:

1. You could contact the TEI Publisher folks if they could suggest a fix or work-around. Their GitHub issues page looks active, so you might start there? https://github.com/eeditiones/tei-publisher-app/issues. Giving their developers an actual real-world use-case to try might help sort out the bug, and fix it for others trying to do the same thing.

2. Perhaps a kind soul at the BnF who is monitoring this group (or a kind soul who knows who to talk to in the BnF) could ask if there is a way of getting the image service fixed.

-Andrew

> To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/CADvjaN7_crZgpQn6TOicZ0QnvCHOJKxSA3eTOZ-5AD%3DL6BQYrw%40mail.gmail.com.

[Laura Morreale]

Thank you, Andrew, I will try what you have suggested.

Although the early adopter route is a tough one, it does introduce us to the many "kind souls" - you among them - out there, and that is in some ways its own reward, especially in these difficult times.

Warmly,

Laura

To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/01E1AC9C-F4C8-437C-826B-78FC2F4299ED%40gmail.com.

[Régis Robineau]

Hi Laura,

I think Andrew is right, it should work with the xml suggested in the response you had on Slack, i.e. base-uri="https://gallica.bnf.fr/iiif/" and facs="ark:/12148/btv1b107206728/f2".
The url pattern of the Gallica Image API endpoint is: https://gallica.bnf.fr/iiif/ark:/12148/{Ark_Name}/f{n}
So the Image API URL for this particular image is indeed: https://gallica.bnf.fr/iiif/ark:/12148/btv1b107206728/f2. This is the "IIIF image base URL", but the problem is that Gallica does not redirect it to the "info.json" that is probably expected by viewing component used by TEI-publisher (i.e. https://gallica.bnf.fr/iiif/ark:/12148/btv1b107206728/f2/info.json).
The implementation of the IIIF Image API in Gallica is rather minimal, and it is still based on the old 1.1 version (from 2013!). I guess TEI-publisher should append the "info.json" suffix by itself to make Gallica images work...

Régis

[Laura Morreale]

Hi Régis,

Ok terrific. The team is meeting this evening to give this another try. If we are successful, I will come back and post the link to our edition here, if it would be helpful to other IIIF users out there who are interested in using BNF images in digital editions. We are so, so close, this is just the very last bit to get right (it's been a 4 year journey!).

Laura

To view this discussion on the web visit https://groups.google.com/d/msgid/iiif-discuss/53cef804-a13e-df55-eff0-51e93ff08ae0%40ephe.psl.eu.

[Régis Robineau]

Le 28/09/2020 à 13:38, Andrew Hankinson a écrit :
> It's certainly not easy, being an "early adopter!"
>
> A couple things you could try:
>
> 1. You could contact the TEI Publisher folks if they could suggest a fix or work-around. Their GitHub issues page looks active, so you might start there? https://github.com/eeditiones/tei-publisher-app/issues. Giving their developers an actual real-world use-case to try might help sort out the bug, and fix it for others trying to do the same thing.

This is probably your best bet to get it work quickly. It would not be
surprising to have other IIIF implementations in the wild not supporting
"baseUriRedirect". For TEI-publisher, it is also a matter of supporting
"level 0" implementations of the Image API, where baseUriRedirect is not
a required feature.

>
> 2. Perhaps a kind soul at the BnF who is monitoring this group (or a kind soul who knows who to talk to in the BnF) could ask if there is a way of getting the image service fixed.

I can do that, I am in contact with the developer in charge of IIIF at
the BnF.

Régis