Talis Aspire Product Updates
New features and product updates
Improvements
  • Following customer feedback we have added a new editable field to the Dictionary in Talis Aspire Digitised Content. The message is sent to the academic when an item is withdrawn by the library. You can customise this under Settings - Dictionary
Improvements
  • Following examples from customers and discussions with the Copyright Licensing Agency (CLA), we have made some improvements to Talis Aspire Digitised Content (TADC) to ensure that the reason for an outcome is clearly communicated to a user so that any perceived disparities between actual results of the CLA Check Permissions API and the TADC concierge result are clearly explained - Changes to Talis Aspire Digitised Content - Concierge Results

Improvements
  • Following customer feedback we have made an improvement to the the Concierge within Talis Aspire Digitised Content (TADC) so that even when the CLA approves a request, you may have full permission from another source, an example being that the Academic is the author or rights holder and wishes to use the full work. For more details please see: Alternative Copyright Source
Improvements
  • We have now improved Quick Add so it directly links held items to the catalogue and displays availability, previously this was only linked following a book metadata refresh.
Fixes
  • When adding or editing page numbers in the edit metadata screen we have now corrected the display to show Page start and Page end in a logical order, previously defaulted to alphabetic display.
Improvements
  • We have released a change that should fix the behaviour you were seeing when links were reverting to DOI when editing bookmarks preferred Online Resource link. This was actually fixed as part of a larger piece of work. 
  • Customers can now choose which link is preferred when there are multiple link types in an Article. You can choose from Web Address, DOI and Open URL, in any order. For example, if you want web addresses to be preferred and never DOIs, then a preference order of "Web Address, Open URL" can be configured. The default order is DOI, Web Address and Open URL. Would you like us to set a specific order? Please raise a support request
Improvements
  • During a rollover, it is possible to select that lists in the old time period can be archived. Where those lists are under review, it causes problems if someone tries to access a review for an archived list. Archived lists are now treated like deleted lists in the review area i.e. they will be indicated as (Archived) against the list name in the reviews area and the review will no longer be accessible.
Improvements
  • We recently released a change to the rollover process to exclude published lists undergoing review from the rollover process. After feedback from customers and further review from us, we have decided to reverse this change as a number of customers may have a significant number of lists under review when performing their rollover and would cause additional effort in the workflow.
Fixes
  • We made a fix to an issue that was causing the UResolver lookup to Alma to fail because the institution code was not capitalised.
Fixes
  • The action buttons on the rollover queue pages were affecting all queues and not the specific queue selected. This has been fixed.
  • When a list is removed from a hierarchy node on the Hierarchy node page, it previously advised that the node would be deleted. We have fixed this so that the correct message will now be displayed.
Improvements
  • We added some additional information to the CLNZ reports for our New Zealand customers. The main and out of print (OOP) sheets in the report now include columns which will indicate where an override has occurred and the override comment, where a request has been manually overridden or where the OOP override has been used despite the availability of a later edition
Fixes
  • We fixed an issue which was preventing comments and outcomes being set on the last review item in a filtered set in Reviews 2.0
Fixes
  • We fixed a bug we introduced which was stopping the "Assign to me" option from appearing on the Assign action in Reviews 2.0
Improvement
  • We made some improvements to Reviews 2.0 to help you get back to where you were in a review. It will now not only remember your position in a review but also any filters you have set. The filter set takes precedence though i.e. if you were looking at an item within a filter set which then falls out of the filter set because you've made changes to the item, it will return you the the 1st item in the filter set and not the item you just changed. Reviews 2.0 will remember your position and filters even if you leave a review and come back later
Improvements
  • It is now possible to filter a review by the presence of library or student notes.
Happy New Year everyone! We've started 2017 off by releasing some improvements to Reviews 2.0

Improvements
  • We've resolved an issue which meant that chapters did not alert correctly for later editions in the left-hand column of a review. This is now resolved and you can now see alerts when a chapter belongs to a book that has a later edition
Improvements
  • We made an improvement to the rollover process to exclude published lists undergoing review from the rollover process. This prevents an issue we encountered which was allowing lists in review to be archived as part of the rollover process

Fixes
  • We fixed an issue which intermittently caused an error when adding a review outcome
Improvement
  • Talis Aspire Reading Lists now supports Koha catalogue and can display holdings and availability.
Fixes
  • When multiple reviews are assigned to a user, the view will now update immediately to reflect this
Improvements
  • Alma & Primo bookmarking:  We have made an improvement to how we bookmark from Primo for Alma users. This was specifically to address the issue preventing the population of the eBook URL for community records which did not have the URL in the 856 field which is our primary mechanism doing this. We have improved the Primo bookmarking process to using uResolver to extract the very same openURL link provided within Primo. This is in addition to first checking for an 856 for all records. 
  • Distinction in Reviews 2.0 alerts:  We've made some improvements to how alerts are displayed. We fixed some reported issues and have introduced a new alert type (indicated with a question mark in a grey pill) to identify lists and items we know have previously been reviewed in the old reviews area, but for which we are unable to determine whether there have been any changes. We are unable to determine changes because we are unable to provide difference reporting the first time a list is seen in Reviews 2.0. 

    This new alert makes it clearer when a review is definitely a new review, when a review definitely has some changes and when the system cannot tell.
