by adamrice » Fri Mar 19, 2010 5:24 pm
This is a great idea in principle, but I think it needs to get fleshed out a little more.
If you're a runner and want to keep track of your shoes, that's simple. If you're a cyclist, you probably aren't interested in keeping track of your bike as a single item—you probably want to keep track of your chain, your tires, etc. These are part of the bike, but they need separate handling.
One way to handle this would be to set each one up as a separate piece of equipment, and specify all of them for a ride. For everyday use, that would be cumbersome.
Another way to handle it would be to have a way to indicate that one piece of equipment "belongs to" another, for example, this chain belongs to this bike. This would require a little more setup (and a more complicated data schema), but for everyday usage would be easier.
But even that doesn't cover every situation. Many cyclists have more than one pair of wheels. And they will want to be able to indicate which wheels they used for each ride. The way I imagine handling this would be to be able to tag each piece of equipment with its type (eg, "wheel"); if there are two pieces of equipment of the same type that both belong to another piece of equipment, then when you choose your equipment for a ride, Rubitrack would show a popup menu of wheel options.
So now you've got a three-tier hierarchy, because each pair of wheels has tires that belong to it. For example:
- Bike
-- Race wheels
--- Vittoria CX tires
-- Training wheels
--- Schwalbe Durano Plus tires
Of course, even this isn't enough, since many cyclists have more than one bike, and might swap wheels between bikes, so the wheels need to be able to "belong to" more than one bike. I'm not sure how to model that, but clearly, it's complicated.
Of course, the much simpler way to deal with tracking consumables is to simply make a mention in your ride notes when you put a new chain or tire into service.