-
Notifications
You must be signed in to change notification settings - Fork 47
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
Include beginning StatPage for Public Laws #127
Comments
@aih - something else you could look at would be to use the package summary or mods metadata from the associated PLAW package. PL 116-11 isn’t currently available on govinfo, but here’s an example from 116-10: https://api.govinfo.gov/packages/PLAW-116publ10/summary?api_key=DEMO_KEY See the references element. |
@jonquandt, this is great! Is there a way to make sure these are as up to date as the notifications here: https://www.archives.gov/federal-register/laws/current.html ? Timeliness is important for our application (at the LRC). |
Just bumping this issue again, as I'm updating our scraper to work with the very useful If possible, having the starting stat page in that document would put everything we need in one place and avoid having to GET another page related to the same document. This is particularly relevant since the statpage gets updated after the bill becomes a law, and we already look for updates to any Also, fwiw, we'd only need the starting page, though I could see the data including start page and length of the statute. |
Apparently, the information is available even more timely here: |
It would be very useful to have access the initial statpage number for any public law once it is assigned by the OFR. The data is available on individual email/webpages here: https://www.archives.gov/federal-register/laws/current.html
Below, for example, is the update for P.L. 116-11. It includes the page that the P.L. will be placed in the Statutes (133 Stat. 843). This item could be added to the 'laws' element or as its own element in the Bill Status.
The text was updated successfully, but these errors were encountered: