On Apr 4, 2006, at 3:46 PM, Matt Price wrote:
Seems to me it would be useful to define several targets --
say "minimal", "intermediate", and "polished" and lay out what needs to
be done for each.
Sure.
Minimal Bibliographic Interface
Target Goals: Allow expert users to insert useful citations by (a)
creating durable citation infrastructure within sw; (b) designing a new
bibliographic database structure; (c) creating a minimal interface
which
uses citeproc to link (a) and (b).
Obviously missing functionality: aiblity to create and modify database
directly within OOo. It is a ssumed that database management per se
will take place through an existing interface (endnote, bibus, or the
like) and be funnelled through some kind of filter to produce a native
bibliography.
I'm a little confused here. I would say "minimal" support might be able
to throw out the database altogether and provide an API to plug-in
different reference management solutions.
Is that what you are saying, or are you saying that database management
should be part of this minimal support?
So for me the different levels would support:
minimal
========
1) new citation coding
2) formatting processing via citeproc (or equivalent)
3) API for third-party access (inserting citations)
intermediate
============
adds:
4) local database
5) full new editing GUI for 4
advanced
========
adds:
6) more advanced remote functionality (ZOOM; though this might relate
to 3 above, and probably should)
Tasks:
(1) Modify the sw code to enable citation data to be saved and
displayed, to making citations avialable by UNO hooks. (these are CPH's
'1-4' of an earlier post.) Assigned to CPH.
(2) Complete design of database. Not assigned
(3) port Citeproc to python. Not assigned.
---------
1-3 can be worked on simultaneously and starting from now, I reckon.
---------
Correct. One thing we have to decide now is the relationship between
data and formatting. If the data source for formatting is embedded
XML/RDF, then the database per se becomes less critical.
[note: I see you just posted something on this Matt; will probably
respond there]
(4) build filters to generate database records and xml/rdf metadata
records from MODS datasets. THis might be conceived as an extension to
bibutils?
Yeah, and I might be able to see if Chris can help us on that.
However, I'd put the above slightly differently in that "MODS datasets"
are one possible input format. By using something like bibutils, we
also get support for RIS, Refer/Endnote, BibTeX, etc.
(5) build a UNO application that provides a graphic user interface to
the bibliographic data, allowing insertion and (per-document)
formatting
of citation data). This involves
...?
---------
4 will probably be tricky in its particulars but it might be possible
to
get something basic off the ground quite quickly.
5 seems to me a good candidate for a Summer Of Code or other ambitious
programming project.
Yes.
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
