cens/ohmageServer — Issue #191: survey_response/search
Author: jojenki
Created: 2012-02-03 22:19:48+00:00
State: open

We need to add search functionality for survey responses.

Use Case:
This is useful for administrators who need to be able to read information about any survey response. This is optimal over survey_response/read because it's a unique use-case. This is for admins who are less concerned about exactly what data exists for a given campaign and are, instead, interested in material that may be categorized by a different entity such as a user or class.

A specific example is when an admin needs to search through all responses from one specific user across all campaigns and/or classes. In this instance, rather than calling survey_response/read for each campaign to which the user belonged, they could simply search for all survey responses by a specific user.

Implementation:
This will need to take as many parameters as their are "columns" of data to search over. For instance, there will need to be username, campaign_id, start_date, and end_date parameters among others.

This will not need to include parameters that do data aggregation or ordering, such as a column_list parameter, a collapse parameter, or a sort_order parameter. This information is not for analysis purposes, but for auditing purposes. It is intended to return all of the information about all of the survey responses that match the criteria.