Service bodies tend to not necessarily follow boundaries that make sense to someone who does not understand it’s organizational makeup. By using the Tomato server, it’s entirely possible to create a schedule that follows geopolitical boundaries without much effort. For this study, I decided to use the 50 states of the United States. This study could have easily been other such designations, perhaps provinces in Canada. I’m also going to make use of the recent feature released in bread 1.6.x (see the blog post on “Reusable Templates w/Bread 1.6.x“)
Keep in mind some of these may not be comprehensive as an entire state may not be covered by a BMLT server at this time. In addition, since the “State” field is free-form text in the BMLT, someone may not be following the two-letter abbreviation naming I’m using here. There is a version of the BMLT root server coming out soon (bmlt-root-server 2.12.0) that will support pre-populating this field as a dropdown. This would require some cleanup as well on each root server. (Note: some of these could take a while to generate).
Status: 5 states no coverage, 10 states partial coverage.
|District of Columbia||Download|
Here’s the bread template used: archsearch-meeting-list-settings-05-26-2019.json
Here’s the reference code for the lab work: