Hi bibliographers,

Somewhat "inspired" by the latest mails in this group I began to make my mind
how to sort all our high-flying ideas in a "timetable". That is, I would like
it if we could make up our minds about what comes first and what later.
(We have done this in some topics, but there is no overall timetable yet, I
believe.)

Personally I would propose following development phases:

- 0 Do some easy fixes in the current bibliographic components.
     Target OOo2.01-2.1. Implemented by the professional coders.
- 1 Build a minimal workable OOoBib that still is already an enhancement
     over the current one. Integrate an extension framework. Target OOo3.0.
- 2 Extend this minimal framework with additional styles, BibDB filters etc.
     Target OOo3.1, OOo3.x? Mostly done by users and us.
- 3 Extend the framework with more difficult and non-mandatory functions
     and increase friendlyness
     Target OOo3.x? Implemented by the professional coders.

Two tasks arise from this?
1.) Define the "minimum reasonably working" OOoBib and its functionality.
2.) Develop a conceptinal extendable framework that leaves enough flexibilty to
cope with our ever-increasing demands (like formulae in titles, ...) without
the need to implement them all at once. This is something the coders need to
do, but some aspects are relevant for us already.

To give a start for discussion I would define the "minimum reasonably working"
OOoBib as following:
- Database management, based on MODS3
- Inline, footnote and endnote citations in various ways, editable
- Dynamic reference handling: Possibility to do changes in the DB
  that are reflected by the references already in the document.
- Applying styles (APA etc.) to the document
- Framework to edit/build new styles
- Framework for queries and internet searches
- Import filter for the current table-based databases.
  (Any other absolutely necessary import or export filters?)
- Reimporting the document DB into the BibDB?

Once this is reached the next steps that require no or easier coding skills
would be for us:
- define new styles (and templates for other things, if applies)
- build more import/export filters

Meanwhile coders could (hopefully!) concentrate to:
- extend internet search functionality
- (user-aided) BibDB synchronzing
- support formatted titles with equations and such
- build a more sophisticated name handling
- manage references for images, citations (and other objects?)
- extend the GUI for more user-friendlyness from the feedback got from the
  first version, things like "drag-and-drop" citation inserting

In order to define what features are exactly needed to satisfy, lets say, 90% of
the potential OOoBib users, a survey should be done within the potential user
community. Maybe this could get included in the official OOo2.0 user survey?

Comments welcome.

Matthias Basler
[EMAIL PROTECTED]


----------------------------------------------------------------
This mail was sent through http://webmail.uni-jena.de

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to