Upgrade ArchivesSpace to 3.5.0

[erussey]

Please upgrade our ArchivesSpace instance to 3.5.0.

I would prefer that we upgrade test first and do some testing before deploying to production to be sure the new version doesn't break any local configurations or plug-ins developed in house.

We are currently on 3.3.1.

Release notes and download: https://archivesspace.org/archives/8469

[abelemlih]

@erussey I emailed the Lyrasis team to request upgrading the Test instance to v3.5.0 of ArchivesSpace. Please refer to this release for the updated configuration: https://github.com/emory-libraries/aspace-deployment/releases/tag/v2024-05-03

[abelemlih]

@erussey ArchivesSpace 3.5.0 is ready for testing on the Test instance. Once approved, I will reach out to Lyrasis for a deploy to production

[erussey]

@abelemlih : There's something in our plug-in for the front end that isn't working. If you look at a resource in the PUI, the Collection organization menu on the right just spins: https://archives-test.libraries.emory.edu/repositories/7/resources/2609

I talked to Lyrasis about this and they attempted a restart and a reindex, but the issue is still there. They suspect that there is an issue with one of our front end plug-ins in the new ASpace version. They aren't seeing any errors in the logs but are seeing errors in the browser:

[erussey]

There may also be a discrepancy between the config files between test and prod. Digital object menus are showing up in test but not in prod. It seems to be this setting that may be set in prod and not in test? https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L502

[erussey]

Another issue is the menus in the PUI are not displaying the names of the repositories:

[erussey]

@abelemlih : Where are we on making the necessary changes to upgrade ASpace? Clare has done some work on the help documentation and I want to be sure it doesn't collide with the work being done on this ticket.

[abelemlih]

@erussey I am going to work on resolving the bugs highlighted above on Friday. My plan is to dedicate the whole day to Aspace enhancements so we can retest the upgrade soon.

[erussey]

Summary of identified bugs during testing (more info and screenshots in previous comments):

• Collection organization tab does not load, preventing view of individual archival objects
• Configuration files between test and prod do not match (see digital object menus)
• Repository names not appearing in the filter and the repository browse (using browse in the header) leads to an error message rather than a display of the repositories

[abelemlih]

@erussey I have been working on resolving the issues above, and the following are my findings:

Collection organization tab does not load, preventing view of individual archival objects

I was able to reproduce this issue locally, and found a solution. On my local, you can now see the collection organization as shown below

Configuration files between test and prod do not match (see digital object menus)

I am not sure what the issue exactly is. We current do not set AppConfig[:pui_hide][:digital_object_badge] in any of our configuration files. It is set by default in the ArchivesSpace repository: AppConfig[:pui_hide][:digital_object_badge] = false

Repository names not appearing in the filter and the repository browse (using browse in the header) leads to an error message rather than a display of the repositories

I was not able to reproduce this issue locally. As seen below, I see the repositories by name and can access the repositories through Browse:

I am not sure what exactly the issue here is, if anything, it could be something wrong in the Test environment. We may need additional guidance from the Lyrasis team since I cannot reproduce it, and we currently do not override the view where it is rendered: https://github.com/archivesspace/archivesspace/blob/master/public/app/views/shared/_only_facets.html.erb

Also, I noticed on the ArchivesSpace repository that they recently resolve some issues with the facets view where the repository names don't show, in this PR: https://github.com/archivesspace/archivesspace/pull/3238. I am not sure if this concerns us and/or whether we should for wait for another bug fix release that contains these changes.

[erussey]

@abelemlih : So glad you figured out the issue with the collection organization. Since you can't reproduce the other two, would it be possible to push through the first fix to test (along with the merged changes from @CB987) which might make it easier to address the second and third with Lyrasis? That would also help us test whether the Aeon plug-in is working properly which we have been unable to do thus far.

[abelemlih]

@erussey I will reach out to Lyrasis with a deploy request to Test, with all the latest changes. Thanks!

[abelemlih]

@erussey Deploy request sent to Lyrasis to deploy v2024-07-05 to Test. This version includes the fix for collection organization tab as well as Clare's latest help page changes.

[abelemlih]

v2024-07-05 with ArchivesSpace 3.5.0 is now live on Test. @erussey this ticket is ready for testing.

[erussey]

@abelemlih : I just sent an email to Lyrasis...it looks like our data in Test is corrupted. I've asked for a data refresh to hopefully address the issue with repositories. The container display you addressed in the latest local Emory plug-in is fixed.