My approach to designing databases
A database consists of:
- A store of data records (related pieces of information) usually in the form of one or more tables.
- A set of displays to facilitate adding records or revising the data
- A means of selecting from the the data against set criteria
- A set of preformatted displays,lists, labels, reports etc. into which data from the store can be gathered and presented at the press of a button
Clear, simple agreed procedures are necessary to ensure the creation and maintenance of your database with minimum effort, minimum errors, and ensure your site is kept up to date.
One key to success is a properly designed set of data entry forms – paper questionnaires and database entry forms that match.
The other essential is a properly designed table or set of linked tables to store the data, such that any piece of data only exists in one place.
I offer
- A joint review and discussion about the objectives of the database.
- Development of a the functional requirements including a schema of the data tables and how they are to be linked.
- Creation of a prototype in the desired software - this may involve converting data already stored in a different form.
- Subsequent database modifications to meet changing needs.
- Fault finding
I don't offer
- Data entry, once the database is complete and handed over
What I expect in return
- If I am to make changes to the design of the database as needs change, then the database will need to be kept in a good state of repair by the agreed procedures. Someone in the organisation needs to be proactive in its maintenance.
- I need to be informed early of any shortcomings
of the database found by the organisation using it
