You might try adding a data point designed to capture why you made each bet in the first place.
I use a series of letter codes for this.
But a number (1, 2, 3, 4, 5, etc.) would work as well.
I've found I need (at a minimum) several hundred tickets sitting in a database.
But once I have that -- I've found that (for me) analyzing the data in terms of why bets were made does a better job of pointing out strengths and weaknesses in my game than does other data points such as surface, dist, class level, etc.
I've given considerable thought as to why this is so.
In my own case the codes I use are data points that describe something subjective -- something unique to me as a player.
This falls into the category of thick data.
Which dovetails with the discussion that took place a while back in this thread:
http://www.paceadvantage.com/forum/s...d.php?t=139762
-jp
.
