Duplicate Citations in Word - how to remove?
Hello,
would be nice if it was possible to remove duplicate citations that were inserted into a single Word document by two different authors from two different libraries.
Here is what happens ... I merge two texts prepared by two people, each inserted the same citation but from different libraries ... there might even be a small difference between the citations, such as some fields missing. Those two citations would be clearly picked as duplicates in standalone Zotero and you could merge them ... but when these are inserted into a text they would show up as (Jones et al, 2006a and Jones et al, 2006b). It is always quite a lot of pain to get rid of this. Any solutions, ideas??
Thanks!
Best,
Marek
would be nice if it was possible to remove duplicate citations that were inserted into a single Word document by two different authors from two different libraries.
Here is what happens ... I merge two texts prepared by two people, each inserted the same citation but from different libraries ... there might even be a small difference between the citations, such as some fields missing. Those two citations would be clearly picked as duplicates in standalone Zotero and you could merge them ... but when these are inserted into a text they would show up as (Jones et al, 2006a and Jones et al, 2006b). It is always quite a lot of pain to get rid of this. Any solutions, ideas??
Thanks!
Best,
Marek
1. Use Fields and make sure to check the "Save references in document" box. That way, when citing, a box will come up with papers already cited. If you select from there Z will use that one, corresponding to the item added by whoever added it first.
2. Use a Group library to share references and cite only from that group library.
Would be nice if the same "Find duplicates" that Standalone Zotero has was implemented in the Word plug-in.
I could absolutely see an option to "merge" two items in a document. That would also help with orphaned references (instead of replacing them all, you could insert a new one once and then merge that with the orphan).
None of this seems super complex programmatically, but the GUI/UX issues are non-trivial and I wouldn't expect this to be super high priority. But certainly nice to have.
Again -- none of this is somehow prohibitively hard, but it needs some actual attention, not just a 20min flip-the-switch