6.11.0

6.11.0 - 2022-04-23

Features

• Documenting the explicit Information Need of the user is a core part of running human judgements, and historically people used the Notes field for this. Now we have a Information Need attribute for every Query, and you can import/export that data via CSV, as well as edit it in the UI. Mouse over the query to see exactly what the user is trying to do! #480 by @epugh.

• The details of a specific query exposed by the Explain Query modal is in a Human readable format, but isn't in a JSON compliant format. Now we sort the keys alphabetically, which helps the user dig through the details, and have a Copy as JSON button so you can use other tools to look at the JSON information. #497 by
  @epugh fixes #492.

• Delete All Queries for a Case was requested by @negyesi in #475. At the case level added a Delete button that brings up a modal that lets you delete the case, archive the case, or delete all the queries. #486 by @epugh.

• Frustrated that your custom API that looks like Solr to Quepid has to deal with JSONP callbacks? Now you don't, as we have introduced the ability to swap from the default JSONP to GET api methods when you define your Solr end point. This is going to simplify the work that folks have to do. #495 by @epugh. For more information refer to the docs at https://github.com/o19s/quepid/blob/master/docs/endpoints_solr.md#solr-endpoints-structure.

• Do you have a relative image url in your search engine that you want to show via thumb: or image:? You can now provide some JSON in the field specification to provide that data: id,title:title,{"name": "image_url", "type":"image", "prefix": "https://www.example.org/images"}, description. This feature is experimental as we learn more about how to have richer field specifications, and may change! #487 by @epugh.

Improvements

• The link to view a single Solr document specifies XML, which I realize is a very OK boomer approach these days! o19s/splainer-search#107 by @begomeister fixes #494 by swapping to JSON format instead.

• github.com/teleborder/FileSaver.js repo disappeared, so migrate to an actual published node module file-saver instead. #498 by @epugh.

• We had a mish-mash of query and query_text as headers in our CSV files, so we've standardized on query to make export/import simpler. #489 by @epugh.

• We discovered that Redis was ONLY used in Quepid to support sending events to Google Analytics! If your QUEPID_GA isn't specified, then Redis is no longer required. Thanks to @rbednarzCBI for updating the production docker settings to remove Redis in #488.

Bugs

• The various CSV upload and export features didn't really handle , in the text properly, so we gave that a good going over. #482 by @atarora fixed by #483 and #485 by @epugh

• Tracking the history of your tries, we had a limit in the database that prevented you from having lots of tries. #478 by @KennyLindahl and #470 by @korlowski. Fixed by #479 by @epugh. Thanks @KennyLindahl for the additional testing work you did to help me fix this!

• Fixed the ability to peek at the next page of result when you have less then 10 results left. Thanks @anegyesi for submitting #473 and fixed in #496.

• Noticed the case level graph isn't useful? PR #491 by @worleydl, Save scores less often, fixes stretching of graph, fixes this.

• @thePanz opened a ticket a year ago (#330) about ratings getting progressively slower in the UI, and a huge amount of updates to the backend. Thanks to @worleydl and #490 this should be fixed.