[Archivesspace_Users_Group] Top containers as box-folder

[Majewski, Steven Dennis (sdm7g)]

We had this problem as well. See previous thread in mailing list:

http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-November/004238.html


I believe it’s a lot easier to fix the problem in 1.4.2 before migration, where it can be done in MySQL, than to try to fix it afterwards when top_container become independent linked objects: a lot simpler to just change a couple values in a table than to deal with deleting and creating top_containers.

In our case it was a bit more complicated because some of the container type enums had already been merged and changed, so it required pulling info from a previous mysqldump and creating a view over several tables.
In your case, I think you can just lookup the container type ids for “box”, “folder” and “box/folder” and update the container values where type_1_id = [box/folder id] AND type_2_id IS NULL and indicator_1 LIKE “%/%” and indicator_2 is NULL.


You might want to first do some exploring of table values in MySQL to check that there aren’t any false positives. I also tested everything out on a local test server with a database cloned from mysqldump of production database, before trying the procedure on production data.


— Steve.


On Mar 6, 2017, at 12:53 PM, Tony Kurtz <Tony.Kurtz at wwu.edu<mailto:Tony.Kurtz at wwu.edu>> wrote:

Greetings,
I’ve searched around but I don’t think I’ve been able to find an answer to an issue we’re having.  If I’m mistaken I’ll happily endure the embarrassment along with the solution!

We are planning an upgrade from AS 1.4.2 to 1.5 and we are doing an assessment of how our top containers will look post-upgrade.  One of our repositories expresses almost all containers with a type indicator of “box-folder” and a value expressed as a box/folder pair, e.g. “1/1”, “1/2”, etc. (and all box/folder expressions are unique within a collection—i.e., each “b/f” value is not repeated). From what we can tell, it looks like the 1.5 upgrade process will result in top containers being created at the folder level.  However, we want top containers to be at the box level.  Is our assumption correct that top containers will be created as folders?  Does anyone have advice on how best to navigate this so that we can ensure that boxes are our top containers—e.g. is there anything we can do prior to the upgrade to make this work out as we wish, or will we just need to do the work post-ugrade?

Thanks

Tony Kurtz
Western Washington University
_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170306/6ab70d7c/attachment.html>