Skip to content
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

Upcoming Adjustment to Action/Committee Element #147

Closed
5 tasks done
jonquandt opened this issue Dec 17, 2019 · 9 comments
Closed
5 tasks done

Upcoming Adjustment to Action/Committee Element #147

jonquandt opened this issue Dec 17, 2019 · 9 comments

Comments

@jonquandt
Copy link
Member

jonquandt commented Dec 17, 2019

Due to a request from Legislative stakeholders, BILLSTATUS files will soon have an updated element for Committees associated with actions. Key changes include:

  • The element will become the element (/billStatus/bill/actions/item/committees)
  • A single Senate actions can have multiple committees associated with it, as items underneath the element

For BILLSTATUS-115s2979:

<item>
                <actionDate>2018-05-24</actionDate>
                <committees>
                                <item>
                                                <systemCode>ssap00</systemCode>
                                                <name>Appropriations Committee</name>
                                </item>
                                <item>
                                                <systemCode>ssbu00</systemCode>
                                                <name>Budget Committee</name>
                                </item>
                </committees>
                <links/>
                <sourceSystem>
                                <code>0</code>
                                <name>Senate</name>
                </sourceSystem>
                <text>

Read twice and referred concurrently to the Committees on Appropriations; the Budget pursuant to the order of January 30, 1975, as modified by the order of April 11, 1986, with instructions that the Budget Committee be authorized to report its views to the Appropriations Committee, and that the latter alone be authorized to report the bill.
                </text>
                <type>IntroReferral</type>
</item>

Note: due to differences in the data provided and requirements from stakeholders, House actions will continue to have a single committee assigned per action – this can result in a multiple actions with the same text, but assigned to different committees. For an existing example, see BILLSTATUS-116hr796 for the actionCode H11100 dated 2019-01-25.

This will likely result in a need to update scripts that parse for committee information. We anticipate this change to be in place in mid-January 2020. A more firm timeline will be provided in the first week of January.

Once this change is in effect for day-forward BILLSTATUS files, GPO plans to reprocess all existing BILLSTATUS files in the bulkdata repository, beginning with the 116th Congress and moving backwards to the 113th Congress.

There are sample files located here. Additional samples can be provided if needed.

This issue will be closed once the change is live and all existing packages have been reprocessed.

Status of change

  • Changes live in production for day-forward BILLSTATUS

Reprocessing Status:

  • 116th Congress
  • 115th Congress
  • 114th Congress
  • 113th Congress
@jonquandt jonquandt self-assigned this Dec 17, 2019
jonquandt added a commit that referenced this issue Dec 17, 2019
Update readme to point to issue #147 for additional information.
@JoshData
Copy link

It looks like this change is already deployed. Starting on Dec. 13 I started getting 689 bills (in the 116th Congress) with "committees" instead of "committee" in actions. (Example: HR 3) It looks like currently 1,897 bills have this change. Folks using the congress project tools are tracking this issue at unitedstates/congress#245.

JoshData added a commit to unitedstates/congress that referenced this issue Dec 20, 2019
Starting on Dec. 13 I started getting 689 bills (in the 116th Congress) with "committees" instead of "committee" in actions in the incoming
GPO bulk data XML files. (Example: [HR 3](https://www.govinfo.gov/bulkdata/BILLSTATUS/116/hr/BILLSTATUS-116hr3.xml)) It looks like currently
1,897 bills have this change. It appears that the data format change described at usgpo/bill-status#147 was published
early, and only in some bills.

Thankfully, our JSON data format for bills already held a list of committee codes, so no change to our data format was needed.

Once GPO has refreshed all of the bulk data files with the new <committees/> format, this code can be simplified to remove the <committee> case.

Fixes #245.
@jonquandt
Copy link
Member Author

@JoshData - we’re looking into why this configuration was deployed early. We will reset this and reprocess the affected packages. Apologies for the inconvenience!

@JoshData
Copy link

Thanks!

@jonquandt
Copy link
Member Author

@JoshData - we have implemented a fix to prevent the <committees> element from appearing again and are in the process or reprocessing the affected packages -- to be safe, we are reprocessing everything between 12/10/2019 and this evening.

Note: new BILLSTATUS files since ~4:45pm should have the current correct <committee> element under actions

I will provide an updated status when the reprocessing is complete via a comment on this issue -- I can also put a comment on your linked issue if you like.

@jonquandt
Copy link
Member Author

All affected billstatus packages were reprocessed last week.

JoshData added a commit to unitedstates/congress that referenced this issue Jan 28, 2020
…es (#246)

Starting on Dec. 13 I started getting 689 bills (in the 116th Congress) with "committees" instead of "committee" in actions in the incoming
GPO bulk data XML files. (Example: [HR 3](https://www.govinfo.gov/bulkdata/BILLSTATUS/116/hr/BILLSTATUS-116hr3.xml)) It looks like currently
1,897 bills have this change. It appears that the data format change described at usgpo/bill-status#147 was published
early, and only in some bills.

Thankfully, our JSON data format for bills already held a list of committee codes, so no change to our data format was needed.

Once GPO has refreshed all of the bulk data files with the new <committees/> format, this code can be simplified to remove the <committee> case.

Fixes #245.
@jonquandt
Copy link
Member Author

As an update, we are now planning to roll this out in February - likely next week. I will provide an update when we have a firm date.

@JoshData
Copy link

Thanks for the update!

@jonquandt
Copy link
Member Author

This will be going live tomorrow around lunchtime Eastern. I will provide another update with the specific date-time for the cutoff of new and updated BILLSTATUS that will have the new committees element.

Note: This will likely cause a slight delay in the afternoon's processing.

@jonquandt
Copy link
Member Author

jonquandt commented Feb 5, 2020

As of 2020-02-05T16:48:27Z, all BILLSTATUS packages processed will include the committees element under actions.

https://api.govinfo.gov/collections/BILLSTATUS/2020-02-05T16:48:27Z?pageSize=100&offset=0&api_key=DEMO_KEY

We will be performing reprocessing of the 116th Congress over the weekend to ensure that they are fully up-to-date while minimizing impact for items that are currently being updated.

We will also go back and do remaining congresses once we complete the 116th.

cc @JoshData

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants