Liz,

We are starting to work on this as part of the specification for 
https://archivesspace.atlassian.net/browse/ANW-1209 (thanks again to Cory for 
doing this work!), which focuses on adding digital object thumbnails in a 
standardized way to both the staff and public interface of ASpace.

As part of that development process, which Hudson Molonglo has done on our 
behalf, we also wanted a standard way to add IIIF manifests.  I hope all of 
this can be added to the core code once it's ready (and we're not implementing 
it in a plugin for that very reason), but the gist is that this approach makes 
it possible to recognize IIIF manifest files and to associate those with a 
viewer.  Here's an example 
https://puitestarchivesspace.library.yale.edu/repositories/11/archival_objects/431642

Certainly more to say on the topic, but I just wanted to respond quickly now 
since I just saw this thread.  I wonder if this approach would work for your 
use case?  I think so, but it would be good to confirm!

Mark


From: [email protected] 
<[email protected]> On Behalf Of Trevor 
Thornton
Sent: Friday, 20 August, 2021 9:15 AM
To: Archivesspace Users Group <[email protected]>
Subject: Re: [Archivesspace_Users_Group] Digital Object Module Use


We're not using the PUI, so our specific implementation is probably not that 
useful. Our finding aids are delivered via a custom Ruby on Rails app, and the 
IIIF manifest is processed into a thumbnail viewer with this Javascript:



https://github.ncsu.edu/ncsu-libraries/collection_guides/blob/master/app/assets/javascripts/thumbnail_viewer.js<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.ncsu.edu%2Fncsu-libraries%2Fcollection_guides%2Fblob%2Fmaster%2Fapp%2Fassets%2Fjavascripts%2Fthumbnail_viewer.js&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955785346%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=yuDkwk5Gp7ea8DwO3fWb5B7F6A%2FyGuoz4001ihbO%2BGc%3D&reserved=0>



The thumbnails link out to our main digital collections site, which uses the 
Universal Viewer:

http://universalviewer.io/<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Funiversalviewer.io%2F&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955785346%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bk3k4KxuUpVEzeGgF8zRCYWT6qDPJQxfCo58%2FQxjVVI%3D&reserved=0>

which takes a manifest URL (like what you have in your DOs) and displays the 
zoomable image, metadata, etc.



I did a little searching and found this presentation abstract:



https://iiif.io/event/2019/goettingen/program/29/<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fiiif.io%2Fevent%2F2019%2Fgoettingen%2Fprogram%2F29%2F&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955795308%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=PKhrgYhx37u8vO3hAVB9dBWPAtF22h1qOqPA%2B6YFfPo%3D&reserved=0>



that mentions a plugin to embed the Universal Viewer in ArchivesSpace. That led 
me here:



https://archives.collections.ed.ac.uk/repositories/2/digital_objects/179<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchives.collections.ed.ac.uk%2Frepositories%2F2%2Fdigital_objects%2F179&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955795308%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fts2X2g8912obVfyQ1QWXZtJw5KntmICQZAw2ddGs2c%3D&reserved=0>



Which doesn't look like it's actually using the Universal Viewer, but I think 
it's doing something close to what you want to do.

On Mon, Aug 16, 2021 at 4:42 PM Liz Neely 
<[email protected]<mailto:[email protected]>> wrote:
Sorry if I'm taking this thread on a turn:

Trevor, I would love to learn more about your implementation or any 
documentation that you accessed to make it work.

We at the Georgia O'Keeffe Museum store DOs as links to IIIF manifests that 
serve our Collections Online 
(example<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcollections.okeeffemuseum.org%2Farchive%2Fcomponent%2Faspace_ef23398f18a4db18283486526d89bf28%2F&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955795308%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=jtZUMXiem9DZEYiPxdkB%2Fsj5%2FHzshKjL5B28eoU7nw0%3D&reserved=0>)
 and linked open data (the data pipeline takes in the EAD). Now that we've also 
published these collections on the PUI, the links appear broken in the PUI 
since the file instance is a link to the manifest (info.json) and not an image 
file. I've been looking around for documentation that recognizes this and 
engages a viewer, but haven't found anything. Am I not looking closely enough?

Any directions would be appreciated!
Thanks,
Liz

Liz Neely (she/her)
Curator of Digital Experience
Georgia O'Keeffe Museum
Santa Fe, New Mexico
[email protected]<mailto:[email protected]>


From: 
[email protected]<mailto:[email protected]>
 
<[email protected]<mailto:[email protected]>>
 on behalf of Trevor Thornton <[email protected]<mailto:[email protected]>>
Date: Thursday, September 17, 2020 at 8:29 AM
To: Archivesspace Users Group 
<[email protected]<mailto:[email protected]>>
Subject: Re: [Archivesspace_Users_Group] Digital Object Module Use
We use digital objects in ArchivesSpace to link archival object records with 
both online resources (mostly digitized images and documents on our digital 
collections 
site<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fd.lib.ncsu.edu%2Fcollections&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955805268%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=UAYGzXnOY5qpblvWZvCwavgKkymfBg7zzJG0ElI9U10%3D&reserved=0>)
 and corresponding packages (AIPs) in our digital preservation repository.

For materials that are published online, the digital object includes the item's 
URL. Our finding aids system uses this URL to access a IIIF manifest for images 
published online, which lets us to include linked thumbnail images within the 
context of the finding aid - here's an example of 
that<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lib.ncsu.edu%2Ffindingaids%2Fmc00456%2Fcontents&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955805268%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=trwgMwZqODhzssOLU5Fqv1SWQddqPAkB4QSEjn10AOk%3D&reserved=0>.

For packages in the preservation repository, we mint a common identifier (UUID) 
that is stored in both systems (in the repo and in AS as the digital object 
identifier), which allows us to link between them.

On Thu, Sep 17, 2020 at 10:11 AM Huggard, Marcella 
<[email protected]<mailto:[email protected]>> wrote:
Hi Bailey,

We're connecting to our digital objects in Islandora - of course, our digital 
management system has way more digital collections available than just what's 
from our manuscript collections, so we try to be very clear and upfront about 
that in our public user interface so researchers know to go to Islandora for 
other digital collections, but we do like the ability to link directly to the 
finding aid. We're also considering ArchivesSpace the single source of truth 
for manuscript collections information online, so having the linked digital 
objects display there falls into that workflow.

Our public interface is at 
https://archives.lib.ku.edu/<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchives.lib.ku.edu%2F&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955805268%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=0eXHM99kizg3duYB%2FgmePa%2FBXZVGpYZDUy9JTsZwC60%3D&reserved=0>
 if you want to take a look!

Marcella

From: 
[email protected]<mailto:[email protected]>
 
<[email protected]<mailto:[email protected]>>
 On Behalf Of Hoffner, Bailey E.
Sent: Friday, September 11, 2020 3:49 PM
To: Archivesspace Users Group 
<[email protected]<mailto:[email protected]>>
Subject: [Archivesspace_Users_Group] Digital Object Module Use

Hello All,

I'm interested in knowing how and why people use (or don't use) the Digital 
Object section of AS. Any input at all would be appreciated - thanks!

-Bailey

Bailey Hoffner, MLIS
Pronouns: she/her/hers
Metadata and Collections Management Archivist
University of Oklahoma Libraries
[email protected]<mailto:[email protected]>
_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]<mailto:[email protected]>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955815217%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3uSEb3mBhFOBqFSI%2BoeNrwe8R8xLUuYbnAJoSQ0DK1Q%3D&reserved=0>


--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]<mailto:[email protected]>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=04%7C01%7Cmark.custer%40yale.edu%7C5a1b4d043ae64f784d6208d963dc7d25%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637650621955815217%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3uSEb3mBhFOBqFSI%2BoeNrwe8R8xLUuYbnAJoSQ0DK1Q%3D&reserved=0>


--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to