Thursday, July 05, 2007

Data Storage

At this point in the process, you are just storing data. The structure of the data is very fluid at this point. That is you really don't know what you are going to end up storing- the number of fields, what the fields are going to contain, etc. For this reason, I recommend using Excel or some other spreadsheet program.

A spreadsheet is ideal at this point because it is very forgiving and adaptable, and adjustments can be made rapidly. With a database, it is necessary to know what you are going to need to store from the very beginning. I'm sure someone will disagree with that statement, and I would admit that yes, database programs can be adapted after creation. However, I have yet to find one that automatically updates across a schema when adjustments are made. If you have one, go ahead and use it, but just remember, you are now the database administrator- do you really have the time for that at this point?

Another primary advantage to using a spreadsheet is that virtually everyone can operate the program. Even if they have never used the program before, they can be quickly taught how to enter data.

While ultimately you might want to create a relational database structure, that is not necessary now. A spreadsheet is easy to break up into parent and child tables at any point in the future and even on an ad-hoc basis.

Additionally, Excel provides easy access to ad-hoc queries and even cross-tabs (I realize this is perhaps overly technical, if you don't know what I mean by these terms, that's ok, don't worry about it.)

In short, Excel provides all the power you need future, and the simplicity and speed you need now.

A note to geeks:

It may seem like you would want a more robust database program to collect this data, and eventually you might. But unless you are already well versed in that program, taking time to learn is a momentum killer at this point. Now is time for action, not steep learning curves. Hiring the development out is not any better. First of all you can't even design the schema of the database yet so paying someone to develop the database is a waste of money; money that should be spent communicating and collecting additional data. Second, database development can be pretty time consuming, and at this point in the process you don't have the time.

Excel allows for rapid collection of data in a very free form way and with very little training. This is exactly what is needed at this point.

No comments:

 
http://rpc.technorati.com/rpc/ping