Releases: samvera/hyku
v3.0.0.pre2
Pre-release 2 - updated to include 2.9.1 Hyrax release samvera/hyrax#4660 and samvera/hyrax#4656 specifically.
This is our first release in over a year. We are increasing the major version do to the user elevation being a breaking change for Hyku consumers who have local (non-sso) based user logins. We don't anticipate this being a massive effort to migrate users, but want to signal clearly to folks that it is something that needs to be done. There are lots of notable features below and our hope is that the next few releases will focus on being smaller, more incremental feature releases and bug fixes.
Features
Theming Improvements
- Customizable CSS in interface
- More individual colors
- Font selection tool
- Ability to set the default images and logos on a per tenant basis from within the UI
Bulkrax Import and Export
- Optional dependency behind feature flipper
- Connected to Browse Everything
- Status dashboard and individual tenant user self service
Contact page customizable email per tenant
Upgrade to Hyrax 2.9.1, Rails 5.2, Ruby 2.7, removed now redundant code
User management improvements, including elevating the users site wide
- User management available as superuser
- Users do not need to register for each tenant enabling Single Sign On functionality
- Roles remain per tenant
- Stepping stone to a more comprehensive and solid permissions structure site wide
- This is a breaking change for anyone with users in individual tenants as those user accounts will need to be migrated out to the 'public' users table before an upgrade to Hyku 3.0. No migration is provided at this time due to no one having a case for it. If you do need help with a migration path for users, please contact us.
Background jobs to automatic embargo release
Local docker development speed improvements using volume caches
Helm chart kubernetes deployment for Hyku
Collection thumbnail path fixes
v3.0.0.pre1
This is our first release in over a year. We are increasing the major version do to the user elevation being a breaking change for Hyku consumers who have local (non-sso) based user logins. We don't anticipate this being a massive effort to migrate users, but want to signal clearly to folks that it is something that needs to be done. There are lots of notable features below and our hope is that the next few releases will focus on being smaller, more incremental feature releases and bug fixes.
Features
Theming Improvements
- Customizable CSS in interface
- More individual colors
- Font selection tool
- Ability to set the default images and logos on a per tenant basis from within the UI
Bulkrax Import and Export
- Optional dependency behind feature flipper
- Connected to Browse Everything
- Status dashboard and individual tenant user self service
Contact page customizable email per tenant
Upgrade to Hyrax 2.9, Rails 5.2, Ruby 2.7, removed now redundant code
User management improvements, including elevating the users site wide
- User management available as superuser
- Users do not need to register for each tenant enabling Single Sign On functionality
- Roles remain per tenant
- Stepping stone to a more comprehensive and solid permissions structure site wide
- This is a breaking change for anyone with users in individual tenants as those user accounts will need to be migrated out to the 'public' users table before an upgrade to Hyku 3.0. No migration is provided at this time due to no one having a case for it. If you do need help with a migration path for users, please contact us.
Background jobs to automatic embargo release
Local docker development speed improvements using volume caches
Helm chart kubernetes deployment for Hyku
Collection thumbnail path fixes
v.2.1.0
Version Number Fix and Updated Translations
This release fixes the version number in the footer and updates the translations from Hyrax.
v2.0.0 - Invasion of the Interest Group
This release includes cleanup and new features post hydra-in-a-box grant work. This updates the base Hyrax to 2.3
See https://github.com/samvera/hyrax/releases for information on the underlying Hyrax updates between 2.0 and 2.3
Default Collection Types
An existing app will have to run a generator to add the pre-defined collection types: user_collection and admin_set
rails hyrax:default_collection_types:create
NOTE: db:migrate must be run before running the generator for default collection types.
Collection Migration
Fedora/Solr Collection Model
CE adds one property to Collections model... collection_type_gid, which identifies the type (RDF::Vocab::SCHEMA.additionalType) of each collection. The gid is generated based on the collection type id (e.g. gid://internal/hyrax-collectiontype/:id).
Migration Process
The migration process performs two updates for every collection...
store the User Collection gid as the collection type for all legacy collections
add a Permission Template and set Accesses based on sharing information in the legacy collection
NOTE: Solr and Fedora services need to be running when this script is called.
rails hyrax:migrate:add_collection_type_and_permissions_to_collections
v1.0.0
This version is all the work prior to upgrading Hyrax to more recent versions. The next release will include necessary data updates and we're working to signal that clearly.