Database Report June 2007

Database Report

Team:

The database project consists of the following developers Susmita Basu,  Michael Cassidy, Greg Hubbard, Wendy Langer and Project Leader  Jan Smith.  Con Validas left in May and is now working overseas - thanks for helping kick start the group.

Overview:

The project commenced in April 2007.  Its aim is to design and build a web based database to cover most of Computerbank's work processes. The open source database will cover contact details, sales, user support, free training, computers, inventory and eWaste.

Development tools: We are using PostgreSQL for the database and Django for the web based front end.  Subversion is being used for the code repository via Google Code for open source projects.

Phase one of the project is to build a more user friendly web based database covering the content in our existing Rhadam database.

Completed:

• We researched our existing in-house database Rhadam and noted its strengths and weakness.
  
• We installed and examined the US Free Geek database and reported on its strengths and weaknesses. 
  
• Following on from this research and discussion we have written a draft schema for phase one.
• We trialled the web based Launchpad for our project. We decided the existing beta version of Launchpad was convoluted and lacked some features, so have abandoned Launchpad.  We are now using a free web based Google tool called Google Code.  We host our Subversion repository with Google code which also has a bug tracker and wiki.  We have set up a mailing list with Google groups.
  
• While we could access our Subversion on Google from our homes we  had a problem accessing the web based Subversion at Computerbank.  Last Friday Wendy was able to access Subversion from Computerbank.  Well done Wendy another teething hurdle solved.
• The team have nearly completed the four Django tutorials. 
• We are now confident that Django and Python will be suitable for Computerbank's database needs.  It allows different levels of access and different levels of permissions.  It nicely sidesteps the need to write SQL statements.
  
• There was a minor diversion when one team member (who shall remain nameless) suggested that we all had to learn Intercal to complete the backend. After some mad googling of Intercal and Django by some of us, we concluded Intercal is only used by the deranged and desperate and will not be used on this project.
• The team is now ready to start a round trip of phase one.

Phase two will be adding inventory and ewaste areas.

Detailed information on this project available at:

Database Project on Google Code