Re: Not reinventing the wheel ...
Markus Hoenicka <[email protected]>
| Newsgroups | gmane.text.refdb.general |
|---|---|
| Message-ID | <[email protected]> |
Stéphane Téletchéa <[email protected]> was heard to say: > Not sure about the future, but actually it already works with Bibus > (that's the reason i've looked towards it). > > You can get a rather complete description for OpenOffice.org connection: > http://bibus-biblio.sourceforge.net/bibus_doc/html/en/usingOOo.html > As far as I understand the document there are two ways to interact with OpenOffice: 1) ODBC This simply pulls the data out of a SQL table via ODBC. This requires that there is a 1:1 mapping of the fields that OO expects and the fields in the database table. RefDB reference databases are relational, that is this simple mapping is not going to work. 2) External control of OO through the UNO interface Sure you can program OO (and Word, fwiw) using their APIs, but this requires each bibliography tool to write one interface per supported word processor (n tools times m word processors makes n*m interfaces). The OO bib project (Bruce, correct me if I'm wrong) tries to implement a mechanism that allows OO to retrieve cited data through the SRU/SRW (http://www.loc.gov/standards/sru/) interface from any database that provides such an interface. This would result in n+m interfaces and is the better approach as soon as you're looking at more than two word processors and more than two data sources. regards, Markus -- Markus Hoenicka [email protected] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642