v6.9.0

6.9.0 - 2021-10-27 - Spooky HTTPS Support!

Features

• Chrome 94 forces you to be on https URL to access HTTPS secured search engines. Quepid now checks to see whether it is running on the same protocol, HTTPS or HTTP that the search engine is running on, and if not, prompts you to reload the app on the same protocol as the search engine. This required updating the messenging in the Case Wizard and the Tune Relevance screens. We also simplified the logic in the home_controller.rb around bootstrapping a Case and Try. Thanks to @tboeghk for pairing with @epugh on how to solve this problem. #431 by @epugh fixes #426 by @DmitryKey and #432 by @bbirrell.

Improvements

• Remove remnants of "SecureApp" angular1 app that was refactored a while ago into regular Rails app for login screens. #434 by @epugh fixes #433.

• Logic to enable Google Analytics tracking was crufty and caused classloader issues in development mode. #419 by @epugh fixes #418.

v6.8.0

6.8.0 - 2021-09-28

Features

• Understand the evolution of your various Tries by visualizing the history as a tree data structure. Understand where you went back to an earlier Try and branched off in new directions. #412 by @epugh fixes #412 by @DmitryKey.

• Deploying Quepid in a cloud native way requires having a healthcheck end point to confirm Quepid is available and happy. #404 by @epugh fixes #404 by @mkr. Thanks to @xaviersanchez for the inspiration to do this.

• Now sort queries by most recently modified. #334 by @DmitryKey and @epugh fixes #307.

• Excited to share the improvements you made to your Case? You can now drop your link to the Case into Slack or other messaging tools, and it will unfurl, i.e show the Case Name and the most recent Try number. You will still need to log into Quepid and have access to that Case. #417 by @epugh fixes #416.

Improvements

• The messaging around how many documents are being scored, i.e @10 or @40 is now driven by the variable k defined in various Scorers. Commit 73a378f by @epugh fixes #413 by @DmitryKey.

• We audited our Docker builds, and _shrank the images from 2.42GB to 1.44GB! Bumping Node version to 15, be smarter about what folders we copy into our production image, and some general fixups. #409 by @dworley and @epugh.

• The logic to check if Google Analytics is enabled via ENV variable is different then the normal Quepid ENV handling. #419 by @epugh cleaned this up, and solves a class loading issue in the DEV mode Quepid, increasing developer happiness!

• Trying to find a doc that SHOULD match and be rated, but can't find it? Using a global scorer like NDCG and curious what all the ratings are? We have reworked the Explain Missing Documents UI into a Find and Rate Missing Documents that lets you see all your ratings associated with a query, and then search and find other documents that are missing. Preview video here https://share.descript.com/view/IkxWkjSzzKF. #407 by @epugh fixes #406 by @mkr.

v6.7.0

6.7.0 - 2021-08-26

Features

• Elasticsearch fields computed using script query now work! Back in February @CGamesPlay contributed a PR (o19s/splainer-search#90) to splainer-search to support this, and now it automagically works in Quepid! Thanks @DmitryKey for opening #327 and supporting this feature.

• Elasticsearch templates can now be used in Quepid! #400 by @epugh exposes the underlying splainer-search functionality in Quepid. Thanks @danielibars for opening #274 and supporting this feature.

• Curious what parameters are being used by Solr to construct the query? We're now adding a echoParams=all to queries and surfacing them in the Explain Query modal at the query level in Quepid. Currently a Solr only feature. #397 by @epugh with inspiration from @mkr.

Improvements

• Continue cleanup of JavaScript, eliminated last remnants of "unit test" style scorers, and renamed customScorer to just scorer in front end app.

v6.6.1

6.6.1 - 2021-08-11

• In testing the Keycloak oAuth integration via the Chorus project, identified that the name of the Client that is passed to Keycloak was tied to the KEYCLOAK_REALM env setting. Changed this to be hardcoded to quepid so it can be different then the Realm name (i.e the Realm is Chorus in the Chorus project, and the Client is quepid). Commmit de9e0e6 by @epugh.

v6.6.0

6.6.0 - 2021-08-09

Features

• OpenID Support! Historically you had to create your own account on Quepid, but that is another barrier to entry, and something else to keep track of. Inspired by the issue Add OAuth Providers by @gregoryduckworth #188, #280 and #389 by @epugh implements the first two providers, Google and Keycloak.

• Explain Query Parsing! We often want to know what the search engine is doing to our query. Now you can click the "Explain Query" popup and see what is happening to your query and the various filter queries. This works with both Solr and Elasticsearch. https://twitter.com/dep4b/status/1420480501710827520. #391 by @epugh.

• Frequently type deftype instead of defType in Solr? I found an old, but broken feature that provided a popup warning on common Solr query syntax errors, which has now been restored. #394 by @epugh fixes #390.

Improvements

• Quepid is running on Rails 6! Rails 6 was released ~26 months ago, and represents the future of Rails. I'm excited that this push initiated by @DmitryKey is going to bring us some great new features like: better developer experience with Webpack for JavaScript, ActionText to handle better text formatting of notes and messages about Cases and Queries, ActionCable which will let us notify all the users of the same case that data has changed when it changes. #381 by @DmitryKey with assist from @epugh.

• Make our ActiveRecord modeling for ownership the same. Teams have an owner, Scorers have an owner, but Cases have a user. Now we have case.owner relationship. #359 by @epugh.

• The nav bar link for Scorers is labeled "Custom Scorers", and takes you to an page called /advanced. Both of the names are rather offputting. Creating Scorers is a normal common thing to do in Quepid, so lets label it Scorers. #392 by @epugh fixes #351.

• We had, as someone put it "dinosaur" age CSS tags for mozilla and webkit browsers that triggered lots of browser warnings in the console. #380 by @epugh cleaned up many of them. It has also prompted some thinking about migrating to Bootstrap 5 for the non core pages. If anyone has some CSS skills, please contact @epugh, to help refine the header menu in Bootstrap 5 CSS.

v6.5.5

6.5.5 - 2021-06-30

Features

• You can now tag a field with translate:, as in translate:content and you will get an icon to pop the text open in a Google Translate in a new browser window. #386 by @epugh.

Improvements

• You can now export fields that have the formatting modifiers thumb and image using the detail format. Also improved the handling of the General and Detail export from the Case Listing page. #383 by @epugh fixes #382. Thanks @DmitryKey for the improvement assist and spotting the Case Listing export issue.

• Admin user can now reset a users password with a new password. #385 by @epugh to fix issue identified by @michaelcizmar. Thanks Michael!

• Trying to communciate about HTTPS better when you set up a case. #384 by @epugh inspired by #279 by @arafalov.

6.5.4

6.5.4 - 2021-06-16

Features

• You can now Clone an existing Scorer!. Super useful when you want to start with one of the communal scorers that only go to 10 deep, like P@10, and you want it to be P@40. Introduced as part of #379 by @epugh.

Improvements

• Enable TLS for Redis 6 on Sidekiq on Heroku. #370 by @michaelcizmar fixes #271 by @michaelcizmar. Thanks Michael for your first PR to Quepid!

• During the Case Wizard setup, allow space delimited list of fields, like title overview to be pasted in, just like comma delimited lists. Thanks @peterdm for the assist on the Regex! #378 by @epugh.

• Revamped the layout of the Scorer creation and editing screens to be visually cleaner. Retired the old Fibonnaci scale, and renamed Default to Detail, as well as Short to Graded scales. Introduced Binary as a new, default scale. @DmitryKey and @epugh paired on this during Quepid Qommunity Qoding hour, resulting in #379.

• Shrink production Docker image of Quepid from 2.19GB to 2.17GB by not installing development and test Gems. Commit 426d267 by @epugh.

Bugs

• Preserve the chosen scorer when cloning a case, we were defaulting to the users default scorer. #372 by @epugh fixes #273. Thanks @binarymax and @nathancday for spotting this!

• Ensure that CSV export always has all the columns expected. Queries that aren't fully rated and have blank values didn't put out complete set of , separators. #371 by @epugh fixes #364 by @sstults. Spotted while working with Quaerite.

• If you don't have a Terms & Conditions url, then your users don't have an agreed_time, so the activity pulse chart in the admin errors out. #373 by @epugh sorts this out.

• In the dawn of Quepid, we had agreed_time but not a boolean agreed. A user let me know he couldn't update his email address (from an account in 2015!) because he didn't have agreed=true set. #374 by @epugh cleans up some old user data.

• Fixed the labeling behavior for a Scorer. @DmitryKey and @epugh paired on this during Quepid Qommunity Qoding hour, resulting in #379, fixing #376.

6.5.3

6.5.3 - 2021-06-01

Bugs

• In 6.5.2 we introduced the image:image_path to show larger images, however there is odd wrapping if you don't have many fields listed for a doc. #365 by @epugh fixes this.

• If you didn't have email set up, then sending invites wouldn't work. #369 by @epugh adds better handling for when email hasn't been set up for Quepid.

6.5.2

6.5.2 - 2021-05-27

Improvements

• We have a new Favicon, but didn't use it everywhere, so #363 by @epugh displays the new favicon everywhere.

Features

• Rating documents where the image carries most of the information? The existing thumbnail:image_path limits you to a 75 pixel wide image. We now have image:image_path which displays a 200 pixel wide image. This is an alternative to the media:image_path approach, as this shows up next to your fields versus inline with your fields. #362 by @epugh fixes #360.

6.5.1

6.5.1 - 2021-05-25

Bugs

• Now that we've had the team invitations feature out for a while, we've found places where we make assumptions that aren't correct. This fixes the Admin panel's user page, and makes on the Teams page the messaging around pending invites. #339 by @epugh.

• We discovered that nDCG@10 score for products with a hitCount below 10 (K) was always 0. #336 by @rudibatt fixes this. Thanks @rudibatt for this contribution!

• Passing in quote delimited parameters to bin/docker r wasn't preserving or quotes or escaping the spaces, causing the thor user:create [email protected] "Eric Pugh" "mysuperstrongpassword" example to fail. #340 by @epugh fixes #338.

• Thanks to Liz Novak at VIN for discovering that a non lowercase email address like [email protected] wouldn't be considered a valid email address, so you couldn't send a invite to join Quepid. #342 fixed by #346 by @epugh with assist from @eribeiro.

Improvements

• Uglifier for JavaScript appears to not work with ES6, and so using Terser instead. #329 by @epugh fixes this.

• Add to the Team page the ability to copy the team invitation url to send via other means then Quepid's own email setup. This is helpful if you don't have email set up, or if you want to share invites with team members via chat tools like Slack. Also fixed the user flow of registering after someone has sent out an invite for someone. #337 by @epugh fixes #335 and #326.

• We've added linting for our Dockerfiles via Deepsource.io. #343 by @epugh fixes #341.

• Our Docker images are getting bloated by including log files from dev and test, leading to almost a 3 GB image. Adding a .dockerignore has got us back to around 2.1 GB image. #358 by @epugh fixes #353.

• Remove the remnants of the query test (unit test style custom scorers) and the default scorer table that are still in the source code. #357 by @epugh fixes #349.

• Sometimes you want to create a Case even when you can't validate the connection. Introduce a option to bypass the validation. #356 by @epugh.

• When we export basic rating data there is an extra LF character at the end of the CSV file. This was causing issues when importing ratings into the Quaerite project (tballison/quaerite#14). #355 by @epugh with assist from @sstults fixes #354 by @sstults.

• Quepid 6.5.0 started failing on Kubernetes clusters due to the need to be able to write to the filesystem. Bootsnap dependency upgrade avoids this. #344 by @epugh. Thanks to @LiuCao0614 and @tonomonic for the assist on this.

• Revamp of how all the permissions for doing actions related to Teams, Scorers, and Cases to use the Permissions data we aleady have for a user. Lots of cleanups on those functions. Finally dealt with the left over need to have a Case per User, or the UI blew up. Now you get a nice message, and the UI doesn't blow up. #347 by @epugh fixes #352, #331, #278.