Skip to content

Releases: samvera/bulkrax

v9.0.0

20 Dec 18:29
Compare
Choose a tag to compare

What's Changed

Breaking Changes πŸ› 

  • speed up entries display by no longer looking at all the status objects by @orangewolf in #988

Requires running bin/rails bulkrax:update_status_messages after deployment for error messages on existing entries to display.

Bug Fixes 🐞

Other Changes

Full Changelog: v8.3.0...v9.0.0

v8.2.2

17 Dec 14:51
Compare
Choose a tag to compare

What's Changed

Bug Fixes 🐞

v8.3.0

02 Dec 23:57
ca08ee4
Compare
Choose a tag to compare

What's Changed

Exciting New Features πŸŽ‰

  • [i858] - Enables chunked uploads for improved file upload reliability by @ShanaLMoore in #982

Bug Fixes 🐞

Full Changelog: v8.2.1...v8.3.0

v8.2.1

02 Dec 22:17
Compare
Choose a tag to compare

What's Changed

Bug Fixes 🐞

  • Avoid false positive from .try(:internal_resource) by @bkiahstroud in #980
  • bump versions to make bundling on arm processors work again by @orangewolf in #983

Full Changelog: v8.2.0...v8.2.1

v8.2.0

19 Sep 18:52
Compare
Choose a tag to compare

What's Changed

Exciting New Features πŸŽ‰

Bug Fixes 🐞

New Contributors

Full Changelog: v8.1.0...v8.2.0

v8.1.0

03 Jun 22:22
Compare
Choose a tag to compare

What's Changed

Exciting New Features πŸŽ‰

Bug Fixes 🐞

Full Changelog: v8.0.0...v8.1.0

v8.0.0

02 Apr 16:25
Compare
Choose a tag to compare

What's Changed

With Bulkrax 8, we now support Hyrax 4 and 5 while still allowing Hyrax 2 and 3 to use Bulkrax. Importantly, this release enables Valkyrie support.

The main addition is creating a new "object factory" that supports Valkyrie. This involved extracting Fedora and Solr operations into the configurable object factory.

For those using Hyrax 2, 3, or 4 (with ActiveFedora), you'll want to configure Bulkrax.object_factory = Bulkrax::ObjectFactory; this is the default assumption for version 8.0 or prior.

For Hyrax 5, you can continue to use Bulkrax::ObjectFactory or configure Bulkrax.object_factory = Bulkrax::ValkyrieObjectFactory. These configurations are done the downstream application configuration/initialization.

Note: The development team thinks that there may not be any breaking changes between v7 and v8; however there were significant underlying changes and there might be breaks. Our design goal was to continue in such a way that older Hyrax's could upgrade Bulkrax; this means less backporting of patches (which creates lots of overhead).

Breaking Changes πŸ› 

Exciting New Features πŸŽ‰

Bug Fixes 🐞

New Contributors

Full Changelog: v7.0.0...v8.0.0

v7.0.0

02 Mar 01:43
Compare
Choose a tag to compare

What's Changed

This release brings pagination the importers and exports pages along with search, sort and filtering. We have also consolidated the import /export show page entry list. It is now one unified list (instead of 3 or 4 tabs) and is also has search, sort, and filters.

This release also implements a new core method for dealing with entries that have failed. We are introducing remove and redo. This completely deletes the Hyrax concern (Work, Collection, FileSet) and then recreates it fresh. This can help with cases where fcrepo got only a partial record. You can do this on an entry by entry bases, for the whole importer or by adding a remove_and_redo column and setting it to true in your import data.

Lastly be sure to see the various quality of life enhancements in this release. There is individual entry re-run from the UI, support for just running the failed or pending entries on an importer and more.

Breaking Changes πŸ› 

  • Denormalize Status Message to that Entry Look Up Can Be Fast by @orangewolf in #913
    When deploying this change all objects will have the status_message "Pending" until the bulkrax:update_status_messages rake task is run. Call rails bulkrax:update_status_messages to do so. It touches every entry, so it could take a little while β˜•
  • For every importer / record combo there should be exactly one entry by @orangewolf in #921
    There were previously cases where a new importer would either steal an existing importers entry or it would update the old entry and not show it when viewing that importer. This fixes that by scoping entry identifiers to the importer or exporter that created them. If you do something that relies on entries hopping between importers when the same identifier is run multiple times, please examine that code.

NOTE: When upgrading to this version, rails assets:precompile will need to be ran for assets to properly render in the UI

Exciting New Features πŸŽ‰

  • 🎁 Add persistence layer to ObjectFactory by @jeremyf in #895 and #921
  • Retry and delete by @orangewolf in #894
  • Update Importer Index and Show Entries With Search, Filtering, Sort and More by @orangewolf in #914
  • Mark records as skipped if we do not see them during an import run by @orangewolf in #922
  • Redo records with the remove_and_rerun property in the data, move individual remove and rerun to a background job by @orangewolf in #923
  • ♻️ Favor member_ids_ssim over file_set_ids_ssim by @jeremyf in #929

Bug Fixes 🐞

  • πŸ“š Adding documentation for configuration by @jeremyf in #896
  • ♻️ Extract Bulkrax::FactoryClassFinder by @jeremyf in #900
  • 🎁 Config option for coercing a factory class name by @jeremyf in #901
  • importer failure helpers by @orangewolf in #859
  • Strip out all special characters from csv headers by @orangewolf in #918
  • Fix exporters show page - 2 by @orangewolf in #926
  • ♻️ Favor configuration over hard-coding by @jeremyf in #927
  • πŸ› Fix exporter page for Bootstrap 3 applications by @kirkkwang in #928

Full Changelog: v6.0.1...v7.0.0

v5.5.1

14 Feb 16:06
Compare
Choose a tag to compare

Add ability to configure queue name: 5e6809c

Full Changelog: v5.5.0...v5.5.1

v5.4.2

14 Feb 16:05
Compare
Choose a tag to compare

Add ability to configure queue name: 5e6809c

Full Changelog: v5.4.1...v5.4.2