874269 - Allow filtering of Events using GET query-params.

Status: RESOLVED WONTFIX

(Webmaker Graveyard :: Events, defect)

Description

[hike]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31

Comment 1

[hike]

Currently you can list Events via GET /events.json or GET /events with Accept: application/json header.

The relevant code is in /app/controllers/events_controller.js (https://github.com/AmoebaConsulting/webmaker.org-compound/blob/master/app/controllers/events_controller.js).

Comment 2

[hike]

GET /events?<field>=<val>&... should allow the user to filter the map display or json output (depending on Accept header or .json) on a subset of the Event-model's fields.

Comment 3

[cbarton]

* Should the "Where" be required when a user fills out the "When" field? It doesn't seem to make a lot of sense showing events on a map filtered to a date since a map shows location.
 
** On that point, how does a user enter a "When" date? Should we use a calendar dropdown? Can they filter by times as well? I know the old mockup had a calendar dropdown, so we could use that convention of expanding the "When" box to show both a start time and end time.

Comment 4

[Mike Beltzner [:beltzner, not reading bugmail]]

(In reply to cbarton from comment #3)
> * Should the "Where" be required when a user fills out the "When" field? It
> doesn't seem to make a lot of sense showing events on a map filtered to a
> date since a map shows location.

The "where" will always be defined by the region indicated by the map, so I guess the answer is "yes"?

> ** On that point, how does a user enter a "When" date? Should we use a
> calendar dropdown? Can they filter by times as well? I know the old mockup
> had a calendar dropdown, so we could use that convention of expanding the
> "When" box to show both a start time and end time.

I think a date-based filter is all we need.

Comment 5

[hike]

The 'Where?' filter has been implemented on the client-side. Eventually we might want to allow GET query filtering for performance reasons, but I don't think it's a priority right now.