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
Massachusetts has just started its new General Court session (Court 194). We need to update our scraping and UX logic to start
We should automatically start scraping legislative members as soon as we add court 194 to our set of court constants (referenced below) - but we should check the UX
Work Detail
Add "194" as a new General Court in constants.ts (it should be the new current court)
We will need 194 set as the current court to start scraping data from the MA Legislature API
We should keep an eye out for the UX as we cut over to the new courts - AFAICT both the scrapers and the UX rely on the same constant, so it's possible that there will be an awkward user experience during the initial scraping (e.g. if we cut over the front-end before the scrapers are run - as we do now, there will be a period of time where we default to an empty court 194). Depending on when the 194 bills go live, this could be a significant amount of time.
We may want to either separate the front-end/back-end current court logic (so we have different switches for turning on the back-end scraping vs the front-end display) - or run the scrapers separately prior to merge so we can add the court 194 data prior to the constant change. Should probably discuss with Matt V.
Scrape the court 194 data
This should happen automatically once the constant change is merged, but there are timing considerations addressed above - so wanted to specifically call this out.
The text was updated successfully, but these errors were encountered:
Summary
Massachusetts has just started its new General Court session (Court 194). We need to update our scraping and UX logic to start
We should automatically start scraping legislative members as soon as we add court 194 to our set of court constants (referenced below) - but we should check the UX
Work Detail
The text was updated successfully, but these errors were encountered: