From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Price Subject: contributing to work on citations Date: Fri, 30 Oct 2015 16:17:43 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113f9ae0c2d2430523581ebe Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZsG7R-00033C-9e for emacs-orgmode@gnu.org; Fri, 30 Oct 2015 16:17:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZsG7M-0004b1-M9 for emacs-orgmode@gnu.org; Fri, 30 Oct 2015 16:17:49 -0400 Received: from mail-io0-x231.google.com ([2607:f8b0:4001:c06::231]:35894) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZsG7M-0004aq-GF for emacs-orgmode@gnu.org; Fri, 30 Oct 2015 16:17:44 -0400 Received: by ioll68 with SMTP id l68so92300755iol.3 for ; Fri, 30 Oct 2015 13:17:43 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode --001a113f9ae0c2d2430523581ebe Content-Type: text/plain; charset=UTF-8 So, from the "some projects" thread I have the sense there is a group of users with some interest in improving citation support. What is the best way to kickstart that process? it seems to me that, at a minimum, the following is needed: 1. Finalization of the citation syntax. IIUC, This involves refining and merging the work in the wip-cite git branch. 2. Choice of a citation creation tool IIUC, the two main candidates are pandoc-citeproc and citeproc-js/node. Pandoc-citeproc works well but requires users to install the whole pandoc infrastructure, and needs to be wrapped in a thin tool for use with org. Citeproc-node has fewer dependencies (I guess), but needs to be updated to support additional output formats (e.g. latex, odt, and org) and is a little more elaborate to run from the command line (runs as a service, can only be communicated with over http). 3. Handling of citation links in the various export engines Functions must be written to handle citations in, at minimum, latex, html, and org 4. Interface with backends Org should be able to talk to bibtex and zotero databases, at least (and maybe more). A lot of this work has already been done. Richard has written org-citeproc as a wrapper for pandoc-citeproc https://github.com/wyleyr/org-citeproc . Aaron has written some functions for org-citeproc in the wip-cite-awe branch. Nicolas has developed the syntax in wip-cite. I even have a fork of citeproc-node that could be used to develop the missing features we need. And of course John has org-ref ( http://kitchingroup.cheme.cmu.edu/blog/2014/05/13/Using-org-ref-for-citations-and-references/) while Erik H has zotxt-emacs for Zotero integration ( https://github.com/egh/zotxt-emacs). What would be the best next move? It seems to me there are enough moving parts that the process will be quite a bit easier if we co-ordinate. thanks, Matt --001a113f9ae0c2d2430523581ebe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
So, from the "some projects" thread I = have the sense there is a group of users with some interest in improving ci= tation support. What is the best way to kickstart that process? it seems to= me that, at a minimum, the following is needed:

1. Finalizati= on of the citation syntax.

IIUC, This involves refining = and merging the work in the wip-cite git branch.

2. Choic= e of a citation creation tool

IIUC, the two main candidat= es are pandoc-citeproc and citeproc-js/node.=C2=A0 Pandoc-citeproc works we= ll but requires users to install the whole pandoc infrastructure, and needs= to be wrapped in a thin tool for use with org.=C2=A0 Citeproc-node has few= er dependencies (I guess), but needs to be updated to support additional ou= tput formats (e.g. latex, odt, and org) and is a little more elaborate to r= un from the command line (runs as a service, can only be communicated with = over http).

3. Handling of citation links in the various= export engines
Functions must be written to handle citations= in, at minimum, latex, html, and org

4. Interface with b= ackends
Org should be able to talk to bibtex and zotero datab= ases, at least (and maybe more).=C2=A0

A lot of this wor= k has already been done. Richard has written org-citeproc as a wrapper for = pandoc-citeproc https://github.com/wyleyr/org-citeproc . Aaron has written = some functions for org-citeproc in the wip-cite-awe branch. Nicolas has dev= eloped the syntax in wip-cite. I even have a fork of citeproc-node that cou= ld be used to develop the missing features we need.=C2=A0 And of course Joh= n has org-ref (http://kitchingroup.cheme.cmu= .edu/blog/2014/05/13/Using-org-ref-for-citations-and-references/) while= Erik H has zotxt-emacs for Zotero integration (https://github.com/egh/zotxt-emacs).

=
What would be the best next move? It seems to me there are enough movi= ng parts that the process will be quite a bit easier if we co-ordinate.
=
thanks,
Matt
--001a113f9ae0c2d2430523581ebe--