Archive for the ‘Access problems’ Category

Problems with Scopus

March 5, 2018

Looks like we’re having a few problems with Scopus at the moment: it seems that we can access it fine, but we are seeing error messages either when we search, or when we try to navigate our results.

The problem has been reported to the supplier and it is hoped the issue will be resolved as soon as possible.


RefWorks in Discover@Bolton currently unavailable

February 14, 2018

So RefWorks within Discover@Bolton isn’t working at the moment (you could say it isn’t feeling the love… see what I did there…). RefWorks itself is working, so you’ll need to login independently – i.e. not from within Discover@Bolton – if you need to access it. This is part of a widespread problem that is affecting many users, and is being worked on. Apologies for the inconvenience.

Problems accessing RefWorks from within Discover@Bolton

February 12, 2018

Looks like we’re having a few problems with accessing RefWorks from within Discover@Bolton: we’re seeing error messages after putting in login credentials. The problem has been reported; keep checking this blog for further updates. Apologies for any inconvenience caused.

Problems accessing the library catalogue

January 17, 2018

We are experiencing problems accessing the library catalogue at the moment. It would appear that this is a nationwide problem. Hopefully all will be working normally soon and apologies for the inconvenience.

Problems with Discover@Bolton

November 21, 2017

There are major problems with Discover@Bolton this morning: searches are returning zero results (even my usual ‘test search’ chocolate, which usually returns millions…). This is part of a widespread problem that appears to be affecting all customers, and is being looked at as a matte of urgency. Hopefully this will be resolved shortly.

Times Higher Educational Supplement currently unavailable online

November 10, 2017

We are currently having problems accessing recent versions of the Times Higher Educational Supplement online. The publisher is working to resolve the issues and we hope this will be resolved as soon as possible. In the meantime, online issues are available up to six months ago; check the Ejournals portal for access details. You can even, if you are so inclined, follow THES’s Twitter feed. Apologies for the inconvenience; we are as frustrated as you.

Problems with electronic resource access at the moment

October 30, 2017

We are experiencing problems with electronic resource access at the moment and you may see an error message. We are working to resolve the problems as quickly as possible and apologise for the inconvenience.

MyiLibrary currently inaccessible

October 20, 2017

We are experiencing problems with MyiLibrary at the moment. This problem is affecting ALL users in the UK and the providers are working to resolve the issue as a matter of urgency.

Issues with accessing full-text via Discover@Bolton (but don’t panic; a workaround is available!)

October 16, 2017

We appear to be experiencing problems accessing full-text via Discover@Bolton, in that it would seem that at the moment, a few extra clicks are required to get to the full-text. We know this isn’t quite right and have reported the problem to the providers. However, we do have a workaround.

Once you have found an article you wish to access, make a note of the details (e.g. year/volume/number/pages etc.). Click on the link to the full-text. If you don’t get taken straight to the full-text, on the following screen, navigate to the year in which your desired article was published and find the correct article. You will then be able to access the article.

Apologies for the inconvenience. We know how frustrating it can be something doesn’t work as expected, and we are doing everything we can do resolve this issue. Keep checking this blog for further updates.

Royal College of Nursing journals update

September 25, 2017

Oh for some better news… The problems we have been experiencing recently with access to Royal College of Nursing journals have yet to be resolved. The better news is that we think we know what the problem is, and we are currently trying to arrange alternative access. Please accept our apologies; we fully appreciate how frustrating this.