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?"

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.

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.

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.

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.

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.

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.

It saves a lot of time when input a some very similar references.

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.

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

Fix the problem diacritic characters. It was promised last year but still é or ä etc. have to be corrected manually.

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.

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,

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?

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.

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).

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.

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,

Enable deduplication of larger numbers of references than is currently possible