If you brought over the /data/ directory, try getting rid of everything in 
there and restarting. Could just be an index issue.
________________________________
From: [email protected] 
<[email protected]> on behalf of Michael 
G Olson <[email protected]>
Sent: Wednesday, October 16, 2019 6:17 PM
To: Archivesspace Users Group <[email protected]>
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 
<[email protected]<mailto:[email protected]>> 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 
<[email protected]<mailto:[email protected]>> 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: 
[email protected]<mailto:[email protected]>
 
<[email protected]<mailto:[email protected]>>
 on behalf of Majewski, Steven Dennis (sdm7g) 
<[email protected]<mailto:[email protected]>>
Sent: Wednesday, October 16, 2019 12:15 PM
To: Archivesspace Users Group 
<[email protected]<mailto:[email protected]>>
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 
<[email protected]<mailto:[email protected]>> 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
[email protected]<mailto:[email protected]>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]<mailto:[email protected]>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


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

_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to