RELEASE NOTES - TIND 1.23.0 - DA, IR, RDM
Welcome to release 1.23.0!
TIND 1.23.0 is a major release. There should be something for everyone in this release, including some noticeable interface changes making TIND even more accessible, a new configuration module allowing repository administrators greater control over the display of their assets, as well as smaller (but no less exciting!) user features across all products.
With this goodie bag of updates, we wish you all a great summer
The release schedule is as follows:
> Release 1.23.0 Sandbox & Early Release Instances
> Release 1.23.0 to all TIND instances
> Release Webinar
Accessibility across the TIND platform is always a priority when we develop new features, but every now and again we need to make more substantial changes across the platform to ensure we are compliant with emerging accessibility requirements. With the goal of reaching AA-WCAG compliance, we have updated the colour scheme, contrasts, and general readability in all user-facing modules; including the front page, search interfaces, the record view, and many more.
As part of this work we have limited the use of different colours and various versions of the legendary “TIND Blue”; instead creating contrast and variation through the use of font sizes, shades and weight, hover effects on links, and similar adjustments.
In an upcoming release, these changes will also be applied to Administration modules and interfaces where they are not yet in place. Further, we are aware there are certain features that will require rework in order to reach AA-WCAG compliance and we expect similar updates in future releases.
Instances with custom branding should not see any changes to customised button and font colours, hovers etc., but if you do experience changes affecting the usability of your instance due to local branding, please reach out to us and we will work with you to adjust these settings.
📜 See Documentation for AA-WCAG Compliance
Earlier this year, the new Multi-Viewer was introduced to TIND Repositories and Digital Archives, allowing preview of multiple media types in the record view by consolidating existing viewers into a new tabular interface. To complement this feature, we are now launching a brand new module which allows system administrators to customise not only the default display of the viewers, but also to create your own configurations and apply them to sub-sets of records.
There is a multitude of configuration options available, including:
adding additional viewer panels (collection of viewers)
adding and removing viewers
renaming and translating viewer and viewer panel labels
reordering viewers and viewer panels
collapsing viewer panels by default
This is also the first step in a larger initiative to make more configurations available directly in the interface. After this summer we will be hosting a training webinar where we will go through all the available functionality in more detail, so make sure you sign up for this to get the full benefit!
📜 See Documentation for Multi-viewer Configuration Module
A new button now appears in the Action Bar in the Detailed View for records that have been submitted through a submission form. This button has the same functionality as the “Edit record in form” link in the Submission Information section further down on the page, but in a more accessible location.
Just like the Edit link, the button only appears to users who have the rights to open the record in the submission form.
📜 See Documentation for Action Bar
Previously, the thumbnail order was decided based on file type, always displaying an image file thumbnail if at least one image was attached to the record. Now, the thumbnail in the search results follows the viewer order. For example, if the first viewer in the multi-viewer is the Video Player, the thumbnail from the first video file will be displayed in the search results for this record.
📜 See Thumbnail Order in Viewer
In the Submission Dashboards, it is possible to choose whether to wrap or truncate the text inside the tables. By default, the text will be truncated but users can now choose to set this to wrap instead. The change will apply to all tables and dashboards.
Contact TIND Support in order to change this configuration
French and Norwegian
translations have been added to the Related Items section of the RDM record Detailed View.
Several interaction and error handling issues have been improved when adding multiple files in the File Manager. It now:
Email editor improvements
[Workflows / All Products]
For monolingual instances, the initial language selector prompt has been removed when updating an email within a workflow. For multilingual instances, the dropdown remains, but the button has been renamed from “Save” to “Confirm”.
An information message “Preview not available” has been added to inform users that a ZIP file cannot be previewed when an undefined error has occurred.
.
An option to place records in baskets was visible to users in the Alerts module, even when the Baskets module had been disabled. There is no longer a reference to the Basket module when creating/editing Alerts in these cases.
Various security fixes and improvements have been implemented.
In specific situations, an item record could have the record title field displayed with title subfields in the wrong order, e.g. subtitle before main title.
When updating the due date through the Loans list action in Global Lists, the hour would change upon save. The selected hour will now be retained.
Renewing loans on behalf of a patron with an expiration date did not adjust the expiration date correctly when the action was initiated on the Loans details page in the Circulation module. The due date will now automatically set to the expiration date of the patron if the loan period exceeds this date.
When exporting specific datafields with subfields in the Excel export, blank indicators would previously operate as wildcards. For example, specifying 700__a in the list of fields to export would wrongly lead to fields with values in the indicator positions, e.g. 7001_a, to be included in the exported report instead of excluded. Using blank indicators (_) will now exclude datafields with values here, whereas the % still operates as a wildcard. That is, asking for 700%%a will ensure that both 700__a and 7001_a are included.
Fields that were suppressed from exports for certain users would be missing from the CSV export, even for users with access to them. This has been changed so that suppressed fields will be included in the export as long as the user is allowed to export them.
Using IIIF manifests to display records from TIND inside the Mirador Project was failing. We have now fixed the restrictions so this is no longer the case.
While files were being loaded into the Files table in the Detailed View, some navigation elements were wrongly displayed and could be interacted with, influencing the files list upon completed load. This is no longer possible.
Clicking the “Export records” button when in Table View mode in the search results would render the dropdown inside the table and hence obscured. It now displays in the same way as with the regular search view.
Spreadsheet files above a certain size will not render in the Spreadsheet Viewer. However, such files would appear in the dropdown list with a “processing” message, giving the impression that they would become available in future. The message now reads that the file size exceeds the maximum limit, which is 500 MB.
If a record previously had an attached image file which since had been replaced with a different file type with the same name, the Universal Viewer would attempt to render the image file and remain in a “loading” state. This has been fixed by only considering the latest version of files when rendering viewers.
The Universal Viewer has been updated to the latest version in order to solve an issue with downloading images through the download button.
For files with long names and/or descriptions, the dropdown area would extend beyond the page limits when clicking to select a file. Now, the text will be truncated. Hovering on the text area will still display the full text value.