Data updates are temporarily on-hold while I perform a (long-delayed) update to the systems that power Cricsheet. Updates will resume once I have the minimum of code in place to provide properly validated updates. All data previously provided by the project is still available, whether in the original YAML format, or the experimental CSV and XML formats.
I am planning to start adding new data as soon as possible, and will update this notice when I have more information.
How did this start?
Cricsheet was started in 2009. The inspiration for it came from a number of sources including Moneyball by Michael Lewis, a post on Pappus plane where he mentioned that he would
would like there to be a cricket equivalent of Retrosheet, and my discovery of the work Aneesh has put in at Against the Spin where he had generated data files for a number of T20 matches. As I had a question I was curious to answer I set about extracting more matches with extended information. A little while later I decided to create a site to put them, and Cricsheet was born.
I never have answered the question I was initially curious about. I have the data now, but I’m not entirely sure how to apply it to the problem!
The name Cricsheet is a homage to Retrosheet the astoundingly impressive source of baseball event data.
He has kindly made it available under a Creative Commons — Attribution-ShareAlike 2.0 Generic — CC BY-SA 2.0 licence, which our icons are also available under. Our gratitude to him.
Who is behind this?
That would be Stephen Rushe. He has written all of the code which extracts and validates the data, as well as developing the website. He also finds it strange to be writing about himself in the third-person.