Skip to content

Releases: trln/trln_argon

TD-1275 Add log/trace information to the UI

05 May 19:39
d2db3ff
Compare
Choose a tag to compare
  • This feature is for Demo Argon or local development mode
  • To enable the feature set an ENV variable ALLOW_TRACEBACKS = 'true'
  • When set, in the UI you can see the log/traceback on a separate page /logs or /logs?lines=100 (the default value for lines is 50)

Add truncation on main search page and advanced search page to address maxClauseCount issue in Solr 9

27 Apr 17:30
91be993
Compare
Choose a tag to compare
  • Default is not to truncate (so this code can run in Solr 7-powered apps to ease the upgrade path)
  • Setting ENABLE_QUERY_TRUNCATION to 'true' truncates basic & advanced search queries
  • Expensive fields (in terms of Solr clauses consumed) are truncated more aggressively
  • Fixes a bug in Advanced Search where unbalanced parentheses or quotes would yield an error

TD-1273 Add Ruby 3.1 to CI test suite

27 Mar 15:22
b95f801
Compare
Choose a tag to compare
Merge pull request #398 from trln/Add-Ruby-3.1-to-CI-test-suite

Add Ruby 3.1 to CI test suite

TD-1267 Duke only, correctly display "<" and ">" symbols when present in the <datafield tag="264">

24 Mar 19:32
ead0cd3
Compare
Choose a tag to compare

v2.2.4 - Bugfix for dd metadata (TD-1264)

22 Feb 21:10
8c5c544
Compare
Choose a tag to compare

This release fixes bug TD-1264, in which TRLN Argon began rendering unwanted and invalid/inaccessible <dd> elements in all the various places where metadata values are displayed, due to upstream changes in Blacklight and ViewComponent. See PR with screenshots.

This change leans into the <dd> elements by rendering the accompanying <dl> & <dt> to ensure the markup is valid and accessible.

Explanation

Blacklight 7.32.0, began requiring ViewComponent 2.66+ at which time it became impossible to short-circuit a metadata viewcomponent with arbitrary markup in a value slot when there is already a values slot. Note in Blacklight 8 the definition list markup can be changed when instantiating a metadata component, but it's not currently customizable in 7.x.

Upgrade Notes

You may need to revise some CSS if you have rules targeting the metadata values. E.g., if you have styles for:

.index-document-metadata ul li.index-metadata.creator_main_a { }
#show-sub-header ul li.index-metadata.creator_main_a { }

...the equivalents would be:

.index-document-metadata dl dd.creator_main_a { }
#show-sub-header dl dd.creator_main_a { }

Bug fix

30 Jan 15:38
fa31e0c
Compare
Choose a tag to compare
  • Advanced search "start over" button wasn't clearing selected facets

Bugfix to make advanced search "facet query" fields work

17 Jan 21:06
77174ab
Compare
Choose a tag to compare

This release removes some local workarounds for advanced search and related constraints display that are no longer necessary. Fixes TD-1247 & reverts TD-1252.


Upgrade Notes

For all implementers, the fix involves updating trln_argon to v2.2.2 and then modifying their local config.advanced_search[:form_solr_parameters] configuration (if present) in their local CatalogController. Especially see the changes in controller_override.rb.

In this config, ensure that:

  • facet.field includes TrlnArgon::Fields::DATE_CATALOGED_FACET.to_s
  • facet.query is not an empty string, e.g., if you have a line 'facet.query' => '' you’ll need to remove it.

Install advanced search 8.0.0.alpha2

19 Dec 16:26
3fbbd27
Compare
Choose a tag to compare

This version of advanced search fixes the issue with the number of values in the Resource Type and Language drop-down lists (TD-1217). In addition, it adjusts the layout of the elements on the advanced search page.
Screen Shot 2022-12-14 at 11 03 00 AM
Screen Shot 2022-12-14 at 11 05 15 AM

TD-1231 Remove count from link to WorldCat search results

10 Oct 18:30
4f26836
Compare
Choose a tag to compare

No longer attempt to fetch count from Worldcat for searches (to avoid potential timeout etc. issues with Worldcat service); continue to produce links to Worldcat by default on 'failing' search result pages.

Configure branches for code mappings

07 Oct 17:41
e93cd89
Compare
Choose a tag to compare

Mappings are now fetched from main by preference, falling back to master branch if the former is not available. Can also fetch mappings from any branch you like by setting ARGON_MAPPINGS_BRANCH in the environment.