<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Chris,<br></div><div><br></div><div>That would be correct for the desired behavior. That said the issue has also been occurring when merging a resource record with an inventory into a resource record without an inventory (which can be a common practice for our local workflows), so post-merge there will only be the components from the one inventory, but now in a different sequence.</div><div><br></div><div>Thanks for the quick response.</div><div><br></div><div>-Matt</div><div><br></div><div><span name="x"></span><span face="georgia, serif" size="2" data-mce-style="font-family: georgia, serif; font-size: small;" style="font-family: georgia, serif; font-size: small;">Matt Francis</span><div><span face="georgia, serif" size="2" data-mce-style="font-family: georgia, serif; font-size: small;" style="font-family: georgia, serif; font-size: small;">Archivist for Collection Management</span></div><div><span face="georgia, serif" size="2" data-mce-style="font-family: georgia, serif; font-size: small;" style="font-family: georgia, serif; font-size: small;">Special Collections Library<br>Penn State University</span></div><div><span face="georgia, serif" size="2" data-mce-style="font-family: georgia, serif; font-size: small;" style="font-family: georgia, serif; font-size: small;"><br></span></div><div><span face="georgia, serif" size="2" data-mce-style="font-family: georgia, serif; font-size: small;" style="font-family: georgia, serif; font-size: small;">Twitter: @archivingmatt</span></div><div><span face="georgia, serif" size="2" data-mce-style="font-family: georgia, serif; font-size: small;" style="font-family: georgia, serif; font-size: small;">http://www.archivingmatt.com</span></div><span name="x"></span><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Chris Fitzpatrick" <Chris.Fitzpatrick@lyrasis.org><br><b>To: </b>"Archivesspace Users Group" <archivesspace_users_group@lyralists.lyrasis.org><br><b>Sent: </b>Monday, March 23, 2015 4:37:11 PM<br><b>Subject: </b>Re: [Archivesspace_Users_Group] reordering from merge<br><div><br></div>
<style style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p style="margin-top: 0px; margin-bottom: 0px;">Hi Matt,</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">Hm, actually the reordering on merge issue was not addressed in this fix. I can look at this quickly tomorrow and probably have something to resolve this.
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">I assume the desired behavior would be to have the series level added to the bottom of the target collection? That is, Resource A is merged into Resource B, so Resource A's component will now all be at the bottom
of Resource B's series list. Does that sound alright? </p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">b,chris. <br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<div id="Signature">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div class="BodyFragment"><span size="2" data-mce-style="font-size: small;" style="font-size: small;">
<div class="PlainText">Chris Fitzpatrick | <span size="2" data-mce-style="font-size: small;" style="font-size: small;">Developer, ArchivesSpace</span><br>
Skype: chrisfitzpat | Phone: 918.236.6048<br>
http://archivesspace.org/<br>
</div>
</span></div>
</div>
</div>
<div style="color: rgb(33, 33, 33);">
<hr style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><span data-mce-style="font-size: 11pt; color: #000000; font-family: Calibri, sans-serif;" style="font-size: 11pt; color: #000000; font-family: Calibri, sans-serif;" face="Calibri, sans-serif" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of MATTHEW R FRANCIS
<mrf22@psu.edu><br>
<b>Sent:</b> Monday, March 23, 2015 7:30 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] reordering from merge</span>
<div> </div>
</div>
<div>
<div style="font-family:times new roman,new york,times,serif; font-size:12pt; color:#000000">
<div>All,<br>
</div>
<div><br>
</div>
<div>As a follow-up on the previously reported reordering from merge issue I wanted to report that we are still experiencing the same problem after the installation of the new 1.21.2 maintenance plug-in. On the bright side, during our limited testing we have
not yet encountered any other scenarios for reordering.</div>
<div><br>
</div>
<div>-Matt</div>
<div><br>
</div>
<div><span></span><span style="font-family:georgia,serif; font-size:small">Matt Francis</span>
<div><span style="font-family:georgia,serif; font-size:small">Archivist for Collection Management</span></div>
<div><span style="font-family:georgia,serif; font-size:small">Special Collections Library<br>
Penn State University</span></div>
<div><span style="font-family:georgia,serif; font-size:small"><br>
</span></div>
<div><span style="font-family:georgia,serif; font-size:small">Twitter: @archivingmatt</span></div>
<div><span style="font-family:georgia,serif; font-size:small">http://www.archivingmatt.com</span></div>
<span></span><br>
</div>
<hr id="zwchr">
<div style="color:#000; font-weight:normal; font-style:normal; text-decoration:none; font-family:Helvetica,Arial,sans-serif; font-size:12pt">
<b>From: </b>"Lora Davis" <ljdavis@colgate.edu><br>
<b>To: </b>"Archivesspace Users Group" <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Sent: </b>Monday, March 9, 2015 7:02:23 PM<br>
<b>Subject: </b>Re: [Archivesspace_Users_Group] reordering from merge<br>
<div><br>
</div>
<div dir="ltr">No advice to offer, but to express a simple "you are not alone."
<div><br>
</div>
<div>I've recently begun doing the same - merging detailed collection-level records created during a collection inventory with existing container lists ead-ified from Excel thanks to the new ASpace-friendly update to Steady. The first (small) collection merged
beautifully with all components remaining in desired order; following the exact same procedures a second, much larger (of course!) collection came out as what I've taken to lovingly calling "component soup."</div>
<div><br>
</div>
<div>I've stopped with this work for the time-being in the hopes that the upcoming patch might help. Fingers firmly crossed.</div>
<div><br>
</div>
<div>Lora</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Mar 9, 2015 at 1:46 PM, MATTHEW R FRANCIS <span dir="ltr">
<<a href="mailto:mrf22@psu.edu" target="_blank">mrf22@psu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div>
<div style="font-family:times new roman,new york,times,serif; font-size:12pt; color:#000000">
<div>All,</div>
<div><br>
</div>
<div>I recently encountered a "new for us" reordering problem while working in ASpace v.1.1.2.</div>
<div><br>
</div>
<div>This time the reordering occurred when you used the merge function to merge together two resources records (was attempting to merge a resource record with an inventory and minimum collection level data into a resource record with rich collection level
inventory but no inventory) . Once the merge was complete the series were reordered in a random fashion (e.g. it went series 9, 11, 2, 1, 6, etc.), but the original order for all the archival objects under each series was maintained.</div>
<div><br>
</div>
<div>Not sure if anyone else has encountered this issue, but thought it was worth reporting.</div>
<div><br>
</div>
<div>-Matt </div>
<div><br>
</div>
<div><span style="font-family:georgia,serif; font-size:small">Matt Francis</span>
<div><span style="font-family:georgia,serif; font-size:small">Archivist for Collection Management</span></div>
<div><span style="font-family:georgia,serif; font-size:small">Special Collections Library<br>
Penn State University</span></div>
<div><span style="font-family:georgia,serif; font-size:small"><br>
</span></div>
<div><span style="font-family:georgia,serif; font-size:small">Twitter: @archivingmatt</span></div>
<div><span style="font-family:georgia,serif; font-size:small"><a href="http://www.archivingmatt.com" target="_blank">http://www.archivingmatt.com</a></span></div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>Lora J. Davis<br>
Collections Archivist<br>
Colgate University Libraries<br>
13 Oak Drive<br>
Hamilton, NY 13346
<div>Tel: (315) 228-6376<br>
Fax: (315) 228-7934</div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
Archivesspace_Users_Group@lyralists.lyrasis.org<br>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>Archivesspace_Users_Group mailing list<br>Archivesspace_Users_Group@lyralists.lyrasis.org<br>http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br></div><div><br></div></div></body></html>