[Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0

[Michael G Olson]

Hi everyone,

Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 and noticed some odd behavior we’d like to validate with our peers.  We received no error messages while running the upgrade.  That said, for one of our repositories (we have many) we’ve noticed that by clicking on the resource tree we get an error message.  I’m speculating here but my guess is that the extent for this resources were not defined in such a way the application knows the relationship between parent and child.  Here is the error message we’re seeing.

.[cid:F9667546-C659-4BE4-90B8-F0FECF129BE6 at stanford.edu]

For this particular example here is how our extents had been entered in application.

[cid:37E27617-7C70-41B3-9EAD-24F61085F107 at stanford.edu]

My questions are has anyone seen this sort of behavior before?  Is this something we can fix in the upgraded application or do we need to implement a fix before the upgrade.  Any insights anyone has on this issue would be much appreciated!

Michael


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191016/0747cdea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cub_001.jpeg
Type: image/jpeg
Size: 3772 bytes
Desc: cub_001.jpeg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191016/0747cdea/attachment.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cub_002.jpeg
Type: image/jpeg
Size: 16694 bytes
Desc: cub_002.jpeg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191016/0747cdea/attachment-0001.jpeg>