RELEASE NOTES - TIND 1.16.0
IR / DA / RDM
We are happy to announce the TIND 1.16.0 release. This is a major feature release with new features, fixes and changes for all products.
The release schedule is as follows:
> Release 1.16.0 Sandbox & Early Release Instances
> Release to all TIND instances
> Customer Release Webinar
[Search | ILS, DA, IR, RDM ]
TIND ILS customers can now activate Index Browse search. This new feature enables end users to browse and search within indexes of terms for specific fields such as Title, Author, Call Number, and Subject. Indexed terms are displayed in alphanumeric order, show the number of matching records in the catalog, and include a link to retrieve matching records. Submitting a query in Index Browse returns potential term matches within the index or highlights the point in the index where the term would appear if not present.
Selecting a matched term returns the traditional search result page where users can continue exploring the results using standard search tools such as facets and format options.
We received valuable feedback from beta testers, and in addition to solving some issues, this version includes
Displaying multiple subfields through concatenation
Possibility to configure the search box placeholder text per index (e.g. replace “Search Author Index” with “Search for Dickens, Charles”).
Improved call number browse
Enabling/disabling case sensitive search and sort
Future improvements will include
Removal of non-filing characters from the Title browse such as “the”, “and”, or “an” as well as other languages
Index browse availability in other TIND products. If you are interested in setting up index browse for your IR, DA or RDM instance, please contact TIND Support.
To learn more, visit: https://docs.tind.io/articlec1h7dgayie-index-browse
[Detailed View & Search | DA, IR, RDM]
TIND users can now track the number of record views by end users visiting your page. This is in addition to the existing feature tracking the number of downloads, and you can now also differentiate between unique and total usage counts and export the results in csv format.
View and Download statistics are viewable at the bottom of the record Detailed View and search results page, depending on the user’s access rights.
To learn more, visit:
[API | ILS, DA, IR, RDM]
TIND has released a new API infrastructure. This will make it easier for local developers to interact with your data in the future. Error handling has also been improved.
This includes:
[Submission | IR, DA, RDM]
TIND is introducing a native dashboard to monitor and interact with the submission workflows which today are managed mainly via email and the Detailed View. This will enable staff and end users alike to access a personalized dashboard where they can review and modify submissions as they travel through the workflow.
Staff users can take actions on a submission directly from the dashboard, such as approve the submission, request changes from the submitter, or open the record in the submission editor for modification.
Each dashboard consists of one or more configurable sections; they can be organized by submission type or workflow step and be made searchable using a dashboard search bar.
This feature must be configured to support existing workflows. TIND Support will reach out to all customers who will benefit from transferring their submission workflow to the new setup.
To learn more, visit: https://docs.tind.io
[Search | ILS, DA, IR, RDM]
TIND now supports the Schema.org type CreativeWork and its sub-schemas. Schema.org was founded by Google, Microsoft, Yahoo and Yandex to promote a common schema to try to understand more about what they are indexing. By having websites provide metadata according to schemas from schema.org, they can achieve this. TIND is now outputting metadata as JSON-LD in the HTML document of the record Detailed View. Search engines do only have access to the metadata for publicly available records.
To learn more, visit: https://docs.tind.io/article/f8i40gqg4g-integration-of-schema-org-schemas-for-improved-seo
[Authorities | ILS, DA, IR, RDM]
TIND now supports the Schema.org type CreativeWork and its sub-schemas. Schema.org was founded by Google, Microsoft, Yahoo and Yandex to promote a common schema to try to understand more about what they are indexing. By having websites provide metadata according to schemas from schema.org, they can achieve this. TIND is now outputting metadata as JSON-LD in the HTML document of the record Detailed View. Search engines do only have access to the metadata for publicly available records.
[File Manager | ILS, DA, IR, RDM]
A default file format was added upon upload if a file did not have a format specified. If a file does not have a valid file format, it will now be blocked.
[Collections | ILS, DA, IR, RDM]
Fixed a bug where collections were successfully created but not immediately searchable
[Batch Uploader | DA]
Corrected system behavior for the Batch Uploader in delete mode. Matching on 035 field will no longer delete the 035 field.
[Thumbnails | DA]
Fixed a bug where thumbnails were not being generated for uploaded materials.
_________________________________________________________________
[Search | ILS, DA, IR, RDM ]
Advanced Search (Customer Release) is tentatively scheduled for the 1.17 release after receiving additional beta feedback from users.
[Search | ILS, DA, IR, RDM ]
TIND has delayed the removal of the Checkout (Legacy) option from Circulation. It will now be removed in the 1.17 release. The legacy option will be deprecated to continue focused development on the enhanced Checkout tool made available as beta last year in the 1.11 release (https://info.tind.io/roadmap/1.11.0).
Translations [ILS, DA, IR, RDM]
Updated translation for the PDF Previewer "Select file" translation to include French, German, Italian, and Norwegian in addition to English.
DataCite [ILS, DA, IR, RDM]
TIND supports the DataCite Metadata Schema 4.4, a list of core metadata properties chosen for an accurate and consistent identification of a resource for citation and retrieval. This enables TIND to send data to DataCite following the 4.4 schema.
