Before we start let me make it clear that this article does not pertain to the player database!
For those of you involved in the Web and more specifically Web 2.0 the idea of an API and Mashups is almost natural and with the Web 2.0 influences in Airbana I got to thinking about the UKARA database.
Assuming the UKARA datbase is normalised and designed properly imagine if there was an external API allowing us to pull up information about a site?
This information should be available through the Freedom of Information act (and if you are registered then I guess the Data Protection Act applies as well) so why not make it easier to access and see what people do with it?
We can make some basic assumptions about what the API should offer:
$API->FindSiteByPostCode(RG1 2NN)$API->GetName(12);$API->GetInsuranceExpireDate(12);
From looking at the Application form we can get a good idea of the sort of data that could be available:
In order to maintain your membership the sites have to keep a record of member visits so there is another opportunity for data mining:
$API->GetMemberCount(12);$API->GetMemberCountOnDate(12,20-03-2008);$API->GetMemberCountDateRange(12,20-01-2008,20-03-2008);
$API->GetUnRegisteredVistorCount(12,20-01-2008);When you start considering the player database (and as I mentioned before I am NOT suggesting the Player database be opened) you could start putting these numbers into context, imagine a graph that shows the uptake of registered players on a National scale, or evaluate the impact of Open Days / freebies have on your future player count.
An API would allow websites like AirBana and potentially even the sites in question to pull the contact details such as the Site mobile phone number from a single source. No longer would a Site Operator have to worry about trawling all the websites / forum posts / contact us pages etc to find the old phone number and update it. Simply update it on the UKARA database and its instantly available to all the sites that use the API.
The Retail side of UKARA also offers us some other intriging opportunities. Using a combination of the functions listed earlier a user could query the API to find out if the Retail site in question has had any complaints in the past [UKARA already publishes an Annual Report to 'Monitor Performance'].
We could utilise AirBana’s XMLRPC files / internal Price Database and the UKARA API to centralise a price list for an all manner of things.
It can be assumed that retailers keep tracks of who buys what, but I doubt that makes it back to UKARA but if it did that would be another opportunity for stats gathering. You’d be able to correlate sales vs player counts at a nearby site without having to brandish a clipboard and get your feet muddy [with that said if you're reading this / care about sales vs player counts you're probably there to get your feet muddy!]
Its only an idea, don’t get too offended if you have any criticisms, opinions or suggestions feel free to put them in the comments or email me at gareth[at]airbana.co.uk