<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} @font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.EmailStyle17
{font-family:"Times New Roman","serif";
color:windowtext}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<p>Hi Angela,</p>
<p><br>
</p>
<p>Thanks for this. Both issues are known bugs that have fixes in place for the next release coming at the end of this month. Issue 1 is one where editing subjects has to include a callback to reindex the resource record, since the "Related Resource" widget
is simply doing a text search for the subject terms. The link is still there in the database ,which is why you can see the subject still linked in the resource page.</p>
<p><br>
</p>
<p>Issue #2 has also been a problem for several people. What's happening is that the subjects are being sorted on their subject id, rather than the id that relates the subject to the resource. Therefore, the subject that's displayed first is the subject that
was created in the system first...not the subject that was related to the resource first. This has also been fixed and will be resolved in the next release.</p>
<p><br>
</p>
<p>Sorry about about the issues, but thanks for reporting them to the list. It's very much appreciated.</p>
<p><br>
</p>
<p>b,chris. <br>
</p>
<p><br>
</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div class="BodyFragment"><font size="2">
<div class="PlainText">Chris Fitzpatrick | <font size="2">Developer, ArchivesSpace</font><br>
Skype: chrisfitzpat | Phone: 918.236.6048<br>
http://archivesspace.org/<br>
</div>
</font></div>
</div>
</div>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Angela Kroeger
<akroeger@unomaha.edu><br>
<b>Sent:</b> Thursday, September 18, 2014 7:14 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] Agent and subject records losing links to resource records and changing sort order of terms and subdivisions</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">I have two related issues with subject and agent records.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">Background: Subject records presently have all terms and subdivisions strung together in a single field. Likewise, agent records presently have the primary part of name
and all subordinate units strung together in a single field. We would like to break these out into separate subfields (e.g.: subjects into terms with subdivisions, agents into primary part of name with subordinate names). However, we've run into two problems.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">Issue #1. This happens every time I edit an agent record or a subject record:
</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">If I change even a single character in the primary part of name field (for agents) or first term field (for subjects), that record loses track of all of the resource
records that it had been linked to. That is, before editing the record, it shows a list of all linked records. After editing the record, it shows "No records found" under linked records. The only way I've been able to fix this is to manually edit each resource
record containing that agent/subject by deleting that agent/subject from the resource record and then adding it back in and re-linking it. Is this a bug? It seems to me that if you change form of a name/subject, all resource records linked to that name/subject
should still be linked to that name/subject. </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">To be clear: we can see the agents/subjects in the resource records--we can even follow the link from the resource record to the agent/subject record, but we cannot see
a list of linked resource records from the agent/subject record. Even if we arrived at the agent/subject record by following a link from a resource record, the agent/subject will show no linked records, not even the one we just came from. So maybe the links
really are present, but are not displaying in the agent or subject records? Is there a fix for this? Waiting a few days for the system to re-index did not help.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">Issue #2. This happens sometimes, but not all the time, and I can't figure out the pattern:
</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">Sometimes when we edit a subject record to put each element into a separate term/subdivision, the record will not retain the correct order of those terms and subdivisions.
For example, we had the subject Artist-in-residence programs -- Nebraska -- Omaha, which is a legitimate LCSH with geographic subdivisions. When I edit the record to put Artist-in-residence programs as a topical term followed by Nebraska and Omaha as separate
geographic terms, as soon as I save the record, ArchiveSpace automatically re-sorts the terms into this incorrect order: Nebraska -- Omaha -- Artist-in-residence programs. When I edit the record to re-sort them into the proper order, they revert to the incorrect
order the instant I save the record. </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">And it's not just that it wants to put the geographic terms first. I've had it go the opposite way. Another example is Omaha (Neb.) -- History. This is a legitimate LCSH
in correct order. Yet when I separated it into Omaha (Neb.) as a geographic term followed by History as a topical term, the moment I save the record, ArchivesSpace incorrectly sorts History to the first term. As with the first example, when I manually correct
the order, the moment I save, it reverts to the incorrect order.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">Any ideas on how to enforce our manual sort order for terms and subdivisions? Is this a bug that will be fixed in an upcoming release?</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">I am reluctant to split our subjects into their component terms and subdivisions if we cannot rely on them staying in the correct order.
</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">I have not yet had this happen when splitting a name into primary and subordinate parts in an agent record (but then, I've only tried it with one agent record). However,
the experience with subject records has made me feel less confident that the pieces will reliably stay in order. (Also, because of issue #1 above, breaking a name into components requires re-linking it from all resource records, another reason I haven't tested
this with a large sampling of records.)</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">Thank you. I appreciate any help anyone can offer.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""> </span></p>
<p class="MsoNormal">Angela Kroeger</p>
<p class="MsoNormal">akroeger@unomaha.edu</p>
<p class="MsoNormal">Archives and Special Collections Associate</p>
<p class="MsoNormal">Dr. C.C. and Mabel L. Criss Library</p>
<p class="MsoNormal">University of Nebraska at Omaha</p>
<p class="MsoNormal">(402) 554-4159</p>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</body>
</html>