A database, at its most basic, is a list of items that have some connection. A simple example would be a telephone directory. In this case the database would have just two 'fields': name and telephone number.
We access databases every day without ever knowing it. Every time we go to the supermarket or get money from a cash-point machine a database is involved somewhere along the line.
BRC already uses at least one database; Mike Jordan has been compiling the Merit Table with the help of one for years. A database should (eventually) save time on manual processes and make currently inaccessible information accessible.
With the benefit of valid, useful, accessible information a coach could have a better overall view of the club and so better tailor sessions which should make it easier to peak for important races.
For the average club member it could mean looking in one place for information on their own and team-mates PB records or the historic club records for each distance. Even future races could be shown and then the club member would know the team-mates they would be running with.
Like anything making something good takes time and skill. I'm pretty certain the club has the skills and no-one is cracking the whip on this one! Making a useful database will mean everyone having some input. Like building a house once the structure is made adding features is not as easy as it would have been at the drafting stage.
Ideally I need to know what sort of information you'd like to see.
Almost any question to which you'd like an answer should be fair game. So think about it and let us know (either speak to Karl, Mike J, Mark W or myself).
Once we have an idea of the questions you want answered, we'll know the data we need to collect. Then you can help again in the collection and validation of this data.
The Internet is the ideal place for the data to reside. This means that it is accessible to anyone with an Internet connection.
The final database will have limited membership information but it could conceivably help the membership secretary depending on the current processes? Once you start the problem is stopping the database becoming all encompassing rather than thinking of ways that it could be used!
Getting something usable will depend on the final requirements and the amount of people that will be working on it.