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

[Alexander Duryee]

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>
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 <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu>
> *Sent:* Wednesday, October 16, 2019 12:15 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
>
>
> 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> 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
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderduryee at nypl.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191016/4941f665/attachment.html>