Below are a range of frequently asked questions on Talis Aspire Digitised Content (TADC). If you have any questions not covered below, please let us know by raising a support ticket.
Q. How do people get access to the TADC concierge?
A. Students do not need access to TADC to view a digitisation. They simply need to authenticate in Talis Aspire Reading Lists (TARL) to view their digitisations.
To enable staff to process requests and complete reports in TADC, please see our support article on setting up and managing users in TADC.
Q. How does the system work out whether or not a resource is eligible for digitisation?
Before any checking can occur the system must first identify the item accurately. It does this by looking up the resource in your library catalogue, and in the case of items not held by you, in the catalogues of your peers and national library services. See request identification and edition checking support article for more information. If the item cannot be accurately identified the request is referred to your digitisation staff for manual identification.
Once an item is accurately identified, copyright checking can begin.
Specific RRO Checks
The concierge utilises the CLA Check Permissions API which provides a clearance response for each digitisation request. When a request is raised, the concierge automatically checks against the API to determine whether or not a request is allowed under the terms of the licence. Where the system is unable to contact the API, receives no response or received an unrecognised response from the CLA API, it will revert to a feed of the included territories, excluded works and included digital titles as published by the CLA.
In addition, the system will also enforce copy limits (eg. up to 10% or 1 chapter of a book per course instance) and other rules such as availability in the library, latest edition and the presence of an electronic copy.
The rules governing the ability to clear under the CAL licence have been built into the TADC ruleset for Australian tenancies. When a request is raised, the concierge automatically checks against this built in ruleset. The system will enforce copy limits (eg. up to 10% or 1 chapter of a book*), presence of an electronic copy, and other rules inline with the CAL licence.
*The divisibility setting for the copy limit (across the institution or by course) is set for the entire tenancy and can be updated under settings - see our CAL divisibility behaviour options support article for more information.
CLL (New Zealand)
The rules governing the ability to clear under the CLL licence have been built into the TADC ruleset for New Zealand tenancies. When a request is raised, the concierge automatically checks against this built in ruleset. The system will enforce copy limits (eg. up to 10% or 1 chapter of a book across the institution) and other rules inline with the CAL licence.
Irish Copyright Licencing Agency (ICLA)
The ICLA do not have the check permissions API that Talis can access. The benefits of using TADC with the ICLA setup is it automates check editions, enforce copy limit (eg. up to 10% or 1 chapter of a book per course instance), reporting and library holdings.
The ICLA has given Talis guidance that they will not penalise universities from the resulting reporting, it is to help the better distribution of royalties to the publishers based on content use. Talis would suggest if you have concerns about the check permissions aspect and availability of the API to speak directly with the ICLA. Talis have included wording from the ICLA licence in Talis Aspire Copyright Clearance to prompt further permissions checks for Exclusions.
Q. How does the system determine whether a request is for the latest edition?
We use information from Nielsen BookData to determine the latest edition of a book. For non-ISBN items, requests will be referred for a local decision. For more information on this, please see our support article on request identification and edition checking.
Q. How does the system detect the presence of electronic copies?
This is mainly done by interrogating the MARC record.
- First we check the 008 position 23 for an 's'
- Then we check the 245$h for the regex /electronic resource/i
- Then we check the 856 ind1='4' ind2 = '0'
If any of those conditions are true, we assume an electronic copy exists.
We only check what is held by the library, we don't reject if there's an ebook that the library doesn't hold.
- Check the link resolver to see if the library holds the article electronically.
- Check the catalogue to see if there is any match to the ISSN/eISSN
- The Concierge will also check the format here, if it only finds an e-journal record*, then it will defer to the link resolver to determine holdings (that is, it ignores the catalogue in this case)
- If the Concierge cannot determine the format, it assumes it is print. It always refers these because we cannot consistently parse serials holdings, so if the Concierge thinks that there is any print coverage (and no electronic), it will always we refer the digitisation request (unless it knows there is a fee pay copy).
- Check for fee pay copies.
* To determine if a MARC record is for an electronic resource we check:
- 008 position 23 for the value 's' or 'o'
- 006 position 6 for the value 's' or 'o'
- 245$h for 'electronic resource'
- 338$a for 'online resource'
- 338$b for 'cr'
- 856 with indicators "4 0" (and a subfield 'u')
Q. Can other institutions see the scans in my vault?
A. No, scans in your vault are private to your institution.
Q. Why can't I request a digitisation from a document?
A. You are only able to place a request for journal articles, book chapters or sections of books. This is because TADC is for copyright management of resources, and not a repository for all digital content.
Q. I've deleted an item on my reading list and added it back on in another location, however the digitisation request is not appearing on the new item. When i raise a new request it is rejected/referred as a duplicate request.
A. A digitisation request is linked to a specific item. Once the item is removed from the reading list, the linked request remains LIVE in TADC, but is not available from the reading list. This is the reason behind why your new request results in a duplicate request. The solution is to withdraw the LIVE request, then edit and resubmit the duplicate request so that it goes back through the validation and compliance checks, and once successful go through to LIVE.