Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Collection Extensions: Release Migration Notes #1596
The major features of this release include:
Migration Procedures from Hyrax 2.0.x to 2.1.0
The following steps describe the process for migrating to Hyrax 2.1.0 which includes the Collection Extensions work. The steps should be run in the order presented.
Edit Gemfile or gemspec to update the version of hyrax.
Database: Application DB changes are all covered by db:migrate
Run migrations to get database changes...
You will also need to run migrate for tests to update your test database.
Default Collection Types
An existing app will have to run a generator to add the pre-defined collection types:
Fedora/Solr Collection Model
CE adds one property to Collections model...
The migration process performs two updates for every collection...
NOTE: Solr and Fedora services need to be running when this script is called.
Instructions for setting up the UniversalViewer for images in works
UniversalViewer setup is in the Management Guide in section Image Server
Tinymce configuration changes
Some modifications were made to the tinymce editor configuration. If you are creating a new app, these configurations will be made for you as part of the hyrax installation process. If you are migrating an app, you will want to review your app's config/tinymce.yml file and compare it to the new one in Hyrax at hyrax/lib/generators/hyrax/templates/config/tinymce.yml.
Avoid flash messages being swallowed for XHR requests
Flash messages are being discarded by Blacklight for XHR requests. To avoid this, add the following line to your
Avoid Performance Issues with solr-suggest
Recommended for all Hyrax apps.
It is strongly suggested that you turn off solr-suggest. Details on why and how to do this are in Fix performance issue caused by solr-suggest.
Fellow Hyrax developers are gathering their experiences with Troubleshooting Migration from Hyrax 2.0.x to 2.1.0. You may want to visit this guide and contribute your experiences.
This was referenced
Aug 30, 2017
$ rake --trace hyrax:default_collection_types:create ** Invoke hyrax:default_collection_types:create (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute hyrax:default_collection_types:create rake aborted! ActiveRecord::StatementInvalid: PG::UndefinedTable: ERROR: relation "hyrax_collection_types" does not exist LINE 8: WHERE a.attrelid = '"hyrax_collection_types"'... ^ : SELECT a.attname, format_type(a.atttypid, a.atttypmod), pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod, c.collname, col_description(a.attrelid, a.attnum) AS comment FROM pg_attribute a LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum LEFT JOIN pg_type t ON a.atttypid = t.oid LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation WHERE a.attrelid = '"hyrax_collection_types"'::regclass AND a.attnum > 0 AND NOT a.attisdropped ORDER BY a.attnum
db migration must be run before generator.
@elrayle It appears that Collections and AdminSets must be reindexed, else the following code:
causes an error because