ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <gnwiii@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Bibliographic Databases
Date: Sat, 19 Apr 2008 16:21:05 -0300	[thread overview]
Message-ID: <22af238a0804191221w31c40557r9c9ada2474fa340@mail.gmail.com> (raw)
In-Reply-To: <28FFA564-77A6-41BE-8E15-F8345C904E76@csiro.au>

On Thu, Apr 17, 2008 at 11:19 AM, Robin Kirkham <robin.kirkham@csiro.au> wrote:

> Dear all,
>
>  I want to set up a shared bibliographic reference database for my
>  research group, and I'm looking at software like refbase http://
>  refbase.sourceforge.net/ or refdb http://refdb.sourceforge.net/ to
>  replace the somewhat random collection of personal BibTeX .bib files
>  we have.
>
>  Does anyone have any experience or advice to offer in using such
>  things, and hooking them up to ConTeXt?  Most of these systems will
>  of course emit a .bib file which will obviously work, but will any
>  emit the .bbl so I can forget about BibTeX?  Will luatex one day
>  connect to a bib database and fetch the details of a cited
>  reference?  Is there a ConTeXt "approved" way forward for this sort
>  of thing?

I can tell you a few things that don't work!  In our lab we have both
TeX and Word users.  Many of them had been using a DOS package
called papyrus, using a special markup that could be translated
to tex (.bbl) files.  Nothing we found was really satisfactory, so
we bought EndNote, which could import from papyrus via "refer"
format and can export to "almost bibtex".  One problem is that
EndNote uses unicode, so we end up with è, etc. that must
be translated for some user's versions of bibtex.  The database
now has a nearly infinite variety of different quote marks:
`a`, 'a', ``a'', "a", etc. depending on how the entry was made
(many are pasted from online or pdf sources).

EndNote is really designed for individual users, although sold
in bulk.  If 2 people open the same database on a shared
drive they end up with a corrupt database.

In my view, a bibliographic database needs to store each
reference in the "source" or original format, whether bibtex,
refer, or one of the newer forms, and provide translators
and version tracking, so each file can have forks for different
uses (e.g., ascii vs unicode char. sets) and edits can be
preserved for the next user.  In practice, people just dump
selected refs to a bib file, make the .bbl file, and fix problems
there, so fixes rarely make it back to the master database.
If they did, we would still have accents and quote marks
being switched back and forth depending on who last used
the entry.


-- 
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-04-19 19:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 14:19 Robin Kirkham
2008-04-17 19:10 ` Andreas Wagner
2008-04-18  8:08 ` Taco Hoekwater
2008-04-18  8:15   ` Wolfgang Schuster
2008-04-18 15:17   ` Andreas Wagner
2008-04-18 17:46     ` Taco Hoekwater
2008-04-18 23:23       ` Andreas Wagner
2008-04-20 14:35       ` Bruce D'Arcus
2008-04-20 14:52       ` Bruce D\'Arcus
2008-04-19 19:21 ` George N. White III [this message]
2008-04-20  9:13 Robin Kirkham
     [not found] <mailman.0.1208685601.23025.ntg-context@ntg.nl>
2008-04-21 12:03 ` Dietrich Rordorf / MDPI

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22af238a0804191221w31c40557r9c9ada2474fa340@mail.gmail.com \
    --to=gnwiii@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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.
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 NNTP newsgroup(s).