Problems exporting to RefWorks from DISCOVER, EBSCOhost databases and Ovid journals

RefWorks are experiencing problems at the moment with people importing records into RefWorks from DISCOVER/EBSCOhost databases and from ejournals on the Ovid platform (with ovidsp.ovid.com in the URL). RefWorks, EBSCO and Ovid are working to fix this but in the meantime have advised users to export a RIS file and then follow this procedure:

To import the exported references into (new) RefWorks:

• Select the + sign and then select Import references.
• Under the heading "Import from a file" drag and drop or select the file generated by the export.
• The system will try to determine the format; if it does not identify the RIS Format select it from the drop down and click import.
• The data will show up in the last imported area.

To import the exported references into legacy RefWorks:

•         Select the reference tab on the main page, then select import.

•         At this point you will see a drop down menu labeled Import Filter/Data Source, scroll down to RIS Format.

•         In the drop down menu labeled Database select RIS Format.

•         You can also select the folder you wish to have the references imported to.

•         Then browse for the .txt file the data is stored in and select import.

•         You should be able to view your references in either last imported or in the folder you selected.

RefWorks via the library catalogue - change for Legacy RefWorks users

We have made a slight change to the way you access Legacy RefWorks through the library catalogue.
When you search for "refworks", instead of seeing results for Legacy RefWorks and RefWorks, there will only be one result, which now contains links out to both versions.

A reminder - all new RefWorks users are using the current version, which looks like this:

Legacy RefWorks is the previous version, which looks like this:

If you have been using RefWorks for some time you may be using the version, and it's up to you whether you switch to the new version, or continue with Legacy.

RefWorks downtime 20th December 6am - 4pm GMT

RefWorks are moving to a new server on 20th of December and are warning of up to 10 hours of downtime for both RefWorks and Legacy RefWorks. RefWorks Citation Manager and Write-n-Cite will also be unavailable during this time.

RefWorks video guide - exporting references to RefWorks

RefWorks have produced a quick YouTube guide to exporting references. It's not specific to University of Bedfordshire, but you may find it useful

New RefWorks and Legacy RefWorks - change in terminology

Since we introduced the new version of RefWorks in 2017, we have been calling it "New RefWorks", and the previous version Old RefWorks, or just RefWorks. We have now decided to make it more clear that the new version is our default, and the old version just for people who have been using it a long time and don't want to switch. Therefore, we will now be referring to the new version as "RefWorks", and the old version as "Legacy RefWorks", both on the library catalogue and our website.

If you are unsure which you are using, this is the current version:

and this is the Legacy version:

RefWorks downtime Sunday 24th March 11am-4pm

We've been warned of scheduled downtime for both versions of RefWorks between 11am and 4pm on Sunday 24th March.

During this window legacy RefWorks and new RefWorks will be unavailable. RefWorks Citation Manager and the RefWorks GoogleDocs plug-in will not be available. Write-n-Cite will be available offline, but users will not be able to sync their references with RefWorks.

All existing references will be maintained and available at the end of the maintenance window.

New RefWorks downtime Friday 22nd February 11pm-3am

We are expecting scheduled maintenance to New RefWorks from 11pm on Friday 22nd February to 3am on Saturday 23rd.

During this window New RefWorks will be offline. Write-n-Cite will be available offline, but you will not be able to sync your references with RefWorks.

All existing references will be maintained and available at the end of the maintenance window.