This release is a minor release.
This release marks 3 additions, 5 changes and 11 fixes.
[APIs] Support for correct
mode on the record API
The record API now supports the mode correct
, following the same logic as the batch uploader.
Read more about this in our documentation.
[Misc] Autocomplete elements in submission forms and autocompleting in the record editor can now be configured to bypass restricted records.
Previously, when configuring authority collections to be available in autocomplete elements in submission forms and autocompletion on certain fields in the record editor, the collection was required to be publicly available. TIND can now configure such automatic completion to instead bypass collection restrictions, if needed.
Bypassing restrictions in this way will still preserve the regular access restrictions on the collection; it will only ensure that autocompletion during submission and the record editor is possible on restricted records.
The same configuration also allows an update to an authority record to trigger updates to restricted bibliographic records.
[Record Page] An entry for the RIS format was added to the list of export formats.
In the list of export formats on the record page, we've added the RIS format as an option.
[Acquisitions] Updated handling of penny rounding for items and invoices
A new rounding strategy has been implemented, which improves the rounding when working with foreign currencies and exchange rates on item costs.
Read more about this in our documentation.
[Global Lists] When exporting invoice lines from global lists, the system reports an error if the cost of the individual items differ from the cost of the invoice itself. Previously, this error was generic, but now the error references the affected invoices and prompts the user to re-save the invoices.
[Misc] The cancel button used in several editors will now attempt to go back in the browser history, or else close the tab after confirming
[Misc] Several Alert boxes and confirm/cancel buttons are now set up to use consistent design components
[Users & Access] When matching patron records with users logging in through SSO, the system will now attempt to match in order on: (1) external id, (2) uid, (3) email.
Read more about this in our documentation.
[Acquisitions] When an item in an order is linked to an invoice, adding a second item in the order form would inadvertently link that item to the invoice of the other item
[Acquisitions] In the invoice form, vendor charge non-taxable would inadvertently be added as tax on the individual items
[Circulation] Some legacy parts of the system was able to create patron records with duplicate email addresses.
[Misc] The sorting of files was done based on a subtly flawed alphabetical sorting, which for a small set of records could result in (1) unexpected search results thumbnail, (2) unexpected image order in the universal viewer, (3) unexpected order of audio file track listing.
[Record Page] The disabled download button for a View only file could still be used to get the link and download the file.
[Record Page] Some display elements rendering call numbers would disregard subfield order within the MARC record
[Record page] In some cases a Details display element could end up trying to retrieve details about the entire set of records, eventually causing a timeout.
[Search] A broad search for Chinese/Han characters would result in no search results found
[Search] For some templates, when the record has multiple files attached the PDF preview functionality on the record thumbnail would not work.
[Submissions] Administrative data stored in MARC tags (e.g. reviewer email address) could be unavailable if that tag was suppressed. This could cause the submission workflow to stop.
[Submissions] Using DOI to import data into the submission form would fail because a metadata provider (Datacite) deprecated an API that was used for the import. The import has now been updated to use a new API provided by Datacite.