 |
RE: [RC] SADDLE "FIT" DATABASE strategy, for the record. - Mike Sofen>>
From: Robert Ferrand [mailto:sadddle@xxxxxxxxxxxxx] Your point that the entry form is improperly designed to provide statistically relevant data because all fields are "free-form entry" is not correct. Currently, we are making a WIDE sweep of the ENTIRE EQUESTRIAN COMMUNITY - WORLD WIDE to better understand what the equestrian community, which comprises 80+ breeds of horses, and as many cross breeds, in a multitude different disciplines, with an undefined number of different types of saddles, so that we all can better understand what equestrians actually believe about saddle fit. You are quite correct, this increases the complexity of querying the database, (hence Oracle), however, I think this is a better approach AT THE BEGINNING OF THE RESEARCH, to let the equestrian community define the parameters, not the saint at the computer. To my knowledge, NO company, institution, or individual has ever attempted an effort on this scale. As the data comes in, we can easily alter the parameters accordingly. So bring them on.<< Unfortunately, your expertise and passion is in the field of saddle fit measurement, not database design, and that was the whole point of my response. You chose instead to mount a soapbox and try to convince us that not only are you altruistic but that there is no linkage between your "research" and your business, and that your research design was correct. I have a different
opinion. I can clearly see such a linkage, AND that isn't why I'm
responding now. I'm responding, once again, to your belief that your
research design is appropriate. With 15+ years as a database architect
working for the largest of companies, I can tell you flat out, without
hesitation it isn't...you will store data that CANNOT be queried for VALID
statistical measures. You have created the classic "Garbage In - Garbage
Out" data model that I routinely have had to fix for my clients.
Mike
Sofen
Santa Cruz,
CA
|