Fixes

  • We fixed an issue that causes any action attempt, where the action has already been performed in reviews due to multiple tabs being open from causing errors. e.g. if there were two tabs open for the same review and it was completed in one tab and then you subsequently tried to complete it in the 2nd tab, this would previously cause an error.
Fixes
  • We fixed an issue that was causing list reviews to get stuck in "Started" status despite being "Completed" in Reviews 2.0
  • We fixed an issue that caused an error when trying to push a list review to Reviews 2.0 where the list had been deleted prior to the review being pushed to Reviews 2.0
Fixes
  • We fixed an issue that generated an error where an attempt was made to submit for review a list which had already been deleted. This typically happens where a list is open in multiple tabs in which a review can be requested in one and the list deleted in the other. We have fixed this so it recognises the 1st action and does not generate an error. 
Improvements
  • Force review workflow option - we have made an improvement to this workflow option. Both "Publish" and "Request review" options are available but on publish, a review request is sent to the library unless the user has the "View reviews data" permission, in which case, it doesn't force review. This means a review request is not created every time someone from the library publishes a list but only when an academic publishes a list.

Fixes
  • We fixed an issue that causes any action attempt, where the action has already been performed in reviews due to multiple tabs being open from causing errors. e.g. if there were two tabs open for the same review and it was completed in one tab and then you subsequently tried to complete it in the 2nd tab, this would previously cause an error.
  • We fixed an issue which was preventing the status of a review being updated to the rest of Reading Lists.
We've been working on further improvements and fixes to enable us to bring Reviews 2.0 out of beta.
Fixes
  • You will now be returned to the correct item and position in the single list review page after you have edited a list item from the review.
  • Chapters will now be correctly filtered when trying to determine whether the book is available in the catalogue or not.
Improvements
  • We made an improvement to display the comments and outcomes for all instances of an item as the default in Reviews 2.0. You can still select the "This list" tab if you want to view comments and outcomes from this list only.
Improvements
  • We have been working on some elements to bring Reviews 2.0 out of beta. Whilst not yet available to customers, we have been working on and released functionality allowing the lists to be sent directly to Reviews 2.0 when an academic requests a review. This means that the processing of the list occurs at this point rather than when the library wants to work on the list. 

Fixes
  • We fixed an issue preventing edits made to a list from being updated to the list review, for those reviews in requested state.
Improvements
  • We have been working on some elements to bring Reviews 2.0 out of beta. Whilst not yet available to customers, we have been working on and released the ability for the Reviews 2.0 area to support the requested state.

Fixes
  • We fixed an issue that meant that it was possible to raise more than one review request through multiple clicks on the request review button. This is no longer possible.
Improvement
  • We improved the display of user names so that they are displayed exactly as entered in order to stop the incorrect capitalisation of some names.
Fixes
  • We fixed an issue causing an error when trying to enter a comment or an outcome on an item which has been removed on the same review, in a different tab.
Improvements
  • General improvements to how users are handled in Reviews 2.0

Fixes
  • We fixed an issue which was causing updates made to a list from being processed in an existing review
  • We have pointed the hierarchy data format link in the hierarchy update page to point at the support page
Fixes
  • We fixed an issue that was causing login problems for some users in Reviews 2.0
Improvements
  • Following discussion with the University of Auckland and CLNZ, we removed the limitation preventing the Out of Print (OOP) workflow option from appearing from digitisation requests on which a later edition has been detected. The option will now always appear on all requests which have exceeded the copy limit
  • We made some improvements to support the changes to the Capita LDS availability service

Fixes
  • We fixed an issue which was causing users to be logged out of Reviews 2.0 after exactly 1 hour regardless of whether they were active or inactive.
Improvements
  • We made some improvements to the process that allows us to migrate historic review comments when migrating a tenancy to use Reviews 2.0. This is one of the improvements that will enable us to continue the migration process for customers waiting to move over to Reviews 2.0
  • We made some performance improvements to how we process queries in TADC. This should result in a general performance improvement in TADC.

Fixes
  • We fixed an issue that was causing the incidental artwork option to intermittently disappear for our Australian TADC users.
Fixes
  • We fixed an issue which was preventing the digitisation request form from appearing when the "Request digitisation" button was clicked on an item with multiple ISBNs
Improvements
We have been doing some performance improvements to allow us to enable historic comment migrations in Reviews 2.0 for those customers who have not yet had their comments migrated. We made the first of a few improvements in this area.
Fixes
We fixed the following in Talis Aspire Digitised Content:
  • Where British Library orders are available for download, we have changed the settings in our call to the British Library API, so that users will now be notified with the download link by email.
  • We fixed the link resolver link on the request form when users are notified of existing electronic versions so that they are directed to the correct results page on the link resolver
Fixes
We fixed the following in the Reviews 2.0 area:
  • Display both eBook link and digitisation status:  both of these things will now appear when both are present, previously it would only display the digitisation request. 
  • Student numbers modal size: we've improved this so that it will expand to the size of the content
