Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Hyrax (2.9.6 -> 5.0.0) EPIC #1022

Open
scherztc opened this issue Jul 5, 2023 · 6 comments
Open

Upgrade Hyrax (2.9.6 -> 5.0.0) EPIC #1022

scherztc opened this issue Jul 5, 2023 · 6 comments
Assignees

Comments

@scherztc
Copy link
Contributor

scherztc commented Jul 5, 2023

Descriptive summary

We are on Hyrax version 2.9.6.

Expected behavior

5.0.0

4.0.0 - May 30, 2023 (1.6 MB)
https://github.com/samvera/hyrax/releases/tag/hyrax-v4.0.0

  • Hyrax 4 has seen major upgrades to its dependencies. It now runs on Ruby 3.2 and Rails 6.1. Blacklight has been updated to version 7, and the Bootstrap style framework to version 4.

3.6.0 - June 27, 2023 (1.21 MB)
https://github.com/samvera/hyrax/releases/tag/hyrax-v3.6.0

  • Hyrax 3.6.0 adds support for reporting site usage to Google Analytics 4 (GA4). Existing users of the prior version of Google Analytics (UA) will need to update their applications as it will soon be retired.

3.5.0 - December 09, 2022 (1.21 MB)
https://github.com/samvera/hyrax/releases/tag/hyrax-v3.5.0
3.4.2 - August 24, 2022 (1.21 MB)
https://github.com/samvera/hyrax/releases/tag/v3.4.2
3.4.1 - March 30, 2022 (1.2 MB)
https://github.com/samvera/hyrax/releases/tag/v3.4.1

3.4.0 - March 23, 2022 (1.19 MB)
https://github.com/samvera/hyrax/releases/tag/v3.4.0

3.3.0 - January 24, 2022 (1.18 MB)
https://github.com/samvera/hyrax/releases/tag/v3.3.0

  • Significant improvements to Analytics for Collections and Works
  • Prep work for upcoming Blacklight upgrade
  • Continued progress towards Valkyrie MVP

3.2.0 - November 16, 2021 (1.15 MB)
https://github.com/samvera/hyrax/releases/tag/v3.2.0

  • Read-only mode feature flipper added
  • Collection Model configurable so that Collection class can be named something other than "Collection"
  • Continued Valkyrie work behind the scenes getting closer to MVP - still in progress

3.1.0 - September 09, 2021 (1.14 MB)
https://github.com/samvera/hyrax/releases/tag/v3.1.0
3.0.2 - May 07, 2021 (1.13 MB)
https://github.com/samvera/hyrax/releases/tag/v3.0.2

  • This release adds support for Rails 5.2.6 and other releases containing the fix for GHSA-hjg4-8q5f-x6fm.

3.0.1 - March 31, 2021 (1.12 MB)
https://github.com/samvera/hyrax/releases/tag/v3.0.1
3.0.0 - March 24, 2021 (1.12 MB)
https://github.com/samvera/hyrax/releases/tag/v3.0.0

  • Support for Rails 5.2 and Ruby 2.7 are added; we now recommend Rails 5.2 for all applications.
  • We dropped testing for Ruby 2.4; we now recommend at least Ruby 2.5 for all applications.
  • Out-of-the-box metadata schemas are updated to more closely align with the recommendations of the Samvera Metadata Interest Group.
  • File versions and transparent PNGs are now supported by our IIIF installation. Universal Viewer's install process is improved to use yarn.
  • Valkyrie is introduced as a production dependency and a custom adapter (Wings) is introduced to handle backward-compatible use of Valkyrie within Hyrax. (see more on this below)

Actual behavior

Steps to reproduce the behavior

  1. Upgrade to 3.0
  2. Upgrade to 4.0

Related work

Link to related issues or prior related work here.

@scherztc scherztc added this to the Security and Maintenance milestone Jul 5, 2023
@scherztc scherztc changed the title Upgrade Hyrax Upgrade Hyrax (2.9.6 -> 4.0.0) EPIC Sep 5, 2023
@scherztc scherztc changed the title Upgrade Hyrax (2.9.6 -> 4.0.0) EPIC Upgrade Hyrax (2.9.6 -> 5.0.0) EPIC Sep 5, 2023
@scherztc
Copy link
Contributor Author

@scherztc
Copy link
Contributor Author

We recently upgraded our Hyrax app from Hyrax 2.96 to 3.6. In the course of this upgrade, which also involved Dockerizing the app, we moved from Fedora 4.7.1 to 4.7.5. Because we had trouble with the Fedora import/export tool, we simply copied over all the Fedora and Solr core data on disk to the new image, and at first glance, everything seems to be working fine. However, reindexing causes loss of some metadata fields, specifically the keyword (keyword_sim and keyword_tesim in the Solr index) and license fields (license_tesim). Likewise, the ActiveFedora::Base.find and associated to_solr methods drop the data in these fields. (I am imagining perhaps that's why the reindexing fails.)
In the Fedora UI, I can see that our legacy data has the keywords stored in a dc:relation field, which is also the case in our previous Fedora instance. But for newly created works (in our 3.6 app), the keywords are assigned one of the ns fields, e.g., ns018:keywords.
I don't know enough about Fedora to determine whether this change has to do with the version of the Fedora app itself, or some configuration change we failed to make, and/or a change in the Hyrax codebase. Any suggestions or leads would be much appreciated!

@scherztc
Copy link
Contributor Author

Important Migration Service : samvera/hyrax#3748

@scherztc
Copy link
Contributor Author

I propose we got to version 3.6 next.

@scherztc
Copy link
Contributor Author

scherztc commented Mar 7, 2024

@scherztc scherztc self-assigned this Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant