[Archivesspace_Users_Group] PUI & Digital Objects links

Custer, Mark mark.custer at yale.edu
Fri Nov 3 16:05:09 EDT 2017


Just a quick note to say this is really great!!!  I’d love to see the full plugin for this if you can share it.

Have a great weekend,


p.s. I’d also love to have the core code updated at some point to make digital objects a bit easier to find in the context of the finding aid when digital objects are associated with a finding aid.  Something like this:

[cid:image002.png at 01D354BD.84CF0BF0]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Friday, 03 November, 2017 1:27 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] PUI & Digital Objects links

FYI: You can replace the digital object icon in the display with a thumbnail image in a plugin.

[cid:image004.png at 01D354BD.84CF0BF0]

You need to add or modify:  plugins/local/public/views/layout_head.html.erb

[1] Get the controller name, and only run the script for “objects” controller
( both the digital object and linked record view are via objects controller. )

<meta name="controller" content="<%= controller.controller_name %>" />
<script type="text/javascript">
    var controller = $('html head meta[name="controller"]' ).attr('content');
    if ( controller == "objects") {
        $( function() {
            form_url = $( '.objectimage >form' ).attr('action'); console.log( form_url );

[2] (above) get the digital object URL from the form action.

[3] I’m leaving out the bulk of the script which, in our instance is fetching and parsing IIIF manifests to get a thumbnail image URL. Replace with whatever is needed to get a thumbnail for your digital objects.

[4] Replace that icon with the thumbnail URL in an image element.
    ( You might need a more specific selector if the contents of that page changes, but this works for me now ):

         if ( thumb ) {
             $('.objectimage >form >button').children().first().replaceWith( $('<img/>').attr( 'src', thumb ) );

We are using IIIF manifests partly to avoid the issues involved with representing and handling complex digital objects in ArchivesSpace. ( i.e. multiple page images for a single ‘object’ and thumbnail or other different views or representations.  )  ArchivesSpace has the ability to represent digital objects as a hierarchy, but I think we need some standards and conventions about how to do this before it can be useful. Is anyone doing this now ?

— Steve Majewski

On Nov 3, 2017, at 10:43 AM, Tummino, Annie <atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>> wrote:

Mark – thank you! This did the trick, I was just totally missing that File Version sub-record. Happy to have your help so quickly.


Annie Tummino
Stephen B. Luce Library
Interim Library Director
Archivist & Scholarly Communications Librarian

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]On Behalf Of Custer, Mark
Sent: Friday, November 03, 2017 10:39 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] PUI & Digital Objects links


The PUI still has a way to go with integrating digital objects, but the gist is that right now to get the red Digital Record icon badge, you’ll need to use that URI as a File URI subrecord, rather than (or in addition to) the Digital Record identifier.  Here’s a bit more info:  https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-DigitalObjectButtons/Thumbnails<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_wiki_spaces_ADC_pages_103209762_Public-2BInterface-2BDocumentation-2Bfor-2Bstaff-23PublicInterfaceDocumentation-28forstaff-29-2DDigitalObjectButtons_Thumbnails&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=SrRFmMrl8XUHku4QrT-H5G6VtQTGz_O8OpYGUdE2kWM&s=npV_komgbgOWxs4zOy2EjnBav8AdWJVtmo2rVi-wqko&e=>

But it would like something like this in the staff interface:


I hope that helps, even if it’s not an ideal solution 😊


Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171103/4340776e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 111300 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171103/4340776e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 271778 bytes
Desc: image004.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171103/4340776e/attachment-0001.png>

More information about the Archivesspace_Users_Group mailing list