<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">I wanted to provide an update to the users about several incidents related to indexing in ASpace. These incidents were reported via the tracking system for Library IT (<a href="mailto:libraryit.entsys@yale.edu">libraryit.entsys@yale.edu</a>
), and while reported by individuals, the issues are systemic and everyone should be aware. I was able to replicate the reported problems in production, but went to see several staff in MSSA to determine if the problem could be replicated in Test ASpace.
I apologize if I do not yet have the full archival lexicon.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u>Incident 1<o:p></o:p></u></b></p>
<p class="MsoNormal"><b>Problem:</b> Staff add new top containers, but only some of them are retrievable via the index (whether through a search, browse, or type ahead feature in various search fields).<o:p></o:p></p>
<p class="MsoNormal"><b>Example:</b> MS 804 Kent State Collection in MSSA<o:p></o:p></p>
<p class="MsoNormal"><b>Replication:</b> This problem can be replicated in production ASpace, but NOT in Test ASpace.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u><o:p><span style="text-decoration:none"> </span></o:p></u></b></p>
<p class="MsoNormal"><b><u>Incident 2<o:p></o:p></u></b></p>
<p class="MsoNormal"><b>Problem:</b> Using ASpace web interface to check which New Accessions have an ‘In Progress’ status does not show all known ‘In Progress’ items. These accessions can be found through other types of searches, but not through the filter
on ‘In Progress.’<o:p></o:p></p>
<p class="MsoNormal"><b>Example:</b> MSSA estimates from the physical pile of folders on Matthew’s desk 2 dozen ‘In Progress’ New Accessions, but only 14 are listed with that status in ASpace. (e.g. Good Vibrations Collection is ‘In Progress’ but does not appear
on a filtered search list).<o:p></o:p></p>
<p class="MsoNormal"><b>Replication:</b> We added 2 new accessions in Test ASpace and they appeared through a filtered search for ‘In Progress’ right away. This is NOT the case in production ASpace.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><u>Incident 3<o:p></o:p></u></b></p>
<p class="MsoNormal"><b>Problem:</b> Importing/merging spreadsheet to an existing FA. File can be imported (the import log shows success and datetimestamp), but it cannot be retrieved through a search (by direct name or even using the ‘import’ prefix).<o:p></o:p></p>
<p class="MsoNormal"><b>Example:</b> Many Office of Origin updates come into MSSA as spreadsheets. Another example is Kroshnitz MS 2013.<o:p></o:p></p>
<p class="MsoNormal"><b>Replication:</b> We imported the Kroshnitz file into Test ASpace and it was immediately retrievable via search. This is NOT the case in production ASpace.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We will try to uncover the issue of inconsistent index behavior across test and production as quickly as possible. We will be utilizing HM and Lyrasis to determine the problem and the permanent solution. Please continue to report any problems
to the incident tracking system. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you to Christine and Matthew for spending time with me to review the problems, and discussing with me how they need the application to perform.<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>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>