If not, could you please consider making some (less important) fields available in all item type (e.g. archive, archive location, library catalogue, call number) so we can use these as custom fields?
Just hoping for custom columns/fields in Zotero sometime! For myself I would like to record both the date added to Zotero (which is already present) and the date I actually read the paper (in the custom column). "Date Modified" is also already present, but if I ever make any changes to the notes on a paper (which I do) then that throws this out the window...
FYI, I already use the "Extra" column for other purposes. Why just not have Extra1, Extra2, Extra3, Extra4, Extra5? A little clumsy but would be seriously helpful.
Translated title (usually the translation into English of a title in another language, required by English-language journals). Non-English abstract (the abstract in a language other than English when the English abstract is algo given) Translated author (transliteration, to be able to use either the author's Latin or non Latin name according to journal requirements) M/F (to register author's gender and analyze bias) Author address (email and affiliation for authos) Author OrcID Special issue title (in addition to series) Publisher address
I work with eighteenth-century books, many of which were published anonymously but for some of which the author was later determined. I need a custom field to indicate that authorship was attributed at some later date (Zotero doesn't play well with the standard convention for indicating attributed authorship, namely surrounding the author's name with square brackets).
Especially emonzo's suggestion of Translated title and Translated author fields!
Edit. Also Translitered title, Translated publication, Translated publisher, Translated Place. I write in three languages and now I have to create separate items for at least Japanese and English/Finnish, sometimes even all of them.
Would a custom field even help much for that? The citation processor (as it stands today) doesn't know what to do with non-standard fields, so it will ignore them.
Is there a good reason the keys in Extra’s key-value pairs must be valid CSL fields?
If that limitation were removed, these key-value pairs would effectively be custom fields, and custom CSL could access the keyed values just as it accesses DOI now. No?
My proposal for general key-value pairs wouldn’t offer everything we’d want from a user-interface standpoint, but it would allow us to store values and include them in citations and bibliographies.
@bwiernik, that is the case with conforming and portable CSL. But where is that enforced? Does citeproc really require it?
The style editor does not stop me from including in my custom CSL, say, <text variable="special1"/> Neither Zotero nor citeproc crash.
I assume citeproc looks in some associative array, finds no key, and happily keeps going. I doubt it even logs a warning. If it had found a value for that key, would it not have output that value?
Some code is parsing the key-value pairs in Extra and checking that the keys are CSL fields. What if that check was simply not performed?
Would I not then be able to write a local, custom CSL that uses my local, custom key-value pair?
Upgrade Storage
If not, could you please consider making some (less important) fields available in all item type (e.g. archive, archive location, library catalogue, call number) so we can use these as custom fields?
FYI, I already use the "Extra" column for other purposes. Why just not have Extra1, Extra2, Extra3, Extra4, Extra5? A little clumsy but would be seriously helpful.
Translated title (usually the translation into English of a title in another language, required by English-language journals).
Non-English abstract (the abstract in a language other than English when the English abstract is algo given)
Translated author (transliteration, to be able to use either the author's Latin or non Latin name according to journal requirements)
M/F (to register author's gender and analyze bias)
Author address (email and affiliation for authos)
Author OrcID
Special issue title (in addition to series)
Publisher address
I work with eighteenth-century books, many of which were published anonymously but for some of which the author was later determined. I need a custom field to indicate that authorship was attributed at some later date (Zotero doesn't play well with the standard convention for indicating attributed authorship, namely surrounding the author's name with square brackets).
Especially emonzo's suggestion of Translated title and Translated author fields!
Edit. Also Translitered title, Translated publication, Translated publisher, Translated Place. I write in three languages and now I have to create separate items for at least Japanese and English/Finnish, sometimes even all of them.
If that limitation were removed, these key-value pairs would effectively be custom fields, and custom CSL could access the keyed values just as it accesses DOI now. No?
Also, and Added By field so I can see who added the source would help me out a lot.
And I am guessing it would be easy to code in.
The style editor does not stop me from including in my custom CSL, say,
<text variable="special1"/> Neither Zotero nor citeproc crash.
I assume citeproc looks in some associative array, finds no key, and happily keeps going. I doubt it even logs a warning. If it had found a value for that key, would it not have output that value?
Some code is parsing the key-value pairs in Extra and checking that the keys are CSL fields. What if that check was simply not performed?
Would I not then be able to write a local, custom CSL that uses my local, custom key-value pair?
pleasethankyou ;)
tex.title=...to theextrafield if you have the better bibtex plugin.