You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A field I'm finding handy in Chicago is allowing location to add a "recursive day" field. This in combination with begin and end dates allows for less "duplicate" data entry for locations that are "flu shots available every Monday through Friday, 8:00 AM to 8:00 PM". This would now only take one row with:
begin date: 09/01/2013
end date: 04/30/2014
begin time: 08:00
end_time: 20:00
recursive days: Monday,Tuesday,Wednesday,Thursday,Friday
'recursive days' is a comma separated list of days of the week, for ease of parsing this string into an array, and doing the date math.
The text was updated successfully, but these errors were encountered:
@tkompare Any chance you could share the Chicago data? Was this data that you converted from a City source, or was it provided by the City in the format your app used. I think it would be helpful to see what another city's data looks like - even with the difference (recursive days) you mention above.
Thoughts on sending a pull request with the data you use on your app n a "city-of-chicago" directory?
A field I'm finding handy in Chicago is allowing location to add a "recursive day" field. This in combination with begin and end dates allows for less "duplicate" data entry for locations that are "flu shots available every Monday through Friday, 8:00 AM to 8:00 PM". This would now only take one row with:
begin date: 09/01/2013
end date: 04/30/2014
begin time: 08:00
end_time: 20:00
recursive days: Monday,Tuesday,Wednesday,Thursday,Friday
'recursive days' is a comma separated list of days of the week, for ease of parsing this string into an array, and doing the date math.
The text was updated successfully, but these errors were encountered: