These were the most popular searches in DISCOVER this May:
Monday, 2 June 2025
Thursday, 1 May 2025
Friday, 25 April 2025
RefWorks problems 25/04/25 - resolved
RefWorks have resolved the problems occurring this afternoon. Please let us know if you have any further issues.
RefWorks problems 25/04/25
RefWorks have notifed us that there are some problems occuring and that they are working on fixing them. If you notice anything odd (such as all your references having disappeared!) please try again later.
Tuesday, 1 April 2025
Thursday, 20 March 2025
Network upgrade 21-23 March affecting all campuses and library systems - now 28-30 March
We put out this advanced notice of downtime on 21-23 March - this has now been put back to 28-30 March
When will this be?
- Downtime: Friday 28 March 2025 from 18:00 – 23:00
- Downtime: Saturday 29 March 2025 from 08:00 - 23:00
- At risk day : Sunday 30 March 2025 - all day until 17:00
What will be affected?
All University ICT services and Internet access will be unavailable during the downtime period for staff and students on-site at all campuses.
- No Internet access on campus
- No Office 365 / Emails / Teams service from onsite computers
- No Access to applications hosted on site - this means that
- the library catalogue, self-issue and return machines will be unavailable
- login to DISCOVER and other digital library resources including ebooks, ejournals and databases will also be affected
Applications hosted off-site (e.g. Email, BREO) will be accessible off site only.
BMJ journals problem resolved
Monday, 17 March 2025
BMJ journals problem
Westlaw - access restored
Westlaw is back to normal - please email us at library.technical@beds.ac.uk if you have any further problems!
Thursday, 6 March 2025
Network upgrade 21st-23rd March affecting all campuses and library systems
What is ICT doing?
We are upgrading the core networking equipment at the Luton campus.
Why are we doing this?
As part of the ICT infrastructure investment programme, it is necessary to have service downtime to allow for essential upgrade work to take place.
When will this be?
Downtime: Friday, 21 March 2025, from 17:00 – 23:00
Downtime: Saturday 22 March 2025, from 8:00 - 23:00
At risk day : Sunday 23 March 2025 - all day until 17:00
What will be affected?
All University ICT services and Internet access will be unavailable during the downtime period for staff and students on-site at all campuses.
- No Internet access on campus
- No Office 365 / Emails / Teams service from onsite computers
- No Access to applications hosted on site - this means that
- the library catalogue, self-issue and return machines will be unavailable
- login to DISCOVER and other digital library resources including ebooks, ejournals and databases will also be affected
Applications hosted off-site (e.g. Email, BREO) will be accessible off site only.
Monday, 3 March 2025
Thursday, 13 February 2025
Digitised chapters/articles on reading lists - possible interruption 13th February
We've been warned of an update to the system behind our reading lists, which may affect the availability of digitised chapters/articles on reading lists. This is due to happen at 17:30, today, 13th February, for up to 30 minutes. If you have issues accessing content outside that time, please let us know.
Friday, 7 February 2025
MyBedsLife update
Thursday, 6 February 2025
RefWorks login working again!
We're really pleased to say that the problems affecting login to RefWorks have now been resolved, and it should all be OK again. Please let us know if you continue to have problems.
Monday, 3 February 2025
Tuesday, 28 January 2025
IEEE Xplore available again
We pleased to say that access to IEEE Xplore is now restored.
Please let us know if you have any further issues.
Monday, 27 January 2025
Problem with logins to IEEE Xplore
There is currently an issue with logins to IEEE Explore.
We are investigating and hope to have it restored soon. If you are on campus, please try this alternative link.
Tuesday, 21 January 2025
RefWorks login failing 21st January
We are having problems logging in to RefWorks today. We have reported this to RefWorks and hope to have it fixed soon.