*This solution is only for libraries using NC LIVE Hosted Proxy or a local proxy *
We have found a solution for libraries using MARC records for RBdigital who have NC LIVE Hosted Proxy or a local proxy. Currently, the link in the 856 field is not directing users to the title record page. Instead, users are directed to the RBdigital homepage.
The problem is caused by the hashtag (#) in the RBdigital URL. To fix this, please encode your 856 URLs in the following manner:
https://login.proxy189.nclive.org/login?url=http://[RBdigital Library ID].rbdigital.com/#titles/9781449872212
https://login.proxy189.nclive.org/login?qurl=http%3a%2f%2f[RBdigital Library ID].rbdigital.com%2f%23titles%2f9781449872212
If you have local proxy, please update your RBdigital proxy stanza to the following:
Title RBdigital Audiobooks
URL https://[RBdigital Library ID].rbdigital.com
HJ https://[RBdigital Library ID].rbdigital.com
HJ [RBdigital Library ID].oneclickdigital.com
If you need MARC records for RBdigital, please email email@example.com
We are still working on a solution for libraries using NC LIVE easy-on and the NC LIVE password. We will update you when we have more information.
This issue appears to be happening with all libraries using a proxy prefix or the NC LIVE prefix in front of RBdigital individual title links.
On-campus users will be directed to the RBdigital homepage. Off-campus users will get an error screen "To allow http://libraryxx.rbdigital.com/ to be used in a starting point URL, your EZproxy administrator must first authorize the hostname of this URL in the config.txt file."
We will update you when we have more information.
Links to individual titles in the 856 field in NC LIVE modified MARC records for RBdigital are currently not working. Users will be directed to the RBdigital homepage, instead of the title record.
Links in the 856 field in NC LIVE modified MARC records, have the NC LIVE prefix and look like this:
Titles are available if you search directly in the RBdigital interface, or remove the NC LIVE prefix from the link. We are working on a solution, and will update you when we have more information available.