Skip to content

Releases: projectblacklight/spotlight

v3.6.0.beta3

22 Jan 19:05
@jcoyne jcoyne
v3.6.0.beta3
5cf8be8
Compare
Choose a tag to compare
v3.6.0.beta3 Pre-release
Pre-release

What's Changed

  • Stop requiring bootstrap components by @jcoyne in #2921
  • Enable new rubocop by @jcoyne in #2924
  • Update analytics to use GA4 by @thatbudakguy in #2923
  • Update search session tracking for Blacklight 8 by @jcoyne in #2927
  • Add documentation about why redcarpet is required by @jcoyne in #2935
  • Make sprockets optional to enable propshaft by @jcoyne in #2931
  • The / operator is deprecated in sass by @jcoyne in #2943
  • Remove unused variables by @jcoyne in #2942
  • Remove unnecessary include of bootstrap/variables by @jcoyne in #2941
  • Don't redeclare variables that are already defined by Bootstrap by @jcoyne in #2940
  • Add relative path to tiny-slider by @jcoyne in #2939
  • Use Blacklight::Configuration.default_configuration for Blacklight 8 by @jcoyne in #2944
  • Rebuild the javascript after Analytics was removed by @jcoyne in #2937
  • Use relative paths to stylesheets by @jcoyne in #2936

Full Changelog: v3.6.0.beta1...v3.6.0.beta3

Contributors

jcoyne and thatbudakguy
Assets 2
Loading

3.6.0.beta1

23 Feb 05:50
@jcoyne jcoyne
v3.6.0.beta1
627d573
Compare
Choose a tag to compare
3.6.0.beta1 Pre-release
Pre-release

Upgrade steps

Add the following line to app/assets/config/manifest.js

//= link spotlight/manifest.js

Note that you must specify BOOTSTRAP_VERSION="~> 4.0" if you run the Blacklight installer, because Spotlight does not yet support Bootstrap 5.

The big changes

  • Blacklight 8 support
  • We no longer require sprockets to compile the javascript, you can use alternative bundlers or just use the javascript published to NPM as spotlight-frontend

What's Changed in detail

New Contributors

Full Changelog: v3.4.4...v3.6.0.beta1

Contributors

bess, mcritchlow, and 4 other contributors
Assets 2
Loading

v3.4.4

12 Jul 14:57
@cbeer cbeer
v3.4.4
33dd785
Compare
Choose a tag to compare
v3.4.4

What's Changed

Full Changelog: v3.4.3...v3.4.4

Contributors

cbeer
Assets 2
Loading

v3.4.1

28 Jun 14:40
@cbeer cbeer
v3.4.1
1ccab79
Compare
Choose a tag to compare
v3.4.1

What's Changed

  • Work around a cancancan regression with polymorphic relations by @cbeer in #2829

Full Changelog: v3.4.0...v3.4.1

Contributors

cbeer
Assets 2
Loading

v3.4.0

28 Jun 14:33
@cbeer cbeer
v3.4.0
b01db32
Compare
Choose a tag to compare
v3.4.0

What's Changed

New Contributors

Full Changelog: v3.3.0...v3.4.0

Contributors

mcritchlow, ggeisler, and 3 other contributors
Assets 2
Loading

v3.3.0

01 Mar 00:37
@cbeer cbeer
v3.3.0
572a768
Compare
Choose a tag to compare
v3.3.0

What's Changed

  • Update CI versions by @cbeer in #2791
  • Add a contributing.md document for Spotlight by @mejackreed in #2291
  • Skip a very flaky test in CI by @cbeer in #2795
  • Import data using #with_indifferent_access to avoid confusing strings and symbols by @cbeer in #2794
  • Make rake tasks read from env for non-interactive usage by @thatbudakguy in #2797
  • Use the actual configured facet limit to determine when to show the 'too many values' version of the count by @cbeer in #2792
  • Truncate titles in breadcrumbs and limit them to 1 line by @marlo-longley in #2796
  • Update confirmation email text by @cbeer in #2800
  • Omit HTML id attributes for the 'current tab tracking' hidden field by @cbeer in #2801
  • Update requirements listed in the README by @cbeer in #2798
  • Tweak log messages and comments by @cbeer in #2799
  • Remove debug logging from test by @cbeer in #2802
  • Address upstream deprecation warnings by @cbeer in #2803
  • Wrap initializers that depend on Rails autoloading with to_prepare by @cbeer in #2806
  • Allow paper_trail v12 by @cbeer in #2807
  • Relax dependency pinning for acts-as-taggable-on by @cbeer in #2808

New Contributors

Full Changelog: v3.2.0...v3.3.0

Contributors

cbeer, marlo-longley, and 2 other contributors
Assets 2
Loading

v3.2.0

08 Oct 17:20
@cbeer cbeer
v3.2.0
cac38ef
Compare
Choose a tag to compare
v3.2.0

What's Changed

New Contributors

Full Changelog: v3.1.0...v3.2.0

Contributors

corylown, aaron-collier, and elrayle
Assets 2
Loading

Spotlight 3.1.0

11 Jun 16:48
@mjgiarlo mjgiarlo
v3.1.0
6754bfb
This commit was signed with the committer’s verified signature.
mjgiarlo Michael J. Giarlo
GPG key ID: DF66BC3FCDD3FC61
Learn about vigilant mode.
Compare
Choose a tag to compare
Spotlight 3.1.0

Features

  • Move analytics rendering from footer into head (#2761)

Improvements

  • Symbolize our strings used in paths (#2754)
  • Guard against the bulk updates visibility column not appearing in the spreadsheet (#2758)
  • Cache the search#count value (#2759)
  • A11y improvements (#2764)

Bug Fixes

  • Allow as_json to accept arguments (#2756)
  • Update install generator to use the destination_root to support generating a new app with the template (#2763)
  • ReindexExhibitJob#perform: fix when object count is 0 (#2760)
  • Explicitly re-enable p tags for text all of our custom blocks (#2765)

Thanks

Assets 2
Loading

Spotlight 3.0.0

07 May 18:09
@cbeer cbeer
v3.0.0
a41542c
Compare
Choose a tag to compare
Spotlight 3.0.0

Features

  • Blacklight 7 support
  • Bootstrap 4
  • Rails 6.1 support
  • New Arabic, Brazilian Portuguese, and Spanish translations, and improved RTL display
  • Accessibility improvements
  • Support bulk updates and bulk actions for adding/removing tags and public/private visibility to many exhibit items at once
  • New exhibit item indexing ETL framework, and other indexing improvements to provide better performance and visibility into the indexing background jobs for the exhibit builders
  • New browse groups for organizing long lists of browse categories

Improvements

  • Include the site title in feedback emails (#2282)
  • Use the :long date format consistently (to include the year) (#2355)
  • Allow the engine configuration to limit which themes are available for a given exhibit (#2372)
  • Updated Exhibit cards on home page (#2481)
  • Improve rendering of browse categories, saved searches, and pages widgets (#2571)
  • Removes the require.js / almond.js conversion of ES6 JavaScript from amd to umd modules #2599
  • Improved OpenSeadragon ("ZPR") viewer styling
  • Add a query facet for public items
  • More granular exhibit export configuration for configuring what parts of an exhibit should be included in an export

Bug Fixes

  • Fix an issue with the analytics component and multiple analytics profiles (#2312)
  • Address a race condition when updating sidecar data (#2316 + #2320)
  • Have feedback emails come addressed from the service, not the feedback submitter (#2301)
  • Fix a navigation issue using the search result widget (#2347)
  • Fix an issue with empty custom field data being indexed as an empty string (instead of removing the data from Solr) (#2356)
  • Follow HTTP redirects when retrieving IIIF resources
  • Reserve page + exhibit slugs that conflict with application routing
  • Image uploads should be associated with an exhibit

Upgrading

In this major release, Spotlight 3 has updated its upstream dependencies to support the latest releases of Rails, Blacklight and Bootstrap. As such, it's important to review those upgrade guides and address deprecation warnings from your application either before or as part of upgrading to Spotlight 3.

  1. Review the Blacklight 7 upgrade guide
  2. Review the Bootstrap 3 to 4 migration guide for any local customizations
  3. Convert any local custom JavaScript from using require.js syntax to the umd version. See #2599

Additionally, there are some changes you need to make to your application to support new features or configurations in Spotlight 3:

  1. Add the SirTrevor initializer to your application
  2. Update local indexing code to use the new ETL framework (see below)
  3. Update your SearchBuilder to replace Spotlight::AccessControlsEnforcementSearchBuilder with Spotlight::SearchBuilder
  4. Install + run the new spotlight migrations: rake spotlight:install:migrations && rake db:migrate

ETL

Spotlight::SolrDocumentBuilder has been removed in Spotlight 3, and your Resource model is now responsible for all steps in the indexing process. Spotlight now provides an indexing pipeline framework to make it relatively easy to build your indexing rules into the resource.

Each resource class has indexing_pipeline method that defines the ETL steps for creating solr documents from your resource instance. In your local resource class, you'll want to add additional configuration to the pipeline to perform appropriate extract and load steps.

The pipeline source configuration is an array of extraction steps. These steps can return/yield one or more source objects that will be transformed later in the pipeline. In general, these objects should be 1:1 to the documents. By default, Spotlight assumes the resource object is the object to index, but e.g. if you had a resource instance that represented a collection containing 5 constituent object, the source would yield an object representing the collection and 5 additional objects for each part of the collection.

The pipeline transform configuration take the sources and turns it into a solr document-style hash. By default, Spotlight provides some steps that augment a document with fields that enable spotlight-specific features, but you'll need to add a transform step to appropriately transform your source object to any number of application-specific metadata fields.

Here's an example of overriding the indexing pipeline for a contrived resource class.

class MyResourceClass < Spotlight::Resource
  def self.indexing_pipeline
    @indexing_pipeline ||= super.dup.tap do |pipeline|
      # Override the default indexing pipeline to add our application-specific logic; in this case, the `#to_solr` method will be
      # called on the source object (which.. because we don't override the `pipeline.sources` at all.. is just the resource instance itself) 
      pipeline.transforms = [Spotlight::Etl::Transforms::SourceMethodTransform(:to_solr)] + pipeline.transforms
    end
  end

  def to_solr
    { id: id, title_field: xml_document.xpath('//title'), ...  }
  end
end

Other examples of this new pattern include:

Other backwards compatibility notes

  • Spotlight 2 exhibit exports may not import cleanly into Spotlight 3 applications

Thanks

Assets 2
Loading

v2.13.0

18 Dec 23:36
@camillevilla camillevilla
v2.13.0
d95c91c
Compare
Choose a tag to compare
v2.13.0

v2.12.1...v2.13.0

Assets 2
Loading