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

[Joshua D. Shaw]

Are there any children for this tree - ie any archival objects underneath? If not, this may be related to this issue: https://archivesspace.atlassian.net/browse/ANW-782

Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Blake Carver <blake.carver at lyrasis.org>
Sent: Wednesday, October 16, 2019 9:35 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0

If you brought over the /data/ directory, try getting rid of everything in there and restarting. Could just be an index issue.
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Michael G Olson <mgolson at stanford.edu>
Sent: Wednesday, October 16, 2019 6:17 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0

Hi Alex,

Great ideas, thank you!  We didn’t get any errors when we ran the upgrade.  I just took a look at this resource in the Java console.  I didn’t see any obvious errors in the Java script consul but I was able to see the logic that should be generating the tree view.  My best guess is that what is going on is that we were using extents on the collection resource in a way that was not actually intended.  We also have a few examples where our archivist correctly encoded constituent parts as proper child objects and in these particular examples we don’t get a tree view error.

Thanks for your help!

Michael

On Oct 16, 2019, at 2:39 PM, Alexander Duryee <alexanderduryee at nypl.org<mailto:alexanderduryee at nypl.org>> wrote:

Michael,

Do you see anything interesting in the system logs or your browser's Javascript console when you try to open the collection?  I don't see anything in the Extent record that you attached that would cause the Resource record to throw an error like that.

Thanks,
--Alex

On Wed, Oct 16, 2019 at 3:25 PM Michael G Olson <mgolson at stanford.edu<mailto:mgolson at stanford.edu>> wrote:
Hi Steve, all,

Sorry about that… the error message we’re receiving when we click on the Collection tree is, "Oops! We're having trouble fetching this tree. Please try refreshing the page.”

If you open the image titled extent you'll see how our archivist entered the extent for this particular collection.  It looks like this isn't really defined as a true child of the collection.

thanks,

Michael


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu<mailto:sdm7g at virginia.edu>>
Sent: Wednesday, October 16, 2019 12:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0


Error messages/images are too compressed or small to read. Just a blur.  Can you resend or else transcribe ?  — Steve M.


On Oct 16, 2019, at 2:52 PM, Michael G Olson <mgolson at stanford.edu<mailto:mgolson at stanford.edu>> wrote:

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.

.<cub_001.jpeg>

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

<cub_002.jpeg>

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


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C78e4560ac9c846d6c30708d752a25fc9%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C637068729668221228&sdata=jow3IAttd8LejGuVWzriZJvbykVmHmm1rdIGyd18w8Q%3D&reserved=0>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C78e4560ac9c846d6c30708d752a25fc9%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C637068729668221228&sdata=jow3IAttd8LejGuVWzriZJvbykVmHmm1rdIGyd18w8Q%3D&reserved=0>


--
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderduryee at nypl.org<mailto:alexanderduryee at nypl.org>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191017/d24bd19d/attachment.html>