Verify accuracy of current srapers

[sethetter]

Non-technical friendly!

Verify the dates that are generated by the scraper for the meetings they are scraping.

The different meeting types are listed here, and the corresponding dates for the meetings are here. The dates correspond to the types by matching tid to the type's id.

If you see any issues, say so here! If it looks good, also say so here!

[Mearnest]

I will attempt to verify the information and dates on what I have so far, but any help would be awseome! I am but one pair of eyes.

[Mearnest]

Actually, best leave this to someone else.

[kaylavix]

So, is there a way for me to know what was scraped and what was just input here by a human https://github.com/openwichita/public-meetings/blob/master/priv/data/meeting_types.json? Or do we need both input types to be checked?

[aaronarduino]

@kaylavix I think all the data comes from the scrapers. So I think all needs to be checked. @Mearnest can correct me if I'm wrong about that.

[Mearnest]

Everything but the Goat and Pandas meetings, which were just testing manual entry on the website.

[kaylavix]

id 1 looks good. That City Council pdf also included 2018 meetings for January, but those aren't in there.
id 2 is also good. Another 2018 date that wasn't scraped?

[kaylavix]

Something's up with id 3, the Board of County Commissioners meetings. Dates are ahead by a couple days. Checked it using the url in the data: https://sedgwickcounty.legistar.com/Calendar.aspx

I'm also not sure how we got dates past April 19, because I can't find anything past that in the above page. Not even if I use their "export to Excel doc" option. Unless it's just assuming Wednesdays.

[kaylavix]

For id 4, Board of Education for 259, I don't see a meeting for March 27, but it's in the data ("id": "113").

There also needs to be a meeting on 6/29. It's their year-end reports meeting.

[Mearnest]

@kaylavix 2018 data wasn't scraped on purpose. It was just meant to be yearly scraping. I added a test 2018 meeting just because.

Also, it's odd to be responding to this 2 months laters. Whoops.

[sethetter]

Better late than never ;)