<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Steve,</p>
<p><br>
</p>
<p>It's definitely a good idea to be very cautious with SQL updates to the ArchivesSpace db, but in this case I'd argue it's appropriate, as well as being the most straightforward path. There's always more than one way to do it but it's something along the
lines of:</p>
<p><br>
</p>
<p>Create a tmp table of the container ids and split indicator_1 (ind1, ind2) values where type_1 is box:folder</p>
<p>Update container type_1 to box where id is in your tmp box:folder table</p>
<p>Update container type_2 to folder <span style="font-family:Calibri,Arial,Helvetica,sans-serif,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols; font-size:16px">where id is in your tmp box:folder table</span></p>
<p><span style="font-family:Calibri,Arial,Helvetica,sans-serif,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols; font-size:16px">Use the matching id in the tmp table to update indicator_1 -> ind1, indicator_2
-> ind2.</span></p>
<p><span style="font-family:Calibri,Arial,Helvetica,sans-serif,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols; font-size:16px">Reindex (you can be precise about it by looking up related records through container
-> instances and updating their system_mtime, but just doing everything is easiest).</span></p>
<p><br>
</p>
<p>Best,</p>
<p>Mark</p>
<p><br>
</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<span dir="ltr"><font color="black" face="Calibri,Arial,Helvetica,sans-serif" size="3"><span style="font-size:12pt; background-color:white"><font face="Calibri,Arial,Helvetica,sans-serif"><font color="#282828" face="Calibri,Arial,Helvetica,sans-serif"><font color="#2F2F2F" face="Arial,sans-serif"></font></font></font></span></font></span></div>
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>Mark Cooper<br>
</div>
<div>Technical Lead, Hosting and Support</div>
<div>LYRASIS</div>
<div>email: mark.cooper@lyrasis.org</div>
<div>skype: mark_c_cooper<br>
</div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Majewski,
Steven Dennis (sdm7g) <sdm7g@eservices.virginia.edu><br>
<b>Sent:</b> Wednesday, November 16, 2016 8:30:30 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> [Archivesspace_Users_Group] splitting containers encoded as box:folder</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
We have thousands of archival_objects where container type_1 is encoded as “box:folder” ( with some variation of case and punctuation ) and with the value encoded in a similar manner ( i.e. “1:1” )
<br>
<br>
This was our normal encoding practice in EAD. I have since added code to our pre-import stylesheet to split these into separate container elements, but these records have already been imported previous to discovering this issue.
<br>
<br>
It would seem easier to fix and split these values before doing the 1.5.1 migration.
<br>
In test migrations, the result is separate top containers for all of the <br>
I’ve been exploring my options for doing this. <br>
Using the backend API would appear to be too difficult and time consuming, so I’m probably going to shutdown the servers and run the backend server from the console to run a script to convert all of the values. ( I suppose an alternative would be to do the
updates directly from MySQL, but I’ve been advising others not to do this. And I probably feel more comfortable doing it in ruby thru the sequel GEM than directly in MySQL. And I don’t trust EAD roundtripping in ASpace enough to try to export/fix/import via
EAD. ) <br>
<br>
Just wondering if anyone else has had to deal with a similar problem and how it was managed?
<br>
<br>
<br>
— Steve Majewski<br>
<br>
<br>
<br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
Archivesspace_Users_Group@lyralists.lyrasis.org<br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
</div>
</span></font>
</body>
</html>