<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear Colleagues,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Our TEST instance of ArchivesSpace was successfully upgraded to version 2.1.2 over the weekend and is now available for staff use. Overall, everything looks good following the upgrade, but I just want to alert you to one issue we’ve encountered.
After creating and saving a new archival object in a resource record in TEST, the object saves and indexes to the database successfully, but it does not fully render in the staff interface until after the user refreshes their web browser. After refreshing
the browser, the new component immediately appears as it was created and saved and can be edited with no problems. We are fairly certain that this is happening because of some issue with our own hosted instances of ArchivesSpace, and that it is not a system-wide
software bug (I performed the same task in the ArchivesSpace sandbox version, which is running on version 2.1.2, and this problem did not occur). Melissa Wisner will report this issue to Lyrasis in order to find a cause and resolution, and we will certainly
make sure it is resolved before PROD is upgraded to version 2.1.2. If anyone has any questions, please don’t hesitate to contact me.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All best,<o:p></o:p></p>
<p class="MsoNormal">Matthew (on behalf of the Yale Archival Management Systems Committee)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Matthew Gorham<o:p></o:p></p>
<p class="MsoNormal">Assistant Head of the Manuscript Unit for Processing<o:p></o:p></p>
<p class="MsoNormal">Beinecke Rare Book & Manuscript Library, Yale University<o:p></o:p></p>
<p class="MsoNormal">P.O. Box 208330<o:p></o:p></p>
<p class="MsoNormal">New Haven, CT 06520-8330<o:p></o:p></p>
<p class="MsoNormal">203.432.7364<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:matthew.gorham@yale.edu">matthew.gorham@yale.edu</a><o:p></o:p></p>
<p class="MsoNormal"><a href="http://www.library.yale.edu/beinecke">www.library.yale.edu/beinecke</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>