Dear John, Database migrations are cumulative and in most cases you can upgrade directly from any one version of ArchivesSpace to any other without having to go through intervening versions. We call it out in the upgrading documents when that's not the case.
Upgrading to 2.0 or later from a 1.5.x version will require a full reindex of your database, however. If you haven't reindexed yet, be sure to do that, and then see if you're still having this issue. You can do this by deleting the indexer_state and indexer_pui_state files in your data folder. The weekend is probably the perfect time to let that run since it does slow down performance overall. If reindexing doesn't resolve the issue, let us know and we can put a support ticket in for this. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] [cid:image002.png@01D39036.091DD4A0] Applications are now open for the 2018 Catalyst Fund<https://www.lyrasis.org/Leadership/Pages/Catalyst-Fund.aspx> From: archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Eiszner, John W Sent: Friday, February 2, 2018 4:22 PM To: email@example.com Subject: [Archivesspace_Users_Group] Collection components not displaying in Archivesspace 2.2.2 Hello, I'm attempting to upgrade our Archivesspace application from 1.5.4 directly to 2.2.2. Are the database schema updates performed by the setup-database.sh script cumulative over all releases of AS? Or is it necessary to install every intervening version (2.0.0, 2.1.0, etc.) and run its setup-database.sh script separately, in release order? Database version from schema_info for our current 2.2.2 installation is 95. Also, in the staff interface of AS 2.2.2, when we select a repository, hit Browse, Resources, choose a particular collection and hit Edit, the component detail for that collection is not displaying. It displays fine in the old version (1.5.4), so is it possible some data got munged or lost during the copy and setup-database from 1.5.4 to 2.2.2? The HTML returned from this command contains an ID "tree-unexpected-failure"-does that mean anything? John Eiszner, Lead Analyst/Programmer University Library Indiana University-Purdue University Indianapolis (IUPUI) jeisz...@iupui.edu<mailto:jeisz...@iupui.edu> 317.274.0751
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group