Closed elynema closed 1 week ago
Dananji did not add .json because the ID listed in the manifest does not have .json. Not sure why we set up this ID value to work this way. The benefit of specifying extension is that browser easily recognizes as a .json file.
Ex: "id": "https://avalon-dev.dlib.indiana.edu/media_objects/g158bh28p/manifest"
@elynema Either with or without the .json
extension should work so we could switch to making the extension explicit if that's preferable.
@Dananji The iiif manifest logo is showing up really big in Chrome and Safari for me:
Did you try a hard reload of the page? It seems to be working for me.
I had to variously hard reload and delete cache, but it seems to look fine now.
Description
Currently, the link to the IIIF manifest is in the "Share this resource" panel labeled as "IIIF manifest". This is fine, but the IIIF manifest logo should be next to the "IIIF Manifest" label to help IIIF users find it.
Done Looks Like
See #5733 for the original work