saizai
New member
So, I'm planning how I might do the site I mentioned earlier as hypothetical.
I'm going to try posting here about design for it to see how the response is. If helpful, I'll continue; if not, I won't.
(I'm also consulting with some Interesting People through other media of course.)
There are several parts to the design. One is, what questions should be asked of all participants during registration? This information would be used to
a) go with all their accident or near-accident reports to analyze factors
b) go towards socioeconomics by bike or similar analysis
c) profile site population vs. general motorcycle population to see probable gaps of knowledge
d) be part of the data put in to a personalized and specific risk assessment profile
Here's what I have so far (in short form). I'll put it in code blocks 'cause I'm too lazy to reformat it for vB and want to preserve the indenting.
All of the lists - for example, motorcycle models, helmet models - are going to be fully automated and categorized, with some seed data and a mechanism for inputting new items not already in the database.
Most of this info should be for obvious reasons - e.g. to determine both what this particular user's risk levels are, and to use in the opposite direction to determine how accidents correlate to various factors being tracked or to interrelation between factors (e.g. bike's CC vs rider weight?). Some is for purely demographic use.
Most of the rest is to only need to ask once, so that it can then be just confirmed or tweaked if the participant (or 3rd party) reports an accident somewhere down the line.
A few items - name, email, license plate # - would be used to enable third parties to input information into the database, or to contact the rider (one way) through the website, but would never be released and would be kept separate from all other data. This would be used, e.g., by field survey teams, or to ask relatives / friends to input about a rider who's become injured enough not to be able to participate.
(I intend to have a privacy policy that encourages honest participation, so that means e.g. never releasing personal data [eg to police or insurance] without user permission or a court order.)
So - any suggestions or refinements on the above? Stuff to add, change, or ditch?
I'm going to try posting here about design for it to see how the response is. If helpful, I'll continue; if not, I won't.
(I'm also consulting with some Interesting People through other media of course.)
There are several parts to the design. One is, what questions should be asked of all participants during registration? This information would be used to
a) go with all their accident or near-accident reports to analyze factors
b) go towards socioeconomics by bike or similar analysis
c) profile site population vs. general motorcycle population to see probable gaps of knowledge
d) be part of the data put in to a personalized and specific risk assessment profile
Here's what I have so far (in short form). I'll put it in code blocks 'cause I'm too lazy to reformat it for vB and want to preserve the indenting.
Code:
Data collected on registration:
profile
name <--- private!
login <--- private!
email <--- private!
Country
ZIP code
socioeconomics (optional)
age
gender
ethinicity(s)
income range
two-scale political position
other personal info
weight
height
inseam
motorcycle(s) ridden
brand
model
- keep list for each brand/model combo with:
- type eg sport, standard, touring, dirt, etc
- cc
- weight
- etc
year
color
purchase price (optional)
ownership (own, rent/lease, borrow, passenger-only)
modifications
visibility / audibility
... specific lists for each
performance
comfort
aesthetics
safety
cargo
other
insurance
license plate # <--- private!; used for 3rd-party input (never output!)
gear ever worn while riding
generics for non-brand items, e.g. light tshirt, light longshirt, shorts,
sandals, fashion leather jacket, earplugs, etc
brand
model
color
size
purchase price (optional)
substantial modifications (e.g. additional reflective stripes, helmet mirrors)
- usual sets of gear / ensembles (used later when asking what gear
was worn during a given month)
- helmet, visor (none, clear, non-clear), glasses, torso outer-outer
(reflective gear, raingear), torso outer (jackets), torso inner (under
armor), lower outer, lower inner, torso/lower attachment type (none,
one-piece, full zip, partial zip), gloves, footgear, ear (earplugs, music)
experience (months/years and age first started)
car driving (auto)
car driving (manual)
dirt bike riding
<250 cc motorbike (motorized bike, scooter, moped, etc) riding
>250 cc motorcycle riding
any motorcycle riding as passenger (if longer than any previous)
training(s)
organization eg MSF, CLASS
particular course eg BRC, ARC
month/year taken
professional status
non-motor police / military
motor police / military
motorcycle racer (pro)
rank
motorcycle racer (amateur)
rank
motorcycle skills trainer / teacher
organization
other that uses motorcycle as part of job
- years experience in any of aboveAll of the lists - for example, motorcycle models, helmet models - are going to be fully automated and categorized, with some seed data and a mechanism for inputting new items not already in the database.
Most of this info should be for obvious reasons - e.g. to determine both what this particular user's risk levels are, and to use in the opposite direction to determine how accidents correlate to various factors being tracked or to interrelation between factors (e.g. bike's CC vs rider weight?). Some is for purely demographic use.
Most of the rest is to only need to ask once, so that it can then be just confirmed or tweaked if the participant (or 3rd party) reports an accident somewhere down the line.
A few items - name, email, license plate # - would be used to enable third parties to input information into the database, or to contact the rider (one way) through the website, but would never be released and would be kept separate from all other data. This would be used, e.g., by field survey teams, or to ask relatives / friends to input about a rider who's become injured enough not to be able to participate.
(I intend to have a privacy policy that encourages honest participation, so that means e.g. never releasing personal data [eg to police or insurance] without user permission or a court order.)
So - any suggestions or refinements on the above? Stuff to add, change, or ditch?