Serve Gottschalk images from prod server

[dchiller]

This PR updates the CU-hosted manifest for the Gottschalk reconstruction to serve images from production rather than staging. With Release 3.2-0.12.0 (https://github.com/DDMAL/cantus/releases/tag/v.3.2-0.12.0) these images are on prod, so we can serve them from prod for both staging and production purposes.

[jacobdgm]

I am not at all an expert IIIF manifests, but if the change is to replace staging.simssa.ca with simssa.ca in this entire file, I trust your text editor to have not missed anything. So I'll give my approval for now, but I do think @ahankinson's suggestion makes sense, so probably update that before merging.

[ahankinson]

Also, visiting https://cantus.simssa.ca/iiif/lacuna.jpg redirects you to https://cantaloupe/iiif/2/lacuna.jpg/info.json so there's something up with the server configuration that needs to be fixed.

[dchiller]

Also, visiting https://cantus.simssa.ca/iiif/lacuna.jpg redirects you to https://cantaloupe/iiif/2/lacuna.jpg/info.json so there's something up with the server configuration that needs to be fixed.

There is nothing on the other end of this (ie. there is no info.json resource for the lacuna image -- or for any image we are serving). I'm hesitant to put in the effort for this given that this is an interim solution and #822 is for putting in place something long-term (probably with greater collaboration with the fragmentarium folks). Does it seem important that this happen now?

[dchiller]

The latest commit addresses Andrew's comment. I'm going to merge to make sure at least this change works, but let's continue the discussion.

[ahankinson]

There is nothing on the other end of this (ie. there is no info.json resource for the lacuna image -- or for any image we are serving)

Then it's not IIIF. The base of the URI must resolve to an info.json response -- that's how image viewers find out how many zoom levels there are, tile sizes, etc.

Section 5: https://iiif.io/api/image/3.0/#5-image-information

Servers MUST support requests for image information. The response is a JSON document that includes technical properties about the full image. It may also contain rights information, and services related to the image.

Canteloupe should generate the info.json automatically, so you don't need to write it by hand.

You have a canteloupe response that is looking for the info.json, but it's not configured correctly. Changing it to https://cantus.simssa.ca/iiif/2/lacuna.jpg/info.json almost works too, but something in the URL rewriting is adding an extra /2/ in there.

[dchiller]

Canteloupe should generate the info.json automatically, so you don't need to write it by hand.

Ah, ok. Then yes, just a configuration issue. The extra 2 is nginx. I'm sure the redirect is a default configuration in cantaloupe.