Differences between revisions 5 and 6
Revision 5 as of 2004-11-16 05:53:11
Size: 3112
Editor: anonymous
Comment:
Revision 6 as of 2004-12-12 15:16:57
Size: 3270
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
   * Most existing organizations use MS Access databases. To remove this dependency we would need to provide a reasonably simple graphical environment for setting up databases and producing graphical front-ends for them. A range of sample schema and front-ends for each needed database application (with appropriate localisations) would help to ease the transition. Another fairly essential tool for this is software to help automate the conversion of MS Access databases to whatever system we choose. Configuration needs to be easy if not existant.    * Most existing organizations use MS Access databases. To remove this dependency we would need to provide a reasonably simple graphical environment for setting up databases and producing graphical [front-end]s for them. A range of sample schema and front-ends for each needed database application (with appropriate localisations) would help to ease the transition. Another fairly essential tool for this is software to help automate the conversion of MS Access databases to whatever system we choose. Configuration needs to be easy if not existant.
Line 23: Line 23:
 * Potential packages to use  * Potential packages to use:
We need a package that can save the information in ["dBase"] file format. So, it can be opened directly with ["OpenOffice"].
Line 25: Line 26:
   * Gnucash (DebianPackage:gnucash )    * ["Gnucash"] (DebianPackage:gnucash ) for finances
Line 27: Line 28:
   * mysql (DebianPackage:mysql-server ) + phpmyadmin (DebianPackage:phpmyadmin )    * ["mysql"] (DebianPackage:mysql-server ) + ["phpmyadmin"] (DebianPackage:phpmyadmin )
Line 29: Line 30:
   * mdbtools (DebianPackage:mdbtools ) which aims to make it possible to work with MS Access databases under Linux -- either by exporting data from them, or by working with them in place.    * ["mdbtools"] (DebianPackage:mdbtools ) which aims to make it possible to work with MS Access databases under Linux -- either by exporting data from them, or by working with them in place.
  • Database requirements
    • Most existing organizations use MS Access databases. To remove this dependency we would need to provide a reasonably simple graphical environment for setting up databases and producing graphical [front-end]s for them. A range of sample schema and front-ends for each needed database application (with appropriate localisations) would help to ease the transition. Another fairly essential tool for this is software to help automate the conversion of MS Access databases to whatever system we choose. Configuration needs to be easy if not existant.

(An awful lot of NPO's have used Macs because of their lack of learning curve, and for them ?FileMaker Pro seems to be popular. So a migration path from FMP is certainly something to consider, as well.)

A well designed and extensible contact management database with both web and non-web cross platform interfacase might be one of, if not the, killer ap for nonprofits to switch to a free software operating system.

Start with a robust content management framework and then add out of the box functionality or "templates" for things like donor management, membership coordination, organizing mass mailings for fund-raising, election coordination, etc.

  • Databases needed:
    • Membership database
    • Finance
    • Inventory
    • LETS
    • Campaign Contacts (media lists, key targets, cooperating members)
    • Fundraising database
  • Potential packages to use:

We need a package that can save the information in ["dBase"] file format. So, it can be opened directly with ["OpenOffice"].

  • ["Gnucash"] (gnucash ) for finances

  • ["mysql"] (mysql-server ) + ["phpmyadmin"] (phpmyadmin )

  • ["mdbtools"] (mdbtools ) which aims to make it possible to work with MS Access databases under Linux -- either by exporting data from them, or by working with them in place.

  • ODB in its new open source form or the dread ebase.
    • a new version of [http://www.ebase.org/ ebase] is being developed that will run as a webapp, and be released under an open source license. 18 month timeline until running code though.

      • Groundspring.org, the folks who were developing ebase Enterprise (the webapp), have imploded as of 1 October 2004, losing their CEO, their CTO, and their director of marketing. However, they do still have a blog up at http://blog.groundspring.org -- there may be some life in them yet, even if they are releasing their whitepapers and specs in .doc format.

  • ["DBDesigner4"] - certainly the most complete free product in this category. http://www.fabforce.net/dbdesigner4/ . There is an open Request For Package (204475 ). It's GPL licenced, and it needs Kylix 3 or Delphi 7 to compile. cf. http://www.fabforce.net/downloadfile.php?iddownloadfile=7

  • opengroupware.org
    • open group only uses postgres, an additional project for this configuration will be to provide a backend to ["MySQL"] or ["SQLite"].
  • [["SQLite"] http://www.sqlite.org/] has the advantage that it is very easy to install, and that, if needed, a database can be ["FTPed"], or emailed around. Nothing like phpmyadmin exists for it however.