-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(bill actions): duplicate actions in unusual order #211
Comments
Hello. We aware of these duplicate actions and we are working to have these fixed soon. We will let you know when the work is complete. |
Any updates or info on the scope of this bug? Does it only effect 118th congress legislation? |
Hi @ryparker - We are still working on this and will let you know when work is complete. This issue is only impacting the 118th Congress. Hopefully, I will have more updates soon! |
Hi @ryparker - work has been completed on this. Can you confirm things look good on your end and, if so, close this issue? Thanks a bunch! |
I've verified that the duplicated actions have been fixed on the congress.gov API. Although the GovInfo API still has this issue. |
As of 3/20 I've noticed duplicate actions (sometimes with minor text changes) on many legislation in the 118th congress. They seem to not only be duplicated but the duplicates are often ordered so that they are not siblings of their duplicate.
i.e.
This is also present in the GPO API (usgpo/bill-status#235). Is this a GPO or LOC issue?
e.g.
curl --location 'https://api.congress.gov/v3/bill/118/sjres/9/actions?format=json&limit=100&api_key=<API_KEY>'
Response:
Notice the following actions where the legislation was "Vetoed by President" twice.
Also the "senate received the message…" actions have two different texts:
1.) "Veto message received in Senate. Ordered held at the desk."
2.) "Veto Message considered in Senate. (consideration: CR S4739-4740)"
Also notice how the following actions have been duplicated:
Another example HR4366:
Here are the legislation i've encountered this issue with:
118th congress
The text was updated successfully, but these errors were encountered: