Mirador (IIIF) viewer in the Dspace 8 demo

[Gary Hsu]

Dear all, 

I just wanted to take a look at how the IIIF viewer works in the Dspace. However, when selecting an item with an image file, there is no option to open it up in a viewer. 

Is it disabled? Alternatively, can someone show me any Dspace instance that has this function?

Many thanks,

Gary

[DSpace Community]

Hi Gary,

Yes, the demo site (and sandbox site) currently do *not* have the IIIF viewer enabled.  The reason is simply that enabling the IIIF viewer requires also having a IIIF Image Server installed, and that's not installed for the demo or sandbox: https://wiki.lyrasis.org/display/DSDOC8x/IIIF+Configuration

I don't have information on which sites have enabled this feature, but hopefully some will respond to this thread.

If you are comfortable with Docker, it's also possible to run a IIIF server in Docker for testing purposes.  See https://github.com/DSpace/DSpace/tree/main/dspace/src/main/docker-compose#run-dspace-8-rest-with-a-iiif-image-server-from-your-branch

Tim

[Gary Hsu]

Hi Tim, 

I followed your instructions and was able to get the IIIF server running (I set the iiif enable= true as well)

However, next to my image there is still no button for the Mirador viewer as shown by an existing instance.

Did I do something wrong in terms of the process of uploading images? 

Gary

[DSpace Community]

Hi Gary,

When the Mirador viewer is enabled in DSpace 8, it doesn't appear as a button. Instead, you will see the Mirador viewer embedded in the Item page itself.

I was able to find a DSpace site that has it enabled. Here's an example: https://digitalcollections.willamette.edu/items/0b015cd4-61fd-484b-b379-2eddaa6794e0

Notice how the Mirador Viewer appears near the top of the page.  Under it is the usual item details.

That same DSpace site has other artwork that can similarly be viewed in Mirador.

Regarding your local setup, it's not easy for me to debug the issues without more information.  It sounds like you might have been looking on the wrong page though (as the screenshot you shared is of the "Full Item page", which does *not* have the Mirador viewer embedded)

Tim

[Gary Hsu]

Thanks for the tip. 

I tried to enable the Mirador viewer in the angular front end ( by running yarn run start:mirador:prod inside the angular container), but I got the error as the port 4000 is used by the dspace-angular container. 

The solution I can think of is to modify the Dockerfile by adding run "yarn run start:mirador:prod" and rebuild the image. 

Am I on the right track even if the docker is in the development mode?  Can Mirador be used in the development mode?

Or do I need a public URL for the docker in a production mode for Mirador ? 

Gary