Gannon,
The bibliographic project team decide against basing the new
bibliographic
application on an SQL database some time ago. I do not want to repeat the
issues here, after all, they are all in the archives of this list.
The new bibliographic application will be XML based rather than SQL based. An
SQL interface may built at some stage but it not a first priority task.
For your suggestions to be useful they really need to address the design work
already done, see
http://wiki.services.openoffice.org/wiki/Bibliographic_Project%27s_Developer_Page
regards
David
On Thursday 22 March 2007 7:48 am, Gannon Dick wrote:
> Simple is good :)
>
> I came up with a bit different solution, but the result is the same ...
>
> The 'biblio' table is actually selectable (there is a drop down box).
> Whichever table is selected last is used to populate the attributes of
> the <text:bibliography-mark> node. You can select either a 'table' or
> a 'view'. The 'biblio' table schema contains 5 user defined fields.
> The basic idea is to construct an View (an SQL Query) which formats
> several "short forms" from the data (year, author etc) in that row and
> writes them to the user-defined fields. You can then paste the desired
> "Short Name" in when you insert the "Bibliography Entry" in the
> document. The current DB engine might be a problem, but the native
> HSQL engine has all the power necessary. The other thing is that the
> "Design View" does not have enough columns for 'biblio', so you must
> use SQL (but you only have to create the View once).
>
> I did this because of the "et. al." problem, but it bleeds over into
> the "ibid" problem (you need to retain the source pointer/identifier)
> too.
>
> --Gannon
>
> --Gannon
>
> --- Bruce D'Arcus <[EMAIL PROTECTED]> wrote:
> > It seems we're (finally!) about wrapped up with the ODF metadata work
> >
> > on which we'll base the new citation support. To make a long story
> > short, we've realized that likely the easiest way to proceed with the
> >
> > details of formatting is that Writer has an API which knows how to
> > track citations, but then requests certain pre-formatted strings as
> > needed.
> >
> > David had outlined his ideas on this earlier here:
> >
> > <http://wiki.services.openoffice.org/wiki/
> > Bibliographic_API_Enhancements#constants_group_BibliographyDataField>
> >
> > I'm wondering about a simpler approach still. I am thinking of
> > properties like just citation, shortCitation and bibliographicEntry.
> > In
> > that scheme, if we have a citation like (Doe, 1999, 2000; see also
> > Smith, 1993):
> >
> > - ref 1 and 3 are the default citation string
> > - ref 2 is the short form
> > - ref 3 would also be a "see also" type, and so grouped and prefixed
> >
> > in standard ways that could be overridden
> >
> > So the RDF in package would look like:
> >
> > <b:Book rdf:about="urn:isbn:34982376">
> > <b:citation>Doe, 1999</b:citation>
> > <b:shortCitaton>1999</b:shortCitaiton>
> > ...
> > </b:Book>
> >
> > Any thoughts? Could things be as simple as I am thinking?
> >
> > Bruce
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
>
> ___________________________________________________________________________
>_________ The fish are biting.
> Get more visitors on your site using Yahoo! Search Marketing.
> http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
-------------------
David N. Wilson
Co-Project Lead for the Bibliographic
OpenOffice.org Project
http://bibliographic.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
