In brief, “tagin! is an open source, location tagging engine that may be used to create indoor location-based services (LBS) and applications. Developers can use tagin! to manage points of interest (POI) and digital signs making them available to their applications on WiFi- and Bluetooth-capable devices”.1
My contribution to tagin! was to implement parts of the RESTful API spec, as part of an upper year independent study course with the Adaptive Technology Resource Centre at the University of Toronto (ATRC). After my involvement with tagin!, the ATRC moved to OCAD University and renamed as the Inclusive Design Research Centre (IDRC).
The RESTful API specifies how a client can interact with the server that stores location tags and location WiFi fingerprints. This section uses Pylons, a Python-based open source web application framework that is strongly influenced by Ruby on Rails, having some of its components as ports of Rails features and heavily adopting the model-view-controller pattern.
During my work with tagin!, SQLite was used to store the data (i.e. tags and fingerprints), but there was a desire to migrate to a standalone database like MySQL for the server side.
