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
One possibility would be to generate the (Time .. Time) from a string spec, such as:
"Feb 18, 2014 noon - 6pm"
another would be rather than specifying individual date entries, saying the schedule needs to be generated over a range of days (e.g. "Feb 18, 2014 - Feb 28, 2014") and then give day specs (e.g. "Mon - Wed, 10am - 5:30pm")
I think the best solution would be to have voteatx import VIP data, and spin this issue out to a separate project that generates VIP datasets from the Travis County data dumps.
The text was updated successfully, but these errors were encountered:
The mechanism for defining schedules is still arduous and prone to errors.
You can see this at:
https://github.com/chip-rosenthal/voteatx/blob/master/data/voting-places/20140304/generate.rb#L74
One possibility would be to generate the (Time .. Time) from a string spec, such as:
"Feb 18, 2014 noon - 6pm"
another would be rather than specifying individual date entries, saying the schedule needs to be generated over a range of days (e.g. "Feb 18, 2014 - Feb 28, 2014") and then give day specs (e.g. "Mon - Wed, 10am - 5:30pm")
I think the best solution would be to have voteatx import VIP data, and spin this issue out to a separate project that generates VIP datasets from the Travis County data dumps.
The text was updated successfully, but these errors were encountered: