[Archivesspace_Users_Group] reordering from merge

Wed Mar 25 07:22:25 EDT 2015

Hi Matt,

I made a ticket here: https://archivesspace.atlassian.net/browse/AR-1172 and put a fix in for the next release.

Merging was being done by order of the component's id rather than position, so components were being inserted and positioned in correctly.

best, chris.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of MATTHEW R FRANCIS <mrf22 at psu.edu>
Sent: Monday, March 23, 2015 11:06 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] reordering from merge

Correct.  I also should mention that so far we have only observed this happening at the highest level present in the hierarchy.  For instance the series will shift from "1, 2, 3, 4, and 5" to "4, 2, 5, 1, and 3", but all of the components under those series have maintained their original sequence.  However based on some of the other conversations I have been a part of I am not sure this experience matches others who have had reordering from merge issues.

Thanks again.

-Matt

Matt Francis
Archivist for Collection Management
Special Collections Library
Penn State University

Twitter: @archivingmatt
http://www.archivingmatt.com

________________________________
From: "Chris Fitzpatrick" <Chris.Fitzpatrick at lyrasis.org>
To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org>
Sent: Monday, March 23, 2015 5:13:42 PM
Subject: Re: [Archivesspace_Users_Group] reordering from merge

Hi Matt,

Ok, so you merge Resource A ( with components A.1, A.2, A.3, A.4 ) into Resource B ( with no components ) and the result is Resource B now has something like A.2, A.4, A.3, A.1, that is Resource A's components in mixed order?

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of MATTHEW R FRANCIS <mrf22 at psu.edu>
Sent: Monday, March 23, 2015 9:47 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] reordering from merge

Chris,

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.

Thanks for the quick response.

-Matt

Matt Francis
Archivist for Collection Management
Special Collections Library
Penn State University

Twitter: @archivingmatt
http://www.archivingmatt.com

________________________________
From: "Chris Fitzpatrick" <Chris.Fitzpatrick at lyrasis.org>
To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org>
Sent: Monday, March 23, 2015 4:37:11 PM
Subject: Re: [Archivesspace_Users_Group] reordering from merge

Hi Matt,

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.

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?

b,chris.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of MATTHEW R FRANCIS <mrf22 at psu.edu>
Sent: Monday, March 23, 2015 7:30 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] reordering from merge

All,

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.

-Matt

Matt Francis
Archivist for Collection Management
Special Collections Library
Penn State University

Twitter: @archivingmatt
http://www.archivingmatt.com

________________________________
From: "Lora Davis" <ljdavis at colgate.edu>
To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org>
Sent: Monday, March 9, 2015 7:02:23 PM
Subject: Re: [Archivesspace_Users_Group] reordering from merge

No advice to offer, but to express a simple "you are not alone."

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."

I've stopped with this work for the time-being in the hopes that the upcoming patch might help.  Fingers firmly crossed.

Lora

On Mon, Mar 9, 2015 at 1:46 PM, MATTHEW R FRANCIS <mrf22 at psu.edu<mailto:mrf22 at psu.edu>> wrote:
All,

I recently encountered a "new for us" reordering problem while working in ASpace v.1.1.2.

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.

Not sure if anyone else has encountered this issue, but thought it was worth reporting.

-Matt

Matt Francis
Archivist for Collection Management
Special Collections Library
Penn State University

Twitter: @archivingmatt
http://www.archivingmatt.com

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

--
Lora J. Davis
Collections Archivist
Colgate University Libraries
13 Oak Drive
Hamilton, NY 13346
Tel:  (315) 228-6376
Fax: (315) 228-7934

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150325/5f887227/attachment.html>