emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: contributing to work on citations
Date: Fri, 30 Oct 2015 16:17:43 -0400	[thread overview]
Message-ID: <CAN_Dec8=0JaNP5arcwrSQCvq7dWvXCPCz2Cu13FHL7T-kzg8qA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2356 bytes --]

next             reply	other threads:[~2015-10-30 20:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 20:17 Matt Price [this message]
2015-11-04 15:18 ` contributing to work on citations Aaron Ecay
2015-11-04 19:37   ` Will Monroe
2015-11-04 19:49     ` William Denton
2015-11-04 20:20     ` John Wiegley
2015-11-04 22:25   ` Matt Price
2015-11-06  1:41   ` Matt Price
2015-11-06 13:10     ` Aaron Ecay
2015-11-06 17:14       ` Matt Price
2015-11-22 20:32         ` Richard Lawrence
2015-11-08 11:17     ` Rasmus

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='CAN_Dec8=0JaNP5arcwrSQCvq7dWvXCPCz2Cu13FHL7T-kzg8qA@mail.gmail.com' \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@gnu.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

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).