It’s been a while since we’ve posted anything about OxPoints, but at last we now have a lot of Arno Mittelbach’s work in Gaboto implemented into our new OxPoints system. With a new home at http://m.ox.ac.uk/oxpoints !
Last Friday we announced the availability of a few ways to access queries from our new system at an OxPoints workshop in OUCS. Here’s a brief overview of what you can get out of our new oxpoints system as of today.
We’re aiming to improve features incrementally and as demand dictates, so for now we’re offering a simple URL access method to get at a few pre-defined queries (more on complex queries later). The stem for all OxPoints queries is:
Following this, you’ll have to specify the query. As of today, we support two main query types -
- Query by item type (receives list of all items of a certain type).
- Query by OUCS/OLIS code (receive a list of all items associated with a unit, as specified by unique id from computing services or library services)
Item types available -
Next we need to add a file type extension. We support a number of types but these are our primary formats:
Full Data Output
- .json (Direct JSON transformation of all data related to a query)
- .xml (RDF XML – not completely compliant.. yet)
Simplified Output (usually adequate for 95% of uses) – omits irregularly used fields
- .kml (Keyhole Markup Language – perhaps the most common, used by Google Earth & Maps)
- .gjson (Simplified version of .json, omitting irregularly used fields and is easier to read)
- Almost any format supported by GPSBabel
Some simplified formats output via GPS Babel (not supported but should work):
All college data represented in JSON: http://m.ox.ac.uk/oxpoints/colleges.json
Oxford University Car Parks in TomTom format: http://m.ox.ac.uk/oxpoints/carparks.tomtom