[Archivesspace_Users_Group] Problem attaching digital objects to resources in ArchivesSpace 3.1.1

Brian Harrington brian.harrington at lyrasis.org
Sun Jun 19 19:07:47 EDT 2022

Hi Scott,

Double-check your “instance_instance_type” controlled value list, and make sure that you have “digital_object” as an option.  ASpace has that hard-coded as the instance type for digital objects, but it sometimes gets deleted.  I’m pretty sure that’s what happened in your case.


Brian Harrington (he/him)
Data Migration Specialist
brian.harrington at lyrasis.org

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Scott Prater <scott.prater at wisc.edu>
Date: Friday, June 17, 2022 at 6:15 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Problem attaching digital objects to resources in ArchivesSpace 3.1.1

We have recently begun testing out attaching digital object Instances to our resources in ArchivesSpace, version 3.1.1.  So far we have no success:  we can create a digital objects, and we can select one and add it to a resource in the Resource edit view, but when we then attempt to save the resource, we get the unhelpful "Validation Error" message with no other information.  The resource is not updated.

I poked around the code, and temporarily disabled the frontend code where validation error exceptions are swallowed (https://github.com/archivesspace/archivesspace/blob/v3.1.1/frontend/app/controllers/application_controller.rb#L366-L388).  I then tried to save the resource with the attached digital object again, and this time saw the swallowed error:

translation missing: validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha

It looks like somehow a type is not getting set, or the backend is mistakenly requiring a type on the digital object.  There is no place I could see in the digital object edit interface where I can select any of those types.  I did select a "Moving image" type on my test digital object, but that did not change the error.

We've upgraded over the years from ArchivesSpace 2.5.1 to 3.1.1, following the upgrade steps for each new release.  Up to now, we haven't had any problems, but perhaps something has been left behind from previous versions?  Or a table is missing in our latest version?  We are running ArchivesSpace locally on our own server;  we have not made any changes to default distributions.

Any help or insight is appreciated (and yes, we did run a full reindex, to no avail).

Thanks in advance,

-- Scott

Scott Prater
Digital Library Architect
UW Digital Collections Center
University of Wisconsin - Madison

Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220619/11720768/attachment-0001.html>

More information about the Archivesspace_Users_Group mailing list