RELEASE NOTES - TIND 1.13.0
Acquisitions: Update expenditure and encumbrance in the fund record (Phase 1) - [Acquisitions | ILS]
TIND ILS Acquisitions tools are now more closely integrated. In this first of two planned updates to acquisitions, the TIND purchase order and invoice forms will now automatically update the funds they are linked to in terms of appropriation, encumbrance, and expenditure.
Funds have been updated to include status, type, fiscal year, and an option to create hierarchical relationships between funds, such as top level Parent Funds and the child Detail Funds, to replicate existing library fund structures.
Users with sufficient permissions can update the appropriations of child funds which can be selected by POs and Invoices to be encumbered and expended throughout the acquisitions workflow.
Changes in the funds are rolled up to the parents and accounted for in the fund hierarchical tree, and a graphical snapshot of the fund hierarchy can now be seen within each fund.
A fiscal year report respecting fund hierarchies can be downloaded from the administration menu view.
This feature represents the core Acquisitions workflow which is ready to use in 1.13. Acquisitions Phase 2 will cover additional specific workflow needs and is already in planning for deployment in the next release.
For full documentation, please see:
📋 Managing Funds using the Fund Editor
Customized Item Table in the Record Page - [Circulation | ILS]
It is already possible to customize the display of columns in the item table of the Detailed View, such as Options, Library, This new feature enables additional customization options such as whether a column is visible or not, the order of columns, and the default ordering of columns. It also adds the option to add volume and issue.
Enabling these customization will require contact with TIND Support.
Documentation available here:
📋 Listing item records in a bibliographic record
Option to allow holds only on items on shelf - [Circulation | ILS]
This new configuration determines which item statuses permit hold requests. The out-of-the-box setting will continue to allow hold requests for all item statuses, but it can be configured to not allow hold requests for items that are on shelf.
When determining whether a user can place a hold request on an item, the system will first consult a user-defined list of item statuses. If the item in question has an item status in this config, then the system will deny the request. If not, the loan rule determines whether to allow or deny the request.
For more information, please see documentation:
📋 Configuring loan rules and rules selection
Batch Actions: Delete Files - [File Manager | IR, DA, RDM]
This new feature provides a simple way to delete files in bulk using the new File Manager. Previously, when uploading digital files the user would need to remove them individually from the upload screen.
Delete will now appear as an option in the File Manager to delete all Files.
Additional batch delete options are planned as enhancements.
For full details please visit our documentation:
📋 Performing Batch Actions on Files
📋 Deleting Files from a Record
File Manager - [File Manager | IR, DA, RDM]
TIND has fully released the new file manager, initially delivered to specific customers for early release in 1.9.0. The new file manager includes a revised design, can manage custom file-level metadata such as license and publishing version, and handles direct-to-object storage uploads.
Users can drag and drop files in a specific order to control the sequence in media previewers and thumbnail generation.
The new design incorporates recognizable components from other parts of the platform, which results in a more consistent overall user experience.
Custom metadata can be completely configured on a customer by customer basis. For example, if a license field is configured, the available licenses are shown in a drop down menu. If a field is configured to be mandatory, the file manager will enforce it.
The file table in the record page has also been updated to support rendering custom file metadata. The license column, which was previously rendering data from the bibliographic field 542, can optionally be configured to instead render from a file level license field.
In addition to custom metadata, we are introducing the concept of explicit file order. Previously, files were ordered alphabetically by the file name. Using the new file manager, individual files can be reordered using a drag and drop interface.
Thumbnail generation and media previewers will render files based on the explicit order, and files can be explicitly ordered alphabetically using a new ORDER-NAME-ASC FFT action.
The 1.13 update will not automatically enable the new file manager; this has to be done in collaboration with the support team.
To learn more please see our documentation:
OCR Service Delivery Enhancements (Phase 1) - [OCR | DA, IR]
Optical Character Recognition (OCR) is now an optional service available in TIND. This service automatically performs OCR on files ingested via the File Manager or submission forms. This feature is developed together with the new file uploader interface, so whenever a new file is uploaded, a new task is started to run OCR.
OCR uses a credits dashboard to run this routine, which is available to customers through the TIND Admin Center.
Additional tools for further configuration of how OCR is performed will be available in Phase 2. For more information on OCR, please contact TIND Support and see the full documentation:
📋 Automatic optical character recognition
Personalize Menu - [Misc | All TIND Products]
The log-in label can now be suppressed or the text can be changed to meet local preferences and avoid any potential confusion from end users. Similarly, features such as the Personalize button can be hidden when the user is not logged in, if this is not part of intended system use.
For more information please see the documentation:
📋 Logging in to the repository
Facets - Remove Trailing Punctuation - [Misc | All TIND Products]
This new feature normalizes the list of facets, simplifying options for the end user by removing duplicate entries that have only minor differences in punctuation. The MARC records are not altered, but the facets are matched more accurately for a cleaner presentation to the end user. For example, in instances where both “United States.” and “United States” both appear as facets, these would be normalized to only display “United States”.
For more information about facets please read additional documentation:
📋 Configuring facets, custom aliases and other search features
Acquisitions
Display
Batch Downloads
Submission Forms
