<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><font size="4" class="">Error messages/images are too compressed or small to read. Just a blur. Can you resend or else transcribe ? — Steve M.</font><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 16, 2019, at 2:52 PM, Michael G Olson <<a href="mailto:mgolson@stanford.edu" class="">mgolson@stanford.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi everyone,
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">.<span id="cid:F9667546-C659-4BE4-90B8-F0FECF129BE6@stanford.edu"><cub_001.jpeg></span></div>
<div class=""><br class="">
</div>
<div class="">For this particular example here is how our extents had been entered in application.</div>
<div class=""><br class="">
</div>
<div class=""><span id="cid:37E27617-7C70-41B3-9EAD-24F61085F107@stanford.edu"><cub_002.jpeg></span></div>
<div class=""><br class="">
</div>
<div class="">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!</div>
<div class=""><br class="">
</div>
<div class="">Michael</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
_______________________________________________<br class="">Archivesspace_Users_Group mailing list<br class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br class=""></div></blockquote></div><br class=""></div></body></html>