<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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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">Hi, <o:p></o:p></p>
<p class="MsoNormal"> You may remember I previously asked about problems with sorting Top Containers search results by Indicator. A developer here identified the code that governs this sort. He describes it thus, lightly edited:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%">It seemed like they were sorting by length, but they’re actually doing something to divide the set of results first into those with indicators
that begin with numbers and those that do not. When it starts with a number, they select the starting numbers until they hit a letter or special character (like a -), add padding #’s to the beginning until it is 255 characters long, then do it AGAIN with the
full value of the indicator, resulting in a 510 character string that looks like the below monster (example is using indicator “42a”):<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%">#############################################################################################################################################################################################################################################################42############################################################################################################################################################################################################################################################42a<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%">When the indicator does NOT start with a number, it still does the above, but instead of the first step (#’s + the number) it only adds
#’s. So, for the indicator S015.25 you get a whole ton of #’s plus the indicator at the end:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%">######################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################S015.25<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%">Then these really long strings are what the Indicator field is sorted by, which results in them being both sorted by length AND by whether
they start with a letter or number (during a sort, # symbols are sorted before 0-9 numbers, so indicators that start with a non-number character always appear first).</span><span style="color:#2F5597;mso-style-textfill-fill-color:#2F5597;mso-style-textfill-fill-alpha:100.0%"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This, for us, results in an ascending order like this, dropping out intermediate TCs that sort correctly. You can see why this is not desirable:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">>12<o:p></o:p></p>
<p class="MsoNormal">M-1<o:p></o:p></p>
<p class="MsoNormal">AM-2<o:p></o:p></p>
<p class="MsoNormal">M-14<o:p></o:p></p>
<p class="MsoNormal">XL03<o:p></o:p></p>
<p class="MsoNormal">AM-10<o:p></o:p></p>
<p class="MsoNormal">PS-88-PS-100<o:p></o:p></p>
<p class="MsoNormal">WW-212-WW351<o:p></o:p></p>
<p class="MsoNormal">PS-101-PS-102<o:p></o:p></p>
<p class="MsoNormal">WW-495-WW-630<o:p></o:p></p>
<p class="MsoNormal">H MS c30.4. (Folio)<o:p></o:p></p>
<p class="MsoNormal">Cylindrical case, Roll #7<o:p></o:p></p>
<p class="MsoNormal">1-35<o:p></o:p></p>
<p class="MsoNormal">1-6 and 1-7<o:p></o:p></p>
<p class="MsoNormal">1 (Paige box)<o:p></o:p></p>
<p class="MsoNormal">2<o:p></o:p></p>
<p class="MsoNormal">2-1<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Are you aware of any background or functional spec for the current Top Container Indicator sort?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for any thoughts on this,<o:p></o:p></p>
<p class="MsoNormal">Robin<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Robin Wendler<o:p></o:p></p>
<p class="MsoNormal">Library Technology Services<o:p></o:p></p>
<p class="MsoNormal">Harvard University<o:p></o:p></p>
<p class="MsoNormal">90 Mt. Auburn St.<o:p></o:p></p>
<p class="MsoNormal">Cambridge, MA 02138<o:p></o:p></p>
<p class="MsoNormal">617-998-5457<o:p></o:p></p>
<p class="MsoNormal">r_wendler@harvard.edu<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>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Wendler, Robin King<br>
<b>Sent:</b> Friday, November 22, 2019 3:37 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] Sorting Top Containers by indicator inaccurate?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello, <o:p></o:p></p>
<p class="MsoNormal"> In our installation of ASpace, sorting Top Containers by Indicator in a Manage Top Containers result set is inaccurate. There is a ticket in JIRA
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D889&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=JKUSUWdXrLBGP_rNc_JtcJNO9wvGRzWSZ2uoZzcT59w&m=dxhmnTDQh9Jv3kcuwCKYew6_y5I8CF8hcwK3qc2ANFE&s=CYnmLODmupoEXtepgBbG1g3wYzUycDph6guTIHtnEXo&e=">
https://archivesspace.atlassian.net/browse/ANW-889</a> (Default numerically sort Top Containers in "Manage Top Container" Resource results), which is
<i>not</i> what we want. We want the alphanumeric sort to be accurate. For example, we see results supposedly sorted by indicator that contain a sequence like this:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Iowa 1<o:p></o:p></p>
<p class="MsoNormal">…<o:p></o:p></p>
<p class="MsoNormal">Iowa 9<o:p></o:p></p>
<p class="MsoNormal">Ohio 1<o:p></o:p></p>
<p class="MsoNormal">…<o:p></o:p></p>
<p class="MsoNormal">Ohio A<o:p></o:p></p>
<p class="MsoNormal">Iowa 10<o:p></o:p></p>
<p class="MsoNormal">..<o:p></o:p></p>
<p class="MsoNormal">Iowa 55<o:p></o:p></p>
<p class="MsoNormal">Texas 1<o:p></o:p></p>
<p class="MsoNormal">…<o:p></o:p></p>
<p class="MsoNormal">Texas 9<o:p></o:p></p>
<p class="MsoNormal">Kansas 1<o:p></o:p></p>
<p class="MsoNormal">…Etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I don’t know if it’s related, but the typeahead search for Top Container from within a Container Instance fails to find any matches for known containers most of the time, and produces flaky results when it does.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are planning on tackling both of these during an upcoming batch of small container management enhancements, but it would help to know if we are trying to solve a known problem elsewhere in the community, or if it is something peculiar
to our installation. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Have you experienced either of these problems, and if so, have you identified the potential culprit(s)?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your thoughts, <o:p></o:p></p>
<p class="MsoNormal">Robin <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>