<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
All,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
It looks to me like everything is working as expected now. Thanks for getting this patch up so quickly, Steelsen!</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
As for the patch, Jay Terray deserves full credit for developing that, not me. All that I did was test it out and push it up to our code base.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Kudos also to Melissa Barton for discovering this bug and reporting it so quickly!</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
All my best,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Mark</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Yulyams <yulyams-bounces@mailman.yale.edu> on behalf of Smith, Steelsen <steelsen.smith@yale.edu><br>
<b>Sent:</b> Wednesday, February 5, 2020 10:29 AM<br>
<b>To:</b> yulaspace@mailman.yale.edu <yulaspace@mailman.yale.edu><br>
<b>Cc:</b> yulyams@mailman.yale.edu <yulyams@mailman.yale.edu><br>
<b>Subject:</b> [Yulyams] Production Restart - Thursday 2/6 at 6pm</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
span.x_EmailStyle17
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">Dear ArchivesSpace Users,</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">In mid-January a bug was reported with the requesting functionality in the new Finding Aid View.
</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">In certain circumstances a single click can result in multiple requests for the same item, generating spurious Aeon transactions. This is causing problems for Access Services staff in multiple units.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">This problem was traced by an LIT consultant, Jay Terray ,to a JavaScript bug. Subsequently a patch was developed by Mark Custer. This patch has been applied in the test system and appears to resolve the issue. Moira, as AUG chair, has
signed off on applying this fix, and YAMS cochairs Alicia and Eve have done the same.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Because this problem has been causing operational issues we are trying to deploy the fix as soon as possible. We have confirmed with the vendor that they will be able to
<b>perform a rollout at 6pm on Thursday, February 6. This rollout</b> includes a restart of production and
<b>could result in an outage</b> of both the PUI and the staff interface <b>of up to 10 minutes</b>. Please plan work accordingly.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">If this rollout cannot proceed for any reason then please reach out to me as soon as possible so that alternative plans may be devised.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Thank you,</p>
<p class="x_MsoNormal">Steelsen</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal" align="right" style="text-align:right">___________________________<br>
Steelsen Smith<br>
Technical Lead</p>
<p class="x_MsoNormal" align="right" style="text-align:right">Client Services and IT Operations</p>
<p class="x_MsoNormal" align="right" style="text-align:right">Yale Library IT<br>
203.432.3333</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
</div>
</div>
</body>
</html>