RefWorks
Your feedback matters to us. Help us improve RefWorks by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines.
For Support related issues please use this form.
Thank you.
-
Warning that a reference is already in Refworks when import it
I would be great, if Refworks detects duplicates while I import references. RefWorks could ask: "This is already in your RefWorks database. Do you want to import it anyway?"
126 votesI am happy to update this idea has been moved to Planned and is part of the 2021 roadmap.
-
Don't automatically import subject headings as tags
Subject headings from Proquest and other databases are automatically imported as "tags." This clutters up the interface, and makes it hard for users to add their own tags.
71 votesI am happy to update that the RefWorks October release includes a user setting to hide tags (and folders) when viewing references in Normal and Full Views, under a new Customize button. This cleans up the view and allows seeing more references on a page. This is an initial step in handling tags; not automatically importing headings as tags will be another step.
-
Be able to restructure folders more easily
Currently, folder structure is set once created and cannot be modified without recreating and deleting folders. It would be great to be able to click and drag folders so that if we decided to make one folder into a subfolder, or make a subfolder into a main folder, we could click and drag it in/ out without having to create a new folder structure, move/ reassign all the references over, and then delete the previous folder structure.
66 votesI am happy to update this idea has been moved to Planned and is part of the 2021 roadmap.
-
Save to Refworks button is not functional
The save to refworks button for chrome is not functional. About 90% of the time when I try to use it and input all the information, the loading bar goes and goes (Uploading 1 of 1.......) and eventually after about a minute it says it was unable to import anything (We're sorry, we were unable to save to RefWorks. We tried, but came up empty.) So frustrating. As said before, this service is great, but quite a few basic functionalities are from from actually functioning properly. These need to be fixed. A quick import button is a huge draw of…
56 votesImprovements to the Save to RefWorks button are planned for the coming year.
-
WAYFless URL to access RefWorks 3 directly without using login page.
We would need a WAYFless URL to RefWorks 3. In our workflows users want to go directly to RefWorks 3 from within other applications. The route to go to the login page is not needed with a WAYFLess URL. Haveing requested this already three years ago nothing seems to have happened. Frustrating.
55 votesI am happy to update this idea has been moved to Planned and is part of the 2021 roadmap.
-
Provide administrator the ability to make and edit "Role" and "Institution" options.
Currently, administrator can not make and edit options for "Role" and "Institutions" which is selected when user create their accounts. This makes it inconvenient for administrator to manage their user and usage stats.
54 votesI’m happy to update that this idea now has the status Planned, as it will be addressed in 2020.
-
Export Tags
It is essential that RefWorks export "tag" metadata in its various export formats. I have been using RefWorks for years but am discontinuing my use of your product until tag data is exportable. Tag metadata is some of the most valuable data in the library of citations that I have amassed over the past four years, and because it is not currently exportable, it feels as if ProQuest is holding my data hostage. Exportable metadata is not merely a perk to be added to your service; it is a MAJOR structural flaw that needs to be addressed.
52 votesI am happy to update that this item is now in Planned status and is part of the 2020 roadmap.
-
Make it possible to add the RefID to an export or to a custom style
We would like to export from New RefWorks with a RefID included. At this moment, the default export options don't include the RefID and it's not possible to add the field RefID to a custom style.
Use case: two researchers have to look at the literature for a systematic review and decide on inclusion or exclusion. They want to have a list in Excel with title and abstract and RefID to make it easier to compare and clean their list afterwards. This is possible in Legacy RefWorks, but not in New/ProQuest RefWorks.
45 votesI am happy to update this idea has been moved to Planned and is part of the 2021 roadmap.
-
I miss a lot from refworks legacy the feature of "duplicate a reference"
It saves a lot of time when input a some very similar references.
32 votesI am happy to update this idea has been moved to Planned and is part of the 2021 roadmap.
-
data-driven article recommendations
There is a demand for data-driven article recommendation function for RefWorks.
Some kind of web services have already implemented this kind of function.
One end-user said that it should be based on not only articles in user account but also references cited in those articles. I hope this idea to be considered.24 votesI’m happy to update that this idea now has the status Planned, as it will be addressed in 2020.
-
Show all fields included in a resource type on the edit screen
Currently RefWorks only shows certain fields when you edit references, it would be better if it showed all fields for that type of resource that are defined in the style
21 votesThis feature is planned for a later 2019 release.
-
Diacritic characters
Fix the problem diacritic characters. It was promised last year but still é or ä etc. have to be corrected manually.
9 votesLanguage Support for Diacritics is currently under development. We are also including some work on Glyphs.
-
ISBN/ISSN, authors can be used to retrieve auto-cite metadata for manual input
More criteria are recommended for retrieving metadata for auto-cite. ISBN, ISSN and authors are common. This will empower the auto-cite capability and save a lot of time for the researchers.
9 votesI am happy to update this idea has been moved to Planned and is part of the 2021 roadmap. We will support reference matching by ISSN and ISBN (in addition to Title and DOI which are currently supported)
-
Integrate with Primo
Provide a easy way for the user to search for relevant resources in his library discovery tool from inside RefWorks.
For customers that use Primo as their library discovery,8 votesThis will be part of our second half of the year work on API integrations.
-
Multiple URLs on record import - separate? or block
Records can't support two links in the URL field, but mutliple URLS on import are all placed there. Some databases (Ovid) allow inclusion of either the "permalink" record URL and/or the external link resolver (full text). When the records are in Refworks, neither link works because they are in one URL field with a space separating them. It would be great if RW could support multiple links for a record (via import) but if not, then perhaps block on space or on the next "http" found?
7 votesWe plan to address this issue in the coming months.
-
RefWorks API documentation
We urgently need to see the API documentation for ProQuest RefWorks so that we can create our own export function for our library catalogue (Koha).
The 'Save to RefWorks' button does not work for Koha so we have no option other than to create our own embedded export feature. Our developers cannot do this without the API documentation.
6 votesI am happy to update this idea has been moved to Planned and is part of the 2021 roadmap.
-
Offer Sensitive and Specific deduplication algorithms instead of New and Legacy
New RefWorks presently offers a choice of two deduplication algorithms that work differently. They find comparable numbers of duplicates, but they do not find the same duplicates. Users have to run both algorithms to find the maximum number of duplicates.
Users would be better off if the choices were between a high-sensitivity search (flag any duplicate picked up by either algorithm) and a high-specificity search (flag only those duplicates picked up by both algorithms).
6 votesI am happy to update that this item is now in Planned status and is part of the 2020 roadmap.
-
Please make it possible to move large numbers of references from the last import page to a folder, all at once
I have just imported 7600 references that I want to put all into the same folder (working on a systematic review). I can only move small quantities at a time as the select all features is limited to the records displayed. Selecting "display 2000 records" causes refworks to crash.
4 votesI am happy to update that this item is now in Planned status. Handling large numbers of references is part of the 2020 roadmap.
-
Integrate with Summon
Be able to search Summon from inside RefWorks' "Search Databases"
Provide a easy way for the user to search for relevant resources in his library discovery tool from inside RefWorks.
For customers that use Summon as their library discovery,4 votesWe have this planned for the 2nd half of the year, but there is not a definitely timetable yet.
-
Deduplicate more than 2000 references simultaneously
Enable deduplication of larger numbers of references than is currently possible
4 votesIncreasing the number of references that can be deduplicated simultaneously is planned for 2020.
- Don't see your idea?