most urgent features/fixes
UNDO FUNCTION
An essential addition of all pieces of software nowadays. Still reverting a small bad step is a piece of work with zotero.
DUPLICATE DETECTION
This basic piece of database maintenance is still missing. Ideally the zotero import button would be changed if a certain item has already been imported, similar to the bookmarking star of Firefox. Short of that, a database check before an item being imported is added to the database.
FIX TAG WARNING BUG
When syncing the database, I often get several dozen error message like "tag XYZ has been removed/added..". I import from PubMed, so items have MeSH keywords. The error messages appear despite no manual manipulation of keywords and every single one of them has to be confirmed manually by clicking ok. Ufff. A huge waste of time when you get say 50 after a huge addition to the database and if you want the sync to run, you'll have to click through 15min of error messages. Short of fixing this, we at least need an accept all button.
An essential addition of all pieces of software nowadays. Still reverting a small bad step is a piece of work with zotero.
DUPLICATE DETECTION
This basic piece of database maintenance is still missing. Ideally the zotero import button would be changed if a certain item has already been imported, similar to the bookmarking star of Firefox. Short of that, a database check before an item being imported is added to the database.
FIX TAG WARNING BUG
When syncing the database, I often get several dozen error message like "tag XYZ has been removed/added..". I import from PubMed, so items have MeSH keywords. The error messages appear despite no manual manipulation of keywords and every single one of them has to be confirmed manually by clicking ok. Ufff. A huge waste of time when you get say 50 after a huge addition to the database and if you want the sync to run, you'll have to click through 15min of error messages. Short of fixing this, we at least need an accept all button.
DUPLICATE DETECTION: See also http://forums.zotero.org/discussion/42/2/duplicate-detection/
TRACK CHANGES: See also http://forums.zotero.org/discussion/10210
Alternatively to the Document.TrackRevisions property, one could also use the Range.Revisions.AcceptAll method. I suggest the behavior should be controlled by a setting in General or Plugin Preferences "Suppress Track-Changes in MS Word during Zotero Refresh" and defaulted to Yes.
Could someone (Simon?) create a ticket for the TRACK-CHANGES feature?