Service Alerts and News

Service Alert: BLTI Error for Gale

Update 1/12/18:

The fix for the BLTI error needs to be done on Gale's side individually for each library that is experiencing it.

If your library is experiencing this error, please contact me so we can alert Gale and resolve the issue.

----------------

Some libraries are encountering an BLTI error page when they try to access TERC off-campus.

"BLTI Authentication failed

Error Code - Please return to your site and log in."

Continue reading »

Titles being deleted from Ebook Central and Credo Reference

219 titles have been removed from NC LIVE's Ebook Central collections (Public Library Complete and Academic Complete) as of December 21, 2017. We are waiting to hear back from ProQuest about whether MARC record updates and deletes are available yet via LibCentral.

28 outdated or low-usage titles have been removed from Credo Reference Academic Core as of January 3, 2018.

Please contact the NC LIVE Help Desk for title lists.

Continue reading »

ProQuest's eLibrary Curriculum Edition is now eLibrary

ProQuest's eLibrary Curriculum Edition has upgraded to a new interface. All NC LIVE member libraries have been upgraded to the new product, which will now be called eLibrary.

What you need to do
If you have this resource linked on your website, please change the name from eLibrary Curriculum Edition to eLibrary.

The NC LIVE link for eLibrary will remain the same: http://www.nclive.org/cgi-bin/nclsm?rsrc=413

Please see ProQuest's Support Article for more details and FAQs.

Continue reading »

Service Alert- RBdigital links to individual titles not working

Update 7/16/19: We are still working on a resolution to this issue. 

Update 1/10/17:

*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:

Continue reading »