RefWorks is listening, blogs work

Blogs do have an impact. After the posting of (y)our wish list we got reaction form RefWorks stating that the list had been passed on to RefWorks developers. It is very likely that at least a few of the issues mentioned in the list will be solved in the next major update expected this summer. So keep sending in your feedback, by mail (j.bosman [at] uu.nl) or by commenting on the posts here. You can also join in and ask for a password to post directly.

RefWorks wish list

OK, RefWorks is a nice tool, very nice in some ways, but ideal? No, not yet. Over the weeks and months I have collected things that could make RefWorks better. That wish list is below. Some wishes are very general, benefitting lots of users, others are targeted to special purposes. By commenting on this post you can add your wishes. RefWorks is reading this blog as well, so perhaps they'll pick some of these points up for a new release.

1. Better customizability of the list view (user fields, link to local file, option to add colums to the list view irrespective of output styles)
2. Stop the overload of confirmation messages ("successfully moved 1 item to antoher folder" etc.). It slows the workflow.
3. Fully shared folders, allowing for multiple editors of a folder and allowing folders to be part of several databases.
4. Find and replace functionality (for any string, across the database). This allows easy correction.
5. Create an output style that lists all information in the records (however incomplete that might be for some records)
6. Easier linking to local files (on hardrives or portable drives)
7. Faster operation by use of modern web technologies such as Ajax etc, making it possible to change pages without reloading them. This would be nice for instance for showing/hiding abstracts (more or less as implemented in Scopus).
8. Easier editing of page numbers in citations
9. ....[your ideas]