Fixes
  • We released a fix to reporting in the CLL report which was not calculating the amount copied where the page ranges are in roman numerals
New features
We have now completed the final elements of the support for the CLNZ licence in TADC. The outstanding elements were to support the capture of the transactional copy licence and out of print workflows and the subsequent reporting requirements.

In earlier releases, we introduced support for the capture for both the transactional copy licence and out of print options by introducing options to capture this when a request exceeds the copy limit and these workflows occur outside of TADC.

They appear as options in the “Copyright obtained” menu. Selecting either of the options will also require the entry of the relevant reference number which will have been provided by CLNZ as part of your workflow. The only instance where the out of print option is not available is when TADC has detected that there is a later edition, as it is stated in the licence that this will be rejected by CLNZ.

Digitised_Content____Talis_Aspire.png 78.4 KB
Each workflow is reported in a separate tab of the report of the audit report according to the specification agreed between the University of Auckland and CLNZ. These tabs contain exactly the same information about the requests as the main tab, with the addition of a column which will be populated with the reference number.

We appreciate that you have been managing these workflows and recording them outside of TADC. If you can provide us with a CSV file with the following 3 columns, in the following sequence and format, we can update the requests in TADC for you and ensure that those historic requests can be reflected in your reporting. 

  1. TADC Request Number
  2. Transactional licence reference number
  3. Out of print reference number

Each row should either have column 1 and 2 populated OR column 1 and 3 populated depending on which type of request it is. All 3 columns cannot be populated.  Please submit a support ticket with a request to do this and a CSV or spreadsheet file with the requests you would like amended.

Fixes
  • List bibliography export - we have solved the issue that was stripping out spaces from the reading list bibliography PDF export.
New Features
  • Transactional copying reporting for CLL ruleset: Following on from our recent release to enable our TADC customers in New Zealand  to indicate when they have done transactional copying for digitisations over the copy limit, any such digitisations are reported in a separate "Transactional copying" tab of the CLL audit report.
  • Out of print workflow for CLL ruleset: Our TADC customers in New Zealand are now able to indicate when they have used the out of print workflow for digitisations over the copy limit.
Digitised_Content____Talis_Aspire.png 78.4 KB
Fixes
  • Availability for items without an ISBN in Reviews 2.0:  where a tenancy had no acquisitions supplier enabled, there was an issue preventing the display of availability for items without ISBNs. This has been resolved and availability for such items is now visible.
Fixes
  • We fixed an issue that was generating an error if an incorrect URL was entered for a review in Reviews 2.0. The system will now redirect you to the All Reviews page if it detects an invalid review instead of generating an error
New Features

Support for Web Bridge resolver: Talis Aspire Digitised Content is now integrated with the Web Bridge link resolver. Customers with this resolver are now able to successfully process digitisation requests for  journal articles.

Transactional copying for CLL ruleset: Our TADC customers in New Zealand are now able to indicate when they have done transactional copying for digitisations over the copy limit
Digitised_Content____Talis_Aspire.png 98.09 KB


Improvements

  • Becoming a list owner adds list to "My Lists" area: We made an improvement which now adds a list to a user's "My List" area when they are assigned as the list owner.
Fixes
We fixed an issue that was causing the date fields in the digitisation form to remain editable, despite the "protect dates" option being set. This is resolved and dates are protected again
Improvements
  • We made an improvement to the worklog display for CLA customers using Talis Aspire Digitised Content. When we check permissions with the the CLA TitleSearch API, the identifier (i.e. ISBN or ISSN) is now displayed against the response received. This is useful when there are multiple identifiers (e.g. ISBNs or ISSNs) on a request which generate different responses. It is now easier to tell which response from the permissions check belongs to which identifier.
Fixes
  • We made some further fixes to the behaviour of EBSCO Fulltext Finder in Talis Aspire Digitised Content so that certain responses for journal articles do not result in an error, and it is possible to submit the digitisation request.

We released a fix in Talis Aspire Reading Lists to the character encoding issue affecting the display of ampersands in the list section title and notes when viewing a list. They were previously appearing as "& amp", but now you will get the proper display for an ampersand (&).
We fixed an issue which was causing intermittent errors when trying to view a digitisation bundle. If for any reason the service which helps us to serve up the digitisation bundle images very quickly was uncontactable, we were failing to use our backup correctly. This has been fixed now so that an error is no longer generated in this scenario and users can always access their digitisations.
Improvements
  • We improved the EBSCO Fulltext Finder resolver yo support its non-standard treatment of dates, which was causing unexpected and incorrect results in both in Reading Lists when checking the resolver and in Digitised Content when raising a digitisation request.
Fixes
  • We fixed an error that was being generated in the Reviews 2.0 area of Reading Lists when it is unable to connect to the library catalogue. It will no longer generate an error but interpret the response correctly and let the user know that it is unable to connect to the catalogue.
Fixes
  • We fixed an issue where time was being displayed in hours and seconds (HH:SS) instead of hours and minutes (HH:MM). Time has been properly restored in Reviews 2.0