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
When bills have a high level of interest, on a day when they are slated for a hearing, scrape status updates, instead of waiting for the CSV to update.
For instance, this would yield the ID of every bill that’s had more than 50 views in the past hour that is listed on the docket for today:
SELECT DISTINCT bill_id
FROM dockets
WHERE bill_id IN
(SELECT bill_id
FROM bills_views
WHEREdate> DATE_SUB(CURDATE(), INTERVAL 1 HOUR)
GROUP BY bill_id
HAVINGCOUNT(*) >=50)
ANDdate= CURDATE()
Of course, this doesn't help with the scraping, but at least it IDs the bills in question. Of course, the 50-view mark is entirely contrived.
The text was updated successfully, but these errors were encountered:
When bills have a high level of interest, on a day when they are slated for a hearing, scrape status updates, instead of waiting for the CSV to update.
For instance, this would yield the ID of every bill that’s had more than 50 views in the past hour that is listed on the docket for today:
Of course, this doesn't help with the scraping, but at least it IDs the bills in question. Of course, the 50-view mark is entirely contrived.
The text was updated successfully, but these errors were encountered: