Skip to content

Fixes for detecting 'ordered reported' and bills passed under suspension by rule#284

Open
JoshData wants to merge 4 commits intomainfrom
jt
Open

Fixes for detecting 'ordered reported' and bills passed under suspension by rule#284
JoshData wants to merge 4 commits intomainfrom
jt

Conversation

@JoshData
Copy link
Member

No description provided.

JoshData added 4 commits May 14, 2022 20:30
…to REPORTED

Although this indicates that a bill is ready for floor action, in the Senate this may result from an opponent objecting to committee consideration, which seems to be a way to kill a bill:

* https://www.everycrsreport.com/reports/RS22309.html
* https://www.congress.gov/congressional-record/2022/5/10/senate-section/article/s2385-7?q=%7B%22search%22%3A%5B%22S.4164%22%2C%22S.4164%22%5D%7D&s=1&r=1

The "type" code (which no one uses) on actions that are actually for "ordered reported" are changed from "calendar" to "ordered-reported".

The "Committee ... Reported by" regex is revised to catch "original measure" and "to Senate".
…ng_action_regex option

I use reparse_actions to quickly test bill action line regex changes that relate to detecting major actions and bill status. It reports a diff of any changed JSON or XML output file. And it works for bills before we have GPO BILLSTATUS XML data files (i.e. before the 108th Congress).

* Some logic is fixed.
* matching_action_regex can be used to select bills to reparse by matching a regex to action lines.
* Don't run on bills before the 93rd Congress which come from parsing Statutes at Large metadata or the Library of Congress American Memory archive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant