<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">Hello,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u>Background of Issue<o:p></o:p></u></b></p>
<p class="MsoNormal">Several staff have encountered errors in ASpace the past several days when editing archival object records. We believe the underlying issue is that certain records have again fallen out of sequence, and the records are locked down preventing
any edits to be saved. Lyrasis believes this is an issue in the API, recently used to batch update content in ASpace. YUL will refrain from use of the API In this capacity until Lyrasis has resolved the issues in the next core release.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u>Suggested Resolution<o:p></o:p></u></b></p>
<p class="MsoNormal">We have decided the most comprehensive and believe it or not fastest path to resolution is to run a full database resequence on the PROD database. Lyrasis has done this twice successfully on our db, once when we started the pilot in October
2015 and again after we migrated our local db to their hosted service for production use.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u>Dates/Times<o:p></o:p></u></b></p>
<p class="MsoNormal">The <b>resequence will begin after 6pm EDT on Friday 3/4 (tomorrow). PROD ASpace will be unavailable until Monday morning, 3/7, at 8am EDT</b>. This maintenance window allows the resequence to complete and for tech support to conduct basic
QC after the resequence completes. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u>Application Dependencies<o:p></o:p></u></b></p>
<p class="MsoNormal">The <b>ASpace-Aeon addon</b> and lookup service (primarily used by MSSA) will be redirected to the TEST instance of ASpace for the weekend. This TEST instance is recent within 1 week of data. It will be redirected back to PROD once success
is verified with the resequence.<o:p></o:p></p>
<p class="MsoNormal">The <b>AS-LSF location update program</b> will NOT run the evening of Friday 3/4. MSSA does have a scheduled transfer of archival materials, which LIT will update with a course-correction run of the program later next week.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u>Reporting Issues Next Week<o:p></o:p></u></b></p>
<p class="MsoNormal">I will be at a conference next week. I will work with Lyrasis over the weekend to QC the results of the resequence and communicate our status to this group. If any emergencies come up with ASpace next week (system down, staff unable to
do any work in ASpace) please email <a href="mailto:libraryit@yale.edu">libraryit@yale.edu</a> If any minor issues come up, please feel free to report via Service Now,
<a href="mailto:libraryit.entsys@yale.edu">libraryit.entsys@yale.edu</a> I will be monitoring email for issues and can do some work from the conference. The YAMS committee is also available for first level support.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for your help in reporting the initial issue and for your patience as we work with Lyrasis to resolve it.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Melissa Wisner<o:p></o:p></p>
<p class="MsoNormal">Library IT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>