This article identifies how Talis Aspire Digitised Content (TADC) uses your link resolver and the benefits of this integration.
What is a link resolver?
As you know, a link resolver is something that searches your institution's holdings to see if you have access to a resource, for example: a journal or an article. If the article has a Digital Object Identifier (DOI), your link resolver then tries to determine not just whether you have the journal, but whether you have access to that particular issue.
How does the link resolver work in Talis Aspire Digitised Content?
In TADC the concierge will use the link resolver to determine if you have holdings of electronic journals and articles. The link resolver looks up articles using the journal's ISSN to see if the institution has access, following these steps:
- 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 held in your catalogue, it assumes it is print. These will always be referred because we cannot consistently identify print serials holdings (unless it knows there is a fee pay copy).
How to review and update your link resolver in Talis Aspire Digitised Content
This is actually something you can update yourself if you have the admin role within Talis Aspire Digitised Content.
- Click on Admin and select Settings
- Select the Services tab
- Review and update the details and Click 'Save'.
If you don’t have a link resolver, what difference will this make?
As part of the workflow in Talis Aspire Digitised Content, the concierge will check to see if your university/institution have holdings/access to the requested item. If you don't have a link resolver enabled in TADC, the system is not able to perform this check. Therefore, these requests will be referred by the system and you will need to manually check and confirm you hold the item before the request can progress.
Staff member reported that the Request Reject workflow was using our old link resolver - I thought this would be something Talis would have to change (like it was in Talis Reading Lists).
I was creating a support ticket and this article was a suggested solution. It doesn't mention how you set the link resolver but on the off chance I thought I'd take a look at TADC Admin Settings (I don't think I've been in it since we went live) and saw it was indeed locally configurable. Not sure if there is an article about that that the support thingy should have suggested, or whether this article would benefit from a brief mention of how to do it.
Thanks so much for flagging that this information wasn't in the article - I agree it definitely fits in here. I've added in the instructions.