[Drupal] MVP API

[AnthonyAstige]

The [Consumer] side needs this data / api to work

• Basic events list
• Well formatted dates (Canceled w/[Consumer] Deal with times & timezones correctly #25 comment 9:45pm)
• Filter by date Note May 23rd: Filter by Eau Claire's time, watch out for off by timezone errors
• Ensure all needed data included for [Consumer] Mock up what data to show inside map bubbles #5

[Lowell20]

@AnthonyAstige do you know if we will want to filter by a date range or maybe, to keep it simple, just individual dates. For example, the consumer side could send multiple requests, one for each date it needs data for. This is just a thought, just let me know what you think you will be looking for

[AnthonyAstige]

@Lowell20 Just one date at a time sounds good for the MVP.

@aaronsalmon - See Lowell's prior comment, in case you're wire framing up something we may have a need for a date range search soon.

[AnthonyAstige]

@Lowell20 - The api gives dates like "2016-05-04T01:30:00". It looks like UTC, but we think UTC usually has a Z at the end. We need to be sure we're doing the right stuff with times/timezones. Can you confirm it's a standard time format and let us know how to identify the timezone, and/or patch it?

[Lowell20]

restructured a few things, here is the beginning of the endpoints naming, including a vendor endpoint
http://vendors.foodtrucks.codeforeauclaire.org/api/vendors
http://vendors.foodtrucks.codeforeauclaire.org/api/events
http://vendors.foodtrucks.codeforeauclaire.org/api/events/date-or-timestamp

[Lowell20]

I can confirm it is UTC time

[AnthonyAstige]

What's the difference between these:

1. http://vendors.foodtrucks.codeforeauclaire.org/api/events
2. http://vendors.foodtrucks.codeforeauclaire.org/api/events/date-or-timestamp

[Lowell20]

I think my goal is to filter the results by a date or date range, the "date-or-timestamp" text can be replaced with the query parameters.
Right now it is just a placeholder until we know what kinds of parameters we will be sending through

[levifelling]

For the MVP we would need API endpoints for:

1. all events (useful for dev, but not required for MVP)
   http://vendors.foodtrucks.codeforeauclaire.org/api/events
2. events where start_time or end_time is on the given day
   http://vendors.foodtrucks.codeforeauclaire.org/api/events/{date UTC}
   http://vendors.foodtrucks.codeforeauclaire.org/api/events/2016-05-26T00:00:00
3. a single event by uuid
   http://vendors.foodtrucks.codeforeauclaire.org/api/events/{uuid}
   http://vendors.foodtrucks.codeforeauclaire.org/api/events/5ec386b2-a9f8-4a79-9b46-f9e9aff1fd08

I'm no too particular on how you want to format the API so long as we can get access to the data.

[AnthonyAstige]

RE: 2. Simpler and more clear I think to just have the date with no time in the url imo. ie;
http://vendors.foodtrucks.codeforeauclaire.org/api/events/2016-05-26

RE: 3. I'm not sure we need single event query in the API for the MVP - #30 can easily retrieve by date and filter locally by Event UUID. (#38 for lodash opened to help here)

[AnthonyAstige]

We have enough in the API now I think for MVP. Issues will fall out while coding as needed from here.