Skip to content
This repository has been archived by the owner on Aug 30, 2020. It is now read-only.

Analytics #3

Open
wbushey opened this issue Dec 19, 2014 · 1 comment
Open

Analytics #3

wbushey opened this issue Dec 19, 2014 · 1 comment

Comments

@wbushey
Copy link
Member

wbushey commented Dec 19, 2014

Gathering information on API queries and responses will be vauable for a number of reasons, including providing us as developers with information about how end users are interacting with this data, and providing information about the types and locations of services that residents are looking for that can be relayed to government and organization decision makers.

I feel like this is still ticket is still in discovery - I'm not really sure what kind of analytics we're interested in, not do I have solid thoughts on how to implement. So, let's talk about that first.

@wbushey
Copy link
Member Author

wbushey commented Dec 19, 2014

OK, I do have some thougths on what data I'm interested in. What queries is the API receiving? (assuming that queries represent requests for centers/classes/events based on location/time/other attributes) What responses are we returning for queries? Are there queries that are returning 0 results?

There's also part of me that thinks implementation could be dead simple: just write some middleware or response hook that writes the request and response to a database. I'd like to see if there are already Django/Python modules for doing this, but as a last resort I suspect writing this ourselves would be pretty quick.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant