Bruce D'Arcus wrote: > One thing that the plug-in does not do currently -- but which would > be nice -- is to allow browsing of the database from within the word- > processor. So using the MS example, imagine if instead they used the > Research Pane to be able to connnect to Zotero? They could then also > move from a citation field in document to a source record in the > bibliographic database.
If Zotero was to provide an API for this database retrieval (I'm not sure if this what I would do in a remote interface, but anyway) we could implement a database cursor around it and then use this one to dump the content into a browser control we hopefully get ready for extension development in 2.3 (not clear ATM). Otherwise we would need to implement a database driver (UNO service) that enables OOo to show the content in the database window in Writer (the window you get when you press "F4"). I really would love to implement everything as a component that can be updated independently from the main OOo code base, means an extension. This would allow us to deliver funtionality incrementally and it would make it easier for other developers to participate in the development. Why is this an important advantage? You should consider that we (the Writer team developers) won't have the resources to implement everything discussed here in the near future. If you wanted to have something done earlier it would be a good idea to plan for "external" contributions and a development cycle that does not need a complete alignment with the OOo releases. So if the browser control wasn't ready in time I would go for the driver even if it was more work to do than hacking the stuff directly into the Writer code base. > This is why I've focused on the metadata work in ODF (so it can store > the data), and have been thinking in terms of a generic API. I have > basically been assuming the bibliographic app sends the requested > citation source metadata -- and maybe optional formatted strings -- > to the word-processor. But we can certainly discuss other options. If the Zotero guys agreed upon using "ODFish" data transfer directly I would be glad to use that. My assumption was that we have to take what we get from there. But that may be wrong. BTW: how is the metadata work going? Do you still think we should have explicit bibliographic data in ODF or are you fine with bibl. data being just another kind of metadata? > FYI, I started a wiki page at the Zotero dev wiki: > > <http://dev.zotero.org/docs/word-processor_integration> > > That in turns links to a page on the API: > > <http://dev.zotero.org/docs/api> > > > .. where I the abstract API ZOOM, which is implemented in open source > code that implements three different protocols, one of which is SOAP > (SRW; the RESTful version is SRU). Thanks, I will have a look as soon as I will have some time. OK, I will do it if I fall prey to the illusion that I have some time. ;-) Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
