From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Matt Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org, "Martin Yrjölä" <martin.yrjola@gmail.com>
Subject: Re: Citation processing via Zotero + zotxt
Date: Thu, 03 Dec 2015 18:31:14 -0500 [thread overview]
Message-ID: <m2y4dbgldp.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <8737vkidgl.fsf@fastmail.fm>
I clearly had some super important academic work to do today, so instead
I played around with citations ;)
I am not yet convinced a citation processor will get us where we want
because of the complexity of the external dependencies, and the
potential/probable need for us to define new CSL files for different
backends, or at a minimum for org-formatted citations and
bibliographies. Hacking bst files is no fun, and it doesn't look like
CSL files are much better! Plus you have to find them and install them
somehow.
I wanted to get a sense for how well I could manipulate citation and
bibliography format from org-ref with a bibtex database. The answer is
it is pretty easy, not perfect, but pretty good, and could certainly be
made better with dedicated effort. You can see how here, and some
discussion about its limitations:
http://kitchingroup.cheme.cmu.edu/blog/2015/12/03/Exporting-numbered-citations-in-html-with-unsorted-numbered-bibliography/
I am pointing this out because I think the approach I used could allow
for plugins for different database backends, different ways to get the
replacements, etc... you could substitute org-ref links for the citation
syntax at some point with no real loss of generality. org-ref could
insert the new syntax as soon as it is available in a main org branch.
Some code will have to be rewritten to get the key under point, but that
probably won't be too hard.
We could provide a solution like this for some backends, using bibtex as
the database, for pretty immediate use. Then other more advanced
solutions could come along that would likely be superior in output
quality if they use real citation processors, but only if there are CSLs
for different backends (if I understand how they work). These would be
optional, and only needed if higher quality and flexibility in output
was required.
What do you think?
Matt Lundin writes:
> Richard Lawrence <richard.lawrence@berkeley.edu> writes:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>>> 2. How would I use this starting from an org-bibtex database (which I
>>> typically export to bibtex)?
>>
>> I can envision a couple of possibilities. One simple option would be to
>> switch to managing your reference database with Zotero, by exporting
>> from org-bibtex to .bib, and then importing the .bib into Zotero.
>>
>> I don't want to force that on anyone, though. Another option is to
>> use the org-bibtex to produce .bib at export time, and then use Zotero
>> to read the .bib and process citations when exporting to non-LaTeX formats.
>>
>> This second option is more work, as I don't know of any API for loading
>> items into Zotero's citation processor in BibTeX format. But given that
>> Zotero is able to import .bib files, I imagine this API would not be too
>> much work to build.
>
> Given these complexities, it seems that if we went the zotero route we
> could end up with a fairly large installation chain (firefox, zotero,
> zotxt, plugin for zotero). And this would require installing items from
> multiple, heterogeneous sources.
>
> I wonder at this point whether pandoc-citeproc (packaged with pandoc)
> would actually be the simpler route. It can parse bibtex files directly
> and (as a filter within pandoc) can output formatted citations in org
> format.
>
> As a GNU/Linux user, I would find installing zotero and all the add-ons
> messier and more cumbersome than installing pandoc and/or node-js (were
> we to use citeproc-js) from the command line.
>
> Best,
> Matt
>
> Footnotes:
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-12-03 23:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 20:16 Citation processing via Zotero + zotxt Richard Lawrence
2015-11-30 8:12 ` Martin Yrjölä
2015-12-01 0:32 ` John Kitchin
2015-12-01 2:59 ` Richard Lawrence
2015-12-03 0:27 ` Matt Lundin
2015-12-03 1:41 ` Christian Wittern
2015-12-03 14:25 ` Matt Lundin
2015-12-03 4:32 ` Richard Lawrence
2015-12-03 15:27 ` Matt Lundin
2015-12-03 17:56 ` Richard Lawrence
2015-12-03 19:14 ` Thomas S. Dye
2015-12-03 22:05 ` Rasmus
2015-12-03 20:45 ` Matt Lundin
2015-12-03 21:04 ` Matt Lundin
2015-12-03 23:31 ` John Kitchin [this message]
2015-12-04 0:03 ` Rasmus
2015-12-04 1:49 ` John Kitchin
2015-12-05 21:18 ` Matt Lundin
2015-12-05 22:23 ` John Kitchin
2015-12-04 2:06 ` Matt Lundin
2015-12-04 11:22 ` John Kitchin
2015-12-04 14:13 ` Matt Lundin
2015-12-05 1:23 ` John Kitchin
2015-12-04 9:20 ` Eric S Fraga
2015-12-01 9:34 ` Ramon Diaz-Uriarte
2015-11-30 11:35 ` Eric S Fraga
2015-11-30 12:02 ` Ramon Diaz-Uriarte
[not found] ` <CAN_Dec-JCmwQ2bc=U93rRaPMYyXOiN_PRbtyya9x396r3qqMrg@mail.gmail.com>
2015-12-01 12:12 ` Fwd: " Matt Price
2015-12-01 15:28 ` Eric S Fraga
2015-12-01 15:51 ` Richard Lawrence
2015-12-01 19:20 ` Matt Price
2015-12-01 21:34 ` Eric S Fraga
2015-12-01 21:51 ` Matt Lundin
2015-12-02 15:21 ` Richard Lawrence
2015-12-01 14:36 ` Rasmus
2015-12-01 19:37 ` Matt Price
2015-12-02 15:58 ` Richard Lawrence
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y4dbgldp.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=martin.yrjola@gmail.com \
--cc=mdl@imapmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).