retain bibtex key
I noticed that the bibtex key is not imported. When the database is exported to bibtex keys are generated from the title and the year. This does not match with tex documents I have written before and is rather annoying.
It would be nice if the bibtex key were stored and used while exporting.
It would be nice if the bibtex key were stored and used while exporting.
(Even a subset of this would be nice: ability to customize how the "key" is created.)
Thanks for considering this.
It would be useful to have fields like "personal signature". Here could be the right place to store the bibtex-key from imported bib-files.
The topic of the other discussion is more about some other missing field. I wouldn't mix them together.
And I wouldn't like to introduce a workaround for a really important feature - in longterm view the bibtex-key is neccessary for the seamless integration.
Thanks a lot!
Edit: It is also discussed in http://forums.zotero.org/discussion/4331/bibtex-importexport-problems/
In the moment the only way i found is to export the bib, open it in a text editor, search for the entry (sometimes over 100 entries for me), copy it, paste it into latex. Zotero wants to be fast. But this is very, very slow :-/
Thanks
Stolzi
https://www.zotero.org/trac/ticket/763
The current version is 2.09 and frankly this is the only feature that is stopping me from using Zotero.
Notes and tags are also user data though. Either one: so long as the distinction is crystal clear from bottom (data layer) to top (the UI the user sees).
I guess to put this differently, the "repository" field itself is a bit odd. Really what you want to say is user-specific is the zero-or-more copies of the item content available to the user. Each of those copies comes from someplace, which is what the "repository" idea gets at.
Someone describes how to do this here: http://www.curiousjason.com/zoterotobibtex.html
The mask for BibTeX-key-creation is stored in a JavaScript-variable in the user profile. This may very likely get overwritten in an update of Zotero, so the described solution is really just a workaround.
But if it is just the matter of setting a variable, it should be pretty easy to implement the possibility to enter the value of this variable in the Zotero preferences, which would make the change update persistent.
Ideally a solution for me would look like this:
*) An additional field for the bibtex key which is editable by the user. It is irrelevant for me where exactly it's located as long as it's there.
*) If I import data without bibtex keys, allow me to have keys autogenerated.
*) If I export data without bibtex keys, allow me to have keys autogenerated.
*) In addition provide an option to autogenerate bibtex keys for selected items (with the option of overwriting existing keys or not). This would cover already existing collections.
The generation of keys can be customized just like now via the existing javascript code. Keys for which generation did not work well (e.g. currently "Börger" will be coded as "baerger" in a generated key, though it should be "boerger") can always be corrected manually.
So a user could maintain his bibtex keys with minimal effort.
This would make the Zotero - LaTeX workflow so much easier.
But, considering that this issue has been open since 2007, I don't have much hope that a solution is going to be implemented in the near future.
it would be a great implementation for mindmap and latex users.