<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Matt,
<div><br>
</div>
<div>Sorry, I missed one of the subtleties of this when reading your original message.</div>
<div><br>
</div>
<div>It seems to me there is a bug in the admin interface. If the empty classifications show up in public, they did in fact migrate, and there absolutely needs to be a way to view, edit, and delete them on the admin side. I had not noticed this issue during
migration testing, but the ability to manually delete empty classifications should be a core requirement/functionality of the system, and I will add that to the product backlog in JIRA.</div>
<div><br>
</div>
<div>Chris Prom</div>
<div><br>
<div>
<div>On Mar 18, 2015, at 9:51 AM, Matthew J Gorzalski <<a href="mailto:mGorzalski@lib.siu.edu">mGorzalski@lib.siu.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 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;
font-family:"Georgia",serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.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]-->
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">Chris,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">Then I am not sure how to address our issue. I planned on deleting the empty classifications in the Aspace admin interface. But like I said, only 5 classifications were listed
instead of the 30 I expected, because 30 appear in the public interface. And of the listed 5, only University Archives was “correct” in that it had the collections attached to it. The other classifications were the empty ones, and therefore the correct versions
didn’t appear in the classification admin interface.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">We tried deleted the bad ones from the database end and re-indexing. It partially worked in that the bad classifications were deleted but the links to those bad classifications
still appeared in the ArchivesSpace public view. Even so, that doesn’t address the problem of the bad classifications being migrated to the administrative classification menu while NOT listing the correct ones as well. If all 30 were listed I could delete
the empty ones.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">Matt<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Prom, Christopher John<br>
<b>Sent:</b> Tuesday, March 17, 2015 4:57 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] UPDATE: classification issue<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I don't think it will be possible to do your number 1 below and possibly also number 2 would be risky.
<span style="font-size:12.0pt"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The underlying issue here is that the classifications are not scoped to a repository in Archon—there is one classification hierarchy that is shared, whereas in aspace the model is that each repo has its own classification system. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The only way to scope it would be to check empty for a particular classification post migration, then delete them, and we saw that as a risky assumption when designing the migration tools.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Chris Prom<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On Mar 17, 2015, at 4:35 PM, Matthew J Gorzalski <<a href="mailto:mGorzalski@lib.siu.edu">mGorzalski@lib.siu.edu</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">When I previously mentioned that only 5 classifications appear in the ASpace classification admin menu instead of the 30 I expected, unfortunately the Manuscripts classification
that migrated is one of the empty or “bad” classifications. See screen shot. You should see a list of records instead of “no records found” if this was the Manuscripts classification
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">In other words, the public interface shows 5 manuscript classifications, one of which actually has collections attached to it. The ASpace admin interface shows only 5 classifications,
and the Manuscript classification that happens to be there is one of the empty Manuscript classifications. In fact, the same goes for our Political Papers and Photographs classifications, and Rare Books classifications. Only University Archives migrated
the correct classification to the ASpace admin classification interface.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">Is it possible to rework the migration to: 1) not duplicate classifications per repository, and 2) ensure that the classifications with attached collections are the ones that appear
in the ASpace classification administrative menu?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">I’ve typed classification too much.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif">MATT GORZALSKI</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif">University Archivist</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#660000">MORRIS LIBRARY</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#660000">MAIL CODE 6632</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#660000">SOUTHERN ILLINOIS UNIVERSITY</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#660000">605 AGRICULTURE DR</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#660000">CARBONDALE, IL 62901</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#660000"> </span><o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:mgorzalski@lib.siu.edu"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif">mgorzalski@lib.siu.edu</span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif">P: 618/453-2225</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif">F: 618/453-3440</span><o:p></o:p></p>
<p class="MsoNormal"><a href="http://lib.siu.edu/"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif">lib.siu.edu</span></a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><empty_classification_migrate.jpg>_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
</span><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Archivesspace_Users_Group@lyralists.lyrasis.org</span></a><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</span></a><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span></p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>