RELEASE NOTES - TIND 26.0.0
We are pleased to announce TIND release 26.0.0. Important and exciting changes are coming to TIND Submission Forms this year! In the previous release, we cleaned up the interface and now we have the first installment of several planned improvements to the submission forms functionality including support for repeatable subfields. This has been a long-awaited addition and was a tough nut for the team to crack, but the work has laid the foundation for more robust and modern submission workflows, and hopefully sometime in the future for an administrator interface to create, edit and manage your submission forms.
The 26.0.0 release schedule is as follows:
> Release 26.0.0 Sandbox & Early Release Instances
> Release 26.0.0 to all TIND instances
> Release 26.0.0 Webinar
[Integrations | DA,]
For ArchivesSpace users, TIND now offers an integration where you can, through any means of record ingestion or update, generate an Archival Object with a linked Digital Object in ArchivesSpace, and add it to a specific resource in your ArchivesSpace repository. When the ArchivesSpace record has been created, it’s URL is sent back to TIND and automatically added to the original record, creating a two-way link between the two.
[Integrations / IR]
Through the Sword 2 protocol, thesis and dissertations that are registered in ProQuest can now be ingested directly into TIND. Currently, records are created using default metadata crosswalk, and files are automatically attached to the record. Further development of this integration will include the option to add a custom import profile using xslt, allowing professional users to transform the incoming records upon ingestion.
[Submission Forms / IR, RDM]
You can now have input fields with repeatable subfields in your submission forms. This means you can. for example, add, multiple affiliations for your authors.
This addition resulted an upgrade to several aspects of the submission forms in general. Adding this feature to your forms will require a reconfiguration. Please contact Support for more information.
[Video Player / DA, RDM]
Video files with restrictions are now processed for preview in the Media Previewer on the record page in the same way as publicly available video files. As with other file types, viewing any video file will depend on the access rights of the user.
Shortly after deployment of this release, the system will start processing restricted video files which have already been ingested. Within a few days the processing should be complete and restricted video files will be available for playback in your instance.
[Video Player / DA, RDM]
The media processing dashboard has received a user interface update to make it easier to track the status of transcoded media files. The different states have been split into separate tabs, and the limit of displayed files has increased from 100 to 500. It is also possible to remove failed processing attempts form the list after reviewing the error message.
With upcoming planned developments for media processing we will extend this dashboard to include processing metrics and status of transcription.
[Integrations / ILS., DA, IR, RDM]
The TIND Library Zotero Connector Citation tool mapping has been improved for the following fields:
Item type
Contributors
Dates
Improved mapping of URL fields and the inclusion of attachments are in progress and coming soon.
[Workflows / ILS]
There is a new workflow available which, when activated, will send a notification to both the patron that requested the item and the holding library when a hold request is cancelled.
To activate this workflow, simply navigate to the Admin Center → Workflows, and toggle on the “Hold Request Cancel Notice workflow”. The notifications can also be modified here.
[Metadata / ILS, DA, IR, RDM]
Concatenated fields can now be configured to preserve a specific order of subfields in the index, regardless of the order of the data fields in the record metadata. This is beneficial when using concatenated fields in the Index browse or search facets, for example, to ensure that the subfields appear in the correct order when displayed.
Read more about concatenated fields in our Search Indexes documentation.
[Metadata / ILS, DA, IR, RDM]
Custom Reports were recently activated for all users of TIND Analytics. TIND Analytics is using the platform Matomo, and this is how Matomo describes the Custom Reports:
Custom Reports is a feature that lets you create new reports in Matomo to get the insights you need in order to reach your goals and to optimize your website or mobile app. You can choose from over 200 dimensions and metrics as well as different visualizations.
Go to Custom Reports - Matomo to learn more and TIND Analytics to get started.
[Submission Dashboards / IR, RDM]
When performing certain actions from the Submission Dashboard, including sending an email with a note to a submitter or curator, you can now see a full preview of the email as well as add additional email addresses in regular or blind copy fields.
This update requires no configuration, except if there has been certain local adjustments made to the dashboard and/or related workflows, in which case the previous Notes modal is preserved. To update these as well, please contact TIND Support for manual configuration.
[Submission Workflows / IR, RDM]
Submission notes to reviewers/curators could previously only be configured to be sent to a specific, pre-configured email address. It is now possible to update the submission workflow email template to send a notification to all members of a system-defined role instead, using the new token role_email
in the “Email to” field. As this field is locked for edits, please contact TIND Support in order to change the recipients of your existing submission workflows.
[Submission Workflows / IR, RDM]
The Authority lookup in Submission Forms and the Record Editor can be configured with multiple providers, and TIND now supports the external knowledge graph FAST, managed by OCLC Research. FAST Linked Data.
Read more in our Authority Lookup Documentation, and contact TIND Support in order to set this up.
[Detail View / DA, IR, RDM]
In the Detail View “Files” section, the information in the “License” column is by default taken from the MARC field 542. Adding a field 542
with the license URL in subfield u
and optionally a license text in subfield f
will create a link to the license.
When configured, the License field can now be set to 540
, which is compliant with the current MARC 21 standard.
Read more in our Files Section documentation and contact TIND Support in order to apply this configuration.
File Manager
Batch Uploader
Exports
OCR Service
[General / [ILS, DA, IR , RDM]
A number of default terms and labels have been translated across these modules:
Submission pages
Submission dashboards
File Manager
Detail View
.
Collections [DA, IR, RDM] : Reindex if the number of records in the index become out of sync with the number of records in a the collection.
Date Slider [ILS, DA, IR, RDM]
Clicking enter after adding a value in the input field would lead to different actions depending on the type of search performed beforehand. The behavior has now been consolidated to apply the updated value on click.
When applying a data range to a search result, the Export button would initially be removed and reappear on refresh. This has been fixed.
Batch Uploader [DA, IR, ILS, RDM]:
Repeatedly clicking “Confirm” when using the Batch Uploader would lead to multiple, identical submission tasks, leading to failures due to unchanged records updates or the generation of duplicate records. The Batch Uploader will no longer allow the user to click Confirm more than once.
Logs from large batches are split into multiple files, but only the first file would be included in the log email. Now, any log and error files are zipped and attached to the email.
Circulation [ILS]: Roles with the action runbibcirculationcheckout
would not have access to the checkout module without also having the action runbibcirculationopeninghours
. This dependency has now been removed.
Authorities [ILS, DA, IR, RDM]: Fixed a problem where the authority lookup would fail if the record did not contain the authority linking field, usually 035__a
. Now, other fields will be mapped but there will be no link between the authority and bibliographic record.
Action Bar [DA, IR, ILS, RDM]: It was possible to configure the link-out button in the Action Bar in such a way that the link would be faulty if the number of links in the record did not correspond with the configuration (single vs. multiple links). This has now been fixed.
OAI-PMH Repository [DA, IR, RDM]: Removed and unspecified sets would be displayed in the repository if they were previously populated with records due to outdated information stored in the backend. This data will now be removed with regular intervals, ensuring that the set list is up to date.