Giter Club home page Giter Club logo

api's Issues

Request: Get page range of sections/parts in CFR

Hi Team,

Could you suggest if there is way to get pageNumbers or range of pages for each part or chapter or section in CFR Titles.
E.g., This is the PDF of "Subpart A" in Title12/Part3. It starts at Page 17 and go until Page 41 and total of 25pages
https://api.govinfo.gov/packages/CFR-2018-title12-vol1/granules/CFR-2018-title12-vol1-part3-subpartA/pdf?api_key=DEMO_KEY;
Similarly for a section 1.110, it starts and ends in Page 13 with total of 1 page.
https://api.govinfo.gov/packages/CFR-2018-title12-vol1/granules/CFR-2018-title12-vol1-sec1-110/pdf?api_key=DEMO_KEY

i looked at the corresponding mods XML also Premis XML. I was not able to find this info anywhere. It would be very helpful if there is a way to get this info from API.

Thank you
Nirmala

Bulk Data content access

Currently, we don't provide direct access to the bulkdata contents via the API. How important is that to the community?

The govinfo bulk data repo does provide access to the contents via both xml and json endpoints as it stands.

It's doable to make the bulkdata available via the API, but we're wondering how much a priority that is to the community vs. some of the other features that we're currently looking at?

If we did this, would making BILLSTATUS and ECFR available be sufficient?

downLoad links do not resolve with uppercase API_KEY

This url https://api.govinfo.gov/packages/CHRG-114jhrg94577/summary?API_KEY=DEMO_KEY returns the following response:

{'branch': 'legislative',
 'category': 'Congressional Committee Materials',
 'chamber': 'JOINT',
 'collectionCode': 'CHRG',
 'collectionName': 'Congressional Hearings',
 'congress': '114',
 'dateIssued': '2018-07-17',
 'detailsLink': 'https://www.govinfo.gov/app/details/CHRG-114jhrg94577',
 'documentType': 'JHRG',
 'download': {'modsLink': 'https://api.govinfo.gov/packages/CHRG-114jhrg94577/mods',
              'premisLink': 'https://api.govinfo.gov/packages/CHRG-114jhrg94577/premis',
              'zipLink': 'https://api.govinfo.gov/packages/CHRG-114jhrg94577/zip'},
 'governmentAuthor1': 'Congress',
 'granulesLink': 'https://api.govinfo.gov/packages/CHRG-114jhrg94577/granules?offset=0&pageSize=100',
 'heldDates': ['2018-07-17'],
 'lastModified': '2018-07-30T19:54:06Z',
 'otherIdentifier': {'migrated-doc-id': 'f:94577.txt'},
 'packageId': 'CHRG-114jhrg94577',
 'pages': '156',
 'publisher': 'U.S. Government Publishing Office',
 'session': '2',
 'title': 'Addendum'}

The download links do not resolve. https://api.govinfo.gov/packages/CHRG-114jhrg94577/zip?API_KEY=DEMO_KEY returns

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /govinfoapi//packages/CHRG-114jhrg94577/zip was not found on this server.</p>
</body></html>

and similar for the modsLink and the premisLink

List available Bill Versions

Story

As a govinfo API user, I want to find all available bill versions for a bill, so it is easier to correlate bill status with bill versions.

Acceptance Criteria

  • user specifies a bill status packageId (required) OR user specifies congress (required) and bill number (required)
  • json output
  • return:
    • a list of bill packageIds, version abbreviation, version user readable, and dates so users know the order of bills from new to old.
  • links to bill version files
  • links to bill status file
  • Ask Community for more information about what should be returned

Not all sections referred in BILLS-115s3611is text mentioned in API

Hi Team,

Below API for Bill S 3611 is not providing all the sections referenced in its text. For eg: Sections referred in this bill are "6103",1070","1088" and "1091". But we are only getting 1070, 1088 and 1091 in API output ("sections":["1070","1088","1091"]).
Below is the API I am referring.

https://api.govinfo.gov/packages/BILLS-115s3611is/summary?api_key=DEMO_KEY

Please help me where I can get all the sections related to bill.

Thanks,
Mani Mittal

Granule Content Type Error

Running:
curl -X GET "https://api.govinfo.gov/packages/CREC-2018-01-04/granules/CREC-2018-01-04-pt1-PgD7-3/xml?api_key=DEMO_KEY" -H "accept: */*"

Response:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="http://origin.api.govinfo.gov/content/#contenterror">here</a>.</p>
</body></html>

The API explorer doesn't handle it well either https://api.govinfo.gov/docs/

support congress as a top level searchable element in the API

For many of the collections they are congress specific and in the package info they have the congress in them
for example the bills collection:
package level has:"congress": "115",
but at the collection level that information is not available:
https://api.govinfo.gov/collections/BILLS/2018-01-01T00:00:00Z?offset=0&pageSize=10&api_key=

"packageId": "BILLS-115hr609enr",
"lastModified": "2018-11-01T14:59:34Z",
"packageLink": "https://api.govinfo.gov/packages/BILLS-115hr609enr/summary",
"docClass": "hr",
"title": "An Act T

It would be very helpful for downloading to allow searching and filtering by congress at the collection level, similar to how docClass was added for the CDOC collection
i.e.
https://api.govinfo.gov/collections/BILLS/2018-01-01T00:00:00Z?offset=0&pageSize=10&congress=115&api_key=
and return only 115th items for that time period.

Query specific data from large collection?

Is it possible to query specific data from the § 172.101 Hazardous Materials Table in the Code of Federal Regulations?
https://www.govinfo.gov/app/details/CFR-2018-title49-vol2/CFR-2018-title49-vol2-sec172-101/summary

For example if I wanted to get the info related to the Identification Number UN1088, such as Hazardous materials descriptions and proper shipping names, Hazard class or Division, Identification Numbers, PG, Label Codes, Special provisions, and Packaging Exceptions, how would I construct my CURL query? (please see this image for clarification https://imgur.com/a/OpXuMf1)

Thank you.

Add md5 for HOB to the details link

  1. So the MD5 for each granule is in the list view for lists of hob granules
    https://api.govinfo.gov/packages/HOB-2019/granules?offset=0&pageSize=100&api_key=xxxxxx

but not in the detail view:
https://api.govinfo.gov/packages/HOB-2019/granules/HOB-2019-s1/summary?api_key=DEMO_KEY

Is it possible to have it added to the detail view?

  1. also is it possible to have it added to the mods.xml file as well?

  2. could it be searchable similar to the docClass searching as well? congress + md5 ?

call to collection CDOC is returning non CDOC items

when we make this api call
https://api.govinfo.gov/collections/CDOC/2018-01-01T00:00:00Z?offset=2890&pageSize=10&api_key=XXXXXXXXXX

we are getting non CDOC documents
{"count":2985,"message":null,"nextPage":"https://api.govinfo.gov/collections/CDOC/2018-01-01T00:00:00Z?offset=2900&pageSize=10","previousPage":"https://api.govinfo.gov/collections/CDOC/2018-01-01T00:00:00Z?offset=2880&pageSize=10","packages":[{"packageId":"ERP-2015","lastModified":"2018-05-21T13:20:12Z","packageLink":"https://api.govinfo.gov/packages/ERP-2015/summary"},{"packageId":"GPO-CDOC-113sdoc25","lastModified":"2018-05-22T09:16:50Z","packageLink":"https://api.govinfo.gov/packages/GPO-CDOC-113sdoc25/summary"},{"packageId":"GPO-CDOC-115sdoc6","lastModified":"2018-05-31T14:16:16Z","packageLink":"https://api.govinfo.gov/packages/GPO-CDOC-115sdoc6/summary"},{"packageId":"ERP-2018","lastModified":"2018-05-21T13:20:15Z","packageLink":"https://api.govinfo.gov/packages/ERP-2018/summary"},{"packageId":"ERP-2008","lastModified":"2018-05-21T13:20:50Z","packageLink":"https://api.govinfo.gov/packages/ERP-2008/summary"},{"packageId":"HMAN-110","lastModified":"2018-05-21T14:12:58Z","packageLink":"https://api.govinfo.gov/packages/HMAN-110/summary"},{"packageId":"SMAN-106","lastModified":"2018-05-21T14:22:01Z","packageLink":"https://api.govinfo.gov/packages/SMAN-106/summary"},{"packageId":"SMAN-104","lastModified":"2018-05-21T14:21:48Z","packageLink":"https://api.govinfo.gov/packages/SMAN-104/summary"},{"packageId":"HMAN-115","lastModified":"2018-05-21T14:13:31Z","packageLink":"https://api.govinfo.gov/packages/HMAN-115/summary"},{"packageId":"GPO-CONAN-REV-2016","lastModified":"2018-05-22T04:38:06Z","packageLink":"https://api.govinfo.gov/packages/GPO-CONAN-REV-2016/summary"}]}'''

cfr_References Field discrepancy

Hi,
One of the output provided by this API endpoint : https://www.federalregister.gov/api/v1/documents/2019-03474.json
gives us the CFR references listed under the 'cfr_references' key value. For this particular granule- 2019-03474 there are 3 cfr_references present.

Although if you look at the corresponding ECFR link for that particular granule - 2019-03474 :
https://www.federalregister.gov/documents/2019/03/14/2019-03474/eliminating-unnecessary-
tax-regulations,
under the "List of Subjects" subheading you will see that that are multiple cfr_references that are not present in the API output.

Is this discrepancy expected? Any insight into this would be helpful!

this is not working ---- collections response is now sorting by lastModified date.

collections response is now sorting by lastModified date.

https://api.govinfo.gov/collections/CHRG/1990-01-01T00:00:00Z/?offset=10000&pageSize=100&api_key=DEMO_KEY

snippet:

{
"count": 27027,
"message": null,
"nextPage": "https://api.govinfo.gov/collections/CHRG/1990-01-01T00:00:00Z/?offset=100&pageSize=100",
"previousPage": null,
"packages": [
{
"packageId": "CHRG-103hhrg76069",
"lastModified": "2018-10-30T17:25:19Z",
"packageLink": "https://api.govinfo.gov/packages/CHRG-103hhrg76069/summary",
"docClass": "HHRG",
"title": "Bpa Competitiveness"
},
{
"packageId": "CHRG-103hhrg74075",
"lastModified": "2018-10-30T17:21:12Z",
"packageLink": "https://api.govinfo.gov/packages/CHRG-103hhrg74075/summary",
"docClass": "HHRG",
"title": "Bpa Proposed Flscal Year 1994 Budget"
},
{
"packageId": "CHRG-103hhrg69593",
"lastModified": "2018-10-30T17:17:43Z",
"packageLink": "https://api.govinfo.gov/packages/CHRG-103hhrg69593/summary",
"docClass": "HHRG",
"title": "Indian Tribal Justice Act"
},
{
"packageId": "CHRG-103hhrg74346",
"lastModified": "2018-10-30T13:44:22Z",
"packageLink": "https://api.govinfo.gov/packages/CHRG-103hhrg74346/summary",
"docClass": "HHRG",
"title": "Bpa Electric Power Resources Acquisition"
},
{
"packageId": "CHRG-113shrg28394",
"lastModified": "2018-10-30T13:41:19Z",
"packageLink": "https://api.govinfo.gov/packages/CHRG-113shrg28394/summary",
"docClass": "SHRG",
"title": "Reassessing Solitary Confinement II: The Human Rights, Fiscal, and Public Safety Consequences"
},
{
"packageId": "CHRG-115shrg27017",
"lastModified": "2018-10-30T13:41:16Z",
"packageLink": "https://api.govinfo.gov/packages/CHRG-115shrg27017/summary",
"docClass": "SHRG",
"title": "Nominations of Brock Long, Russell Vought and Neomi Rao"
},
...

Originally posted by @jonquandt in #19 (comment)

Granule mods are not being returned

There's an issue where granule-level mods are not being returned. We're working on a fix for this. Package-level mods are unaffected.

Example:

https://api.govinfo.gov/packages/HMAN-115/granules/HMAN-115-pg339/mods?api_key=DEMO_KEY

Workaround

Much of the relevant information from MODS for the granule is avaialble via the summary json
https://api.govinfo.gov/packages/HMAN-115/granules/HMAN-115-pg339/summary?api_key=DEMO_KEY

or it can be found in the MODS for the package:
https://api.govinfo.gov/packages/HMAN-115/mods?api_key=DEMO_KEY

See the relevant related item, i.e.:
<relatedItem type="constituent" ID="id-HMAN-115-pg339" xlink:href="https://www.govinfo.gov/metadata/granule/HMAN-115/HMAN-115-pg339/mods.xml">

Feature Request for HOB and CRI

Since these collections are published as one large update for all the granules we do not have a good way to determine if the data for individual granules has changed or deleted, we would be able to determine changes faster if there were an md5 hash for each granule (md5 of the the text of the granule). We could keep track of the previous md5 and compare it to the new one to see if things changed so we would not have to re-download every granule/file.

https://api.govinfo.gov/packages/HOB-2018/granules?offset=0&pageSize=100&api_key=
`
"count": 6550,
"offset": 0,
"pageSize": 100,
"nextPage": "https://api.govinfo.gov/packages/HOB-2018/granules?offset=100&pageSize=100",
"previousPage": null,
"granules": [
{
"title": "A bill to amend title 10 United States Code, to establish a punitive article in the Uniform Code of Military Justice on domestic violence, and for other purposes",
"granuleId": "HOB-2018-hr4639",
"granuleLink": "https://api.govinfo.gov/packages/HOB-2018/granules/HOB-2018-hr4639/summary"m
"md5": "123456789..."
},

`

Type of change for updates made at section level

Hi team,
https://www.federalregister.gov/api/v1/documents/2018-28281.json
In the above API endpoint the 'action' key gives us whether the entire FR document is a rule or a proposed rule.

But as noticed in the particular ecfr link for that FR document : https://www.federalregister.gov/documents/2019/02/14/2018-28281/regulatory-capital-rule-implementation-and-transition-of-the-current-expected-credit-losses?utm_campaign=subscription%20mailing%20list&utm_source=federalregister.gov&utm_medium=em

There are multiple updates made for each legal citation at the section level. Is their any API endpoint that could give us the type of change made for an update made for each legal citation at the section level?

Thank you,
Anirudh

documentation around JSON/XML field definition and values in FR granules

Hi Team,

Could you please suggest if we have some documentation around the definition of fields (elements) and possible values they can take in Federal Register granule level XML files. E.g., and when and where they would be used, as they are not available in all granule XML files.

As well, if there is any documentation available around JSON values (e.g., citation, correction_of, proclamation_number, significant etc.) as well, would be very helpful. Some of them are self-explanatory, but it would be very helpful to have guided documentation around the fields/elements.

Thank you
Nirmala

duplicate data items

Hi all,

This is probably not an API issue, but there are a number packages that seem to have duplicate information.

Below is a list of the ones I've found.

[['https://api.govinfo.gov/packages/CHRG-114shrg31304/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg79104795/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111hhrg54476/mods',
  'https://api.govinfo.gov/packages/CHRG-111hhrg55059/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg48284/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg79104342/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg48308/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg89104354/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg89104347/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg89104346/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg48296/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg89104359/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg48293/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg89104362/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg48317/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg89104372/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54980/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg89104384/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54956/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104391/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54965/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104390/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54968/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104387/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54971/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104392/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54974/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104413/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54986/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104406/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg48302/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104411/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg48305/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104412/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg54989/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg99104419/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112hhrg65734/mods',
  'https://api.govinfo.gov/packages/CHRG-112hhrg66317/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112hhrg73291/mods',
  'https://api.govinfo.gov/packages/CHRG-112jhrg73291/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104454/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg19104469/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg39104526/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg39104525/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104447/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64600/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104481/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64588/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104449/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64603/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104448/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64606/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104470/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64597/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104453/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64618/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104466/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64609/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104450/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64612/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104477/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64621/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg39104544/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72302/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104523/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72311/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104503/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72308/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104516/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72334/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104490/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72333/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg39104524/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72317/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104498/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72332/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg29104494/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72336/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg39104546/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg72337/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg39104568/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg78042/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg24504/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg69104725/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg39104527/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg78060/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg39104555/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg78075/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg49104585/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg87215/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg59104647/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg87249/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg49104586/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg87250/mods'],
 ['https://api.govinfo.gov/packages/CHRG-113shrg49104609/mods',
  'https://api.govinfo.gov/packages/CHRG-113shrg87254/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114jhrg22555/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg22555/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114shrg24506/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg69104668/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114shrg27171/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg69104746/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114shrg59104628/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg93127/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114shrg69104691/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg93112/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114hhrg94494/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg98593/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114shrg69104718/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg98771/mods'],
 ['https://api.govinfo.gov/packages/CHRG-114shrg69104744/mods',
  'https://api.govinfo.gov/packages/CHRG-114shrg98759/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg69104262/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg33929/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg79104332/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg41260/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910446/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg85926/mods'],
 ['https://api.govinfo.gov/packages/CHRG-105hhrg50804/mods',
  'https://api.govinfo.gov/packages/CHRG-105hhrg54586/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg20750/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg27000/mods'],
 ['https://api.govinfo.gov/packages/CHRG-106jhrg67455/mods',
  'https://api.govinfo.gov/packages/CHRG-106jhrg64389/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg92167/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg2910469/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg79104312/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg41242/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg79104324/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg41248/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg49104169/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg99863/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107hhrg82131/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg80036/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg49104167/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg99866/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg92134/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg2910486/mods'],
 ['https://api.govinfo.gov/packages/CHRG-105hhrg97577/mods',
  'https://api.govinfo.gov/packages/CHRG-105hhrg52520/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg27150/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg23926/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg23038/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg20323/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910466/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg85917/mods'],
 ['https://api.govinfo.gov/packages/CHRG-106hhrg64703/mods',
  'https://api.govinfo.gov/packages/CHRG-106hhrg64702/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg79104329/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg41269/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg1910409/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg85914/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107hhrg83027/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg80034/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg77905/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg81196/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910435/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg85908/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg91493/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg91434/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107shrg83485/mods',
  'https://api.govinfo.gov/packages/CHRG-107shrg86375/mods'],
 ['https://api.govinfo.gov/packages/CHRG-105hhrg48166/mods',
  'https://api.govinfo.gov/packages/CHRG-105hhrg48145/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg59104236/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg33932/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910465/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg85923/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg59104239/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg33908/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110hhrg40733/mods',
  'https://api.govinfo.gov/packages/CHRG-110hhrg49982/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910485/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg39104123/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg26759/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg30817/mods'],
 ['https://api.govinfo.gov/packages/CHRG-106hhrg66213/mods',
  'https://api.govinfo.gov/packages/CHRG-106hhrg65393/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg85920/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg2910458/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108hhrg87944/mods',
  'https://api.govinfo.gov/packages/CHRG-108hhrg87943/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg39104113/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg92164/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110hhrg42280/mods',
  'https://api.govinfo.gov/packages/CHRG-110hhrg42883/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107shrg83050/mods',
  'https://api.govinfo.gov/packages/CHRG-107shrg81313/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107hhrg73222/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg73203/mods'],
 ['https://api.govinfo.gov/packages/CHRG-104hhrg25630/mods',
  'https://api.govinfo.gov/packages/CHRG-104hhrg24935/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110hhrg40305/mods',
  'https://api.govinfo.gov/packages/CHRG-110hhrg46780/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg39104133/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg99860/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg24090/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg28103/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg1910421/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg85938/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg92155/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg2910489/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg22833/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg21980/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg69104266/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg33914/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110jhrg42170/mods',
  'https://api.govinfo.gov/packages/CHRG-110jhrg46059/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg69104290/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg33923/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107hhrg72230/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg72330/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg79104318/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg41266/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg49104156/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg99848/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg92143/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg2910468/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910470/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg92158/mods'],
 ['https://api.govinfo.gov/packages/CHRG-105shrg51102/mods',
  'https://api.govinfo.gov/packages/CHRG-105shrg56570/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg24291/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg21017/mods'],
 ['https://api.govinfo.gov/packages/CHRG-105hhrg40796/mods',
  'https://api.govinfo.gov/packages/CHRG-105hhrg40908/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110hhrg41809/mods',
  'https://api.govinfo.gov/packages/CHRG-110hhrg38229/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg28909/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg30548/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg79104327/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg41251/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110hhrg41984/mods',
  'https://api.govinfo.gov/packages/CHRG-110hhrg46057/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg89477/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg89465/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg99875/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg49104179/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910490/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg92152/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg39104130/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg92146/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107hhrg80044/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg80040/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg99878/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg49104176/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg47095/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg45221/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110hhrg45233/mods',
  'https://api.govinfo.gov/packages/CHRG-110hhrg44748/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg85935/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg2910427/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107hhrg80852/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg80851/mods',
  'https://api.govinfo.gov/packages/CHRG-107hhrg80840/mods'],
 ['https://api.govinfo.gov/packages/CHRG-105shrg51563/mods',
  'https://api.govinfo.gov/packages/CHRG-105shrg56572/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg20474/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg21799/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg69104281/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg33935/mods'],
 ['https://api.govinfo.gov/packages/CHRG-106hhrg67557/mods',
  'https://api.govinfo.gov/packages/CHRG-106hhrg67558/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg99881/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg39104146/mods'],
 ['https://api.govinfo.gov/packages/CHRG-110shrg69104268/mods',
  'https://api.govinfo.gov/packages/CHRG-110shrg33917/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910483/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg92131/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg99869/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg49104171/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg27641/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg21820/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg2910459/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg85941/mods'],
 ['https://api.govinfo.gov/packages/CHRG-105shrg56565/mods',
  'https://api.govinfo.gov/packages/CHRG-105shrg50653/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg39104111/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg92140/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg39104107/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg92161/mods'],
 ['https://api.govinfo.gov/packages/CHRG-107shrg81606/mods',
  'https://api.govinfo.gov/packages/CHRG-107shrg79994/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108hhrg92796/mods',
  'https://api.govinfo.gov/packages/CHRG-108hhrg92797/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg85929/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg2910445/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg86911/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg89611/mods'],
 ['https://api.govinfo.gov/packages/CHRG-108shrg89354/mods',
  'https://api.govinfo.gov/packages/CHRG-108shrg89535/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg22985/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg28129/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109hhrg24401/mods',
  'https://api.govinfo.gov/packages/CHRG-109hhrg28102/mods'],
 ['https://api.govinfo.gov/packages/CHRG-111shrg79104339/mods',
  'https://api.govinfo.gov/packages/CHRG-111shrg48290/mods'],
 ['https://api.govinfo.gov/packages/CHRG-112shrg19104445/mods',
  'https://api.govinfo.gov/packages/CHRG-112shrg64594/mods'],
 ['https://api.govinfo.gov/packages/CHRG-115shrg24401/mods',
  'https://api.govinfo.gov/packages/CHRG-115shrg24930/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg49104194/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg27147/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg59104231/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg27927/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg59104210/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg27534/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg59104230/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg27360/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg49104196/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg27113/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg59104218/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg27572/mods'],
 ['https://api.govinfo.gov/packages/CHRG-109shrg59104224/mods',
  'https://api.govinfo.gov/packages/CHRG-109shrg26550/mods']]

Agency Mapping for Section or Each Granule

Hi team,

The ECFR website provides us with the regulatory entity mapping for each Title and Volume. Is their any API endpoint or source from which we can obtain this information in machine readable format? The ecfr link we are referring to is here : https://www.ecfr.gov/cgi-bin/ECFR?page=browse

For eg --
CFR-2018-title17-vol1-sec1-2, this particular granuleID is present in the below API endpoint :
https://api.govinfo.gov/packages/CFR-2018-title17-vol1/granules?offset=0&pageSize=10000&api_key=NSlyx6Yi2AMkeRUpQKm4YFgRSupyXNcobKsKUbGT

We need to map each granuleID present in the above API endpoint with the regulatory entities present on the ECFR website. Any insight would be appreciated!

Thank you,
Anirudh

Bills missing from bills collection?

(This is as of Jan 23, 2:45pm eastern) If I hit the bills collection endpoint for all bills since 2019-01-01

https://api.govinfo.gov/collections/BILLS/2019-01-01T20%3A18%3A10Z?offset=0&pageSize=1000&api_key=<my key>

It seems to be missing a number of senate bills, for example s158. The bill was clearly created/updated since 2019-01-01.

What should I be doing to get all bills from that endpoint?

Add Committee/subcommittee information to package and granule summaries

Including committee and subcommittee data for CHRG and other Congressional collections would be very valuable to users.

Currently they can find the committee information within the MODS metadata file, but it should be something that we expose on the package and granule summaries as well, where it's available in the data.

For example
https://www.govinfo.gov/app/details/CHRG-116hhrg34926/CHRG-116hhrg34926 shows that it is from the Committee on Agriculture.

This should be relatively easy to add.

API is down?

Hi, the API seems to be down. Is there a status page or mailing list to get notified of outages?

Thanks!

Bills become law information not coming in API

Hi Team,

While analyzing the bills API I observed that once bill becomes Law or signed by president there is no entry in bill collection API.
As an example last version we can found for bill 115S2248 is ENR. There is no entry for it becoming the law.
API referred here is : https://api.govinfo.gov/collections/BILLS/2018-12-03T00:00:00Z/2019-01-10T23:59:59Z?offset=0&pageSize=10000&api_key=DEMO_KEY

Could you please tell if this is the issue with API or there will be no entry for bill becoming law.
If there will not be any entry for bill becoming law, how to track its status?

Thanks,
Mani Mittal

api call to retrieve packages based on 'publication date'

Hi,

startDate and endDate parameters are used to search against the lastModified value for the individual packages, Could you let me know if there is a way to get packages based on their publication date?

I was trying to get FR issues published on December 10, 2018. Here is the API call I tried and the JSON response I received.
API Call: https://api.govinfo.gov/collections/FR/2018-12-10T00:00:00Z/2018-12-11T00:00:00Z?offset=0&pageSize=100&api_key=DEMO_KEY
JSON Output: {"count":0,"message":"No results found","nextPage":null,"previousPage":null,"packages":[]}

With the change in Start date like this, I got the result am looking for.
API Call: https://api.govinfo.gov/collections/FR/2018-12-08T00:00:00Z/2018-12-11T00:00:00Z?offset=0&pageSize=100&api_key=DEMO_KEY
JSON Output: {"count":1,"message":null,"nextPage":null,"previousPage":null,"packages":[{"packageId":"FR-2018-12-10","lastModified":"2018-12-08T05:24:32Z","packageLink":"https://api.govinfo.gov/packages/FR-2018-12-10/summary","docClass":"FR","title":"Federal Register Volume 83 Issue 236 (December 10, 2018)","congress":null}]}

I understand that since the last modified date of “FR-2018-12-10” package is 8th December, it didn’t come with my first API call.
I am looking for retrieving all packages published on a specific date.

Thank you.
Nirmala

Related Documents Service

Story

As a govinfo API user, I want to find documents related to one that I already know about, so I can understand how the documents interact.

Acceptance Criteria

  • user specifies a packageId (required) and granuleId(optional)
  • json output
  • return:
    • a list of packageId/granuleIds related to specified accessId - includes all known/implemented relationships
    • description of relationship ( "Bill Version", "Federal Register Documents Related by Regulation Identification Number (RIN)")

Questions

  1. should the relationship description be human-readable or will a machine-readable code with separate provided mapping be sufficient?
  2. would rdf output be desirable?

Question: USCOURTS Total Package Count Variance

Hi,
Quick question, I've just started looking into the API specificity for the US COURTS.
When you call the collection endpoint:
https://api.govinfo.gov/collections?api_key=XXXX
It returns the package and granule count for each collection.

The USCOURTS Collection has a package count of: 3,801,046
{
"collectionCode": "USCOURTS",
"collectionName": "United States Courts Opinions",
"packageCount": 3801046,
"granuleCount": 2617554
}``

Now when I call the USCOURTS collections endpoint:
https://api.govinfo.gov/collections/USCOURTS/1990-01-01T20%3A18%3A10Z?offset=0&pageSize=10000&api_key=XXXXXX

I get back a total count of 1,184,518
{ "count": 1184518, "message": null, "nextPage": "https://api.govinfo.gov/collections/USCOURTS/1990-01-01T20:18:10Z?offset=10000&pageSize=10000", "previousPage": null, "packages": [] }

I've tried change the date and no matter what I change it to this is the maximum total packages available.

So is the total packageCount from the collection the real total or not?

If so how do I obtain the rest of the packages when I invoke the USCOURTS collection api call?

Thank you.

api maintenance

We're doing some maintenance on the backend API. You may see some intermittent 502 errors when trying to connect over the next hour. I will close this ticket when the work is complete

Collections API returning an outdated 'lastModified' date for many bills after 12-21-18

A query of the Collections API for recent bills returns many bills whose 'lastModified' date seems to be frozen at 12-21-2018, though their status XML has a later date, and updated information (e.g. P.L. numbers).

An illustrative example, from the query https://api.govinfo.gov/collections/BILLS/2018-12-10T20:18:10Z/2019-02-09T19:20:10Z?offset=0&pageSize=10000, is the value for item 1750, corresponding to packageId: "BILLS-115hr1733enr". The item has the following object, with lastModified: 2018-12-21T02:27:00Z:

1750:
{
   packageId: "BILLS-115hr1733enr",
   lastModified: "2018-12-21T02:27:00Z",
   packageLink: "https://api.govinfo.gov/…LLS-115hr1733enr/summary",
   docClass: "hr",
   title: "An Act To direct the Sec…f used lubricating oil.",
   congress: "115"
}

The billstatus API for this bill, however, has an updateDate of 2019-01-21T17:31:40Z, and new information (including a P.L. number of 115-345). (see https://www.govinfo.gov/bulkdata/BILLSTATUS/115/hr/BILLSTATUS-115hr1733.xml)

This mismatch seems to apply to bills after 12-20-2018, and before some time in January. I am assuming that the 'lastModified' date relates to the package itself and is being updated when, e.g. a P.L. number is added for an enrolled bill.

Endpoint to display differences between different editions of CFR, USCODE

Hi team,

Is their any API endpoint output that gives us the difference in old regulation text and new within the code of Federal Regulations, for any rule changes published in the federal register.

Secondly is their an API endpoint or access to difference between old and new text for US Code statutes, for any legislative changes via the Congress.

The information that we're looking for can be in any form from XML File returned after making a certain API call or the JSON response received upon making a certain API call.

Thank you,
Anirudh

Request for LSA section level info in JSON or XML format

Hi Team,

LSA collection provides list of CFR sections affected. I was able to get the granules links that provides Title level information e.g., API call that provides granules in LSA collection published in Jan-2019: https://api.govinfo.gov/packages/LSA-2019-01/granules?offset=0&pageSize=100&api_key=DEMO_KEY
From the above link, using the ‘granuleLink’, I could get summary info for each title. (e.g., API link: https://api.govinfo.gov/packages/LSA-2019-01/granules/LSA-2019-01-title20/summary?api_key=DEMO_KEY).
from this summary link, in order to get the details of the sections effected, I think I need to look at pdf and htm format links ("txtLink" and "pdfLink"). E.g., htm format link: https://api.govinfo.gov/packages/LSA-2019-01/granules/LSA-2019-01-title20/htm?api_key=DEMO_KEY; and pdfLink: https://api.govinfo.gov/packages/LSA-2019-01/granules/LSA-2019-01-title20/pdf?api_key=DEMO_KEY

Could you let me know if the sections effected information is available through XML or JSON? I would like to consolidate each section that got affected separately, e.g., write each section that got affected to a single row in csv file.
This kind of manipulation on the PDF and HTM format seems complex, rather not possible as am not able to set demarcation between the section numbers start and end in the HTML format.
Please suggest if I am missing to get the right API link in order to get the section level info in easy manipulation or machine readable format.

Thank you
Nirmala

value of 'volumeCount' variable in CFR collection JSON output

Hi Team,

I am trying to construct the CFR-2018 section level index with the help of CFR collection API call. E.g., this API call (https://api.govinfo.gov/packages/CFR-2018-title12-vol1/summary?api_key=DEMO_KEY) provides ‘volume1’ header level information in CFR Title 12 as JSON output.
“{"title":"Banks and Banking","collectionCode":"CFR","collectionName":"Code of Federal Regulations (annual edition)","category":"Regulatory Information","dateIssued":"2018-01-01","detailsLink":"https://www.govinfo.gov/app/details/CFR-2018-title12-vol1","granulesLink":"https://api.govinfo.gov/packages/CFR-2018-title12-vol1/granules?offset=0&pageSize=100","packageId":"CFR-2018-title12-vol1","download":{"xmlLink":"https://api.govinfo.gov/packages/CFR-2018-title12-vol1/xml","pdfLink":"https://api.govinfo.gov/packages/CFR-2018-title12-vol1/pdf","txtLink":"https://api.govinfo.gov/packages/CFR-2018-title12-vol1/htm","modsLink":"https://api.govinfo.gov/packages/CFR-2018-title12-vol1/mods","premisLink":"https://api.govinfo.gov/packages/CFR-2018-title12-vol1/premis","zipLink":"https://api.govinfo.gov/packages/CFR-2018-title12-vol1/zip"},"branch":"executive","pages":"1118","governmentAuthor1":"National Archives and Records Administration","governmentAuthor2":"Office of the Federal Register","suDocClassNumber":"AE 2.106/3:12/","documentType":"CFR","titleNumber":"12","partRange":{"from":"1","to":"199"},"volumeCount":"8","publisher":"Office of the Federal Register, National Archives and Records Administration","otherIdentifier":{"migrated-doc-id":"12CFR"},"lastModified":"2018-08-03T21:54:07Z"}”

I thought the {"volumeCount":"8"} indicates the total number of volumes in CFR Title 12. But it seems not, there are total 10 volumes in Title12, here is the API link to get Volume10: https://api.govinfo.gov/packages/CFR-2018-title12-vol10/summary?api_key=DEMO_KEY.

Could you confirm what indicates the “volumeCount” key in the JSON output?

Thank you
Nirmala

Title 12 2018 API showing last modified date as 2019-05-06

Hi Team,

I have recently extracted the Title 12 API Data for 2018 (CFR-2018-title12-vol1). That time it was showing last modified date as 2018-08-03. Since new data is available for 2019 but 2018 API is also showing last modified date as 2019-05-06. Does this means metadata for 2018 is also changed and I need to extract the 2018 data again.
Sample API : https://api.govinfo.gov/packages/CFR-2018-title12-vol1/granules/CFR-2018-title12-vol1-chapI-toc-id4/summary?api_key=DEMO_KEY

Please look into the issue and suggest.

Thanks and regards,
Mani Mittal

US Code data for 2018/2019

Hi Team,

US code 2017 edition data is available in API format on govinfo. Is there any update on 2018/2019 editions for US Code.

Thanks,
Mani Mittal

Title 12 volume 2 and volume 5 data not available.

Hi Team,

While checking for 2019 data for title 12 we found it is missing for volume 2 and volume 5. I have mentioned the API calls below. Please let us know when the data will be available.

Also please let us know if there will be any change in data already available and how to track those changes.
Please do let us know the timelines for uploading 2019 data for remaining titles as well.

https://api.govinfo.gov/packages/CFR-2019-title12-vol2/granules?offset=0&pageSize=10000&api_key=DEMO_KEY
https://api.govinfo.gov/packages/CFR-2019-title12-vol5/granules?offset=0&pageSize=10000&api_key=DEMO_KEY

Thanks,
Mani Mittal

FR issue granules (granule content) in XML format

Hi Team,

I am looking for an efficient way to get the content/section numbers/amendment details of selected granules of a FR issue. The XML structure of FR issues provides this information, but it is at entire issue level. Is there a way to get the XML format file at a granule level as well. Right now, I see that the granules data (the content) is available in pdf and htm formats.

e.g., package FR-2019-01-23, I can get the entire issue with this api call: https://api.govinfo.gov/packages/FR-2019-01-23/xml?api_key=DEMO_KEY,
in this if I am interested only the granule “2019-00089” and section numbers and amendment details mentioned in it, I had to search for the granule ID in the XML and take the help of XML tree structure (which is ,

and tags) to get the required content that I am looking for.

I am wondering if the XML structure of the granules are available separately, like how htm and pdf version are given: https://api.govinfo.gov/packages/FR-2019-01-23/granules/2019-00089/htm?api_key=DEMO_KEY
"download":{"txtLink":"https://api.govinfo.gov/packages/FR-2019-01-23/granules/2019-00089/htm","pdfLink":"https://api.govinfo.gov/packages/FR-2019-01-23/granules/2019-00089/pdf","modsLink":"https://api.govinfo.gov/packages/FR-2019-01-23/granules/2019-00089/mods","premisLink":"https://api.govinfo.gov/packages/FR-2019-01-23/premis","zipLink":"https://api.govinfo.gov/packages/FR-2019-01-23/zip"}

If there are any alternative ways to get FR granule level content/specific section numbers of a granule from API rather taking XML file , please suggest.

Thank you
Nirmala

Is the GovInfo API down?

I am unable to get to the documentation page for GovInfo's API. The connection times out with a message of "api.govinfo.gov’s server IP address could not be found." Tried connecting with a Mac and Windows machine through Google Chrome.

Following the example for the Congressional Record collection found here, https://www.govinfo.gov/features/api, fails for the same reason. Attempted the example with both Python's requests and cURL but no success.

Is the API down?

Here is the error from Python's requests.

requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.govinfo.gov', port=443): Max retries exceeded with url: /collections/CREC/2018-10-01T00:00:00Z?pageSize=10&offset=0
(Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x110a79650>: Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known',))

Attempted passing the api.data.gov API key as an HTTP query and as a query parameter.

missing html and pdf download links for CHRG collection at summary link

Hi all seems like CHRG collection is missing the html and pdf download links at the summary level

https://api.govinfo.gov/packages/CHRG-111shrg54718/summary?api_key=DEMO_KEY


"title": "THE DISCOUNT PRICING CONSUMER PROTECTION ACT: DO WE NEED TO RESTORE THE BAN ON VERTICAL PRICE FIXING?",
"collectionCode": "CHRG",
"collectionName": "Congressional Hearings",
"category": "Congressional Committee Materials",
"dateIssued": "2009-05-19",
"detailsLink": "https://www.govinfo.gov/app/details/CHRG-111shrg54718",
"granulesLink": "https://api.govinfo.gov/packages/CHRG-111shrg54718/granules?offset=0&pageSize=100",
"packageId": "CHRG-111shrg54718",
"download": {
"modsLink": "https://api.govinfo.gov/packages/CHRG-111shrg54718/mods",
"premisLink": "https://api.govinfo.gov/packages/CHRG-111shrg54718/premis",
"zipLink": "https://api.govinfo.gov/packages/CHRG-111shrg54718/zip"
},

shouldn't there be html and pdf download links in there? like on
https://www.govinfo.gov/app/details/CHRG-111shrg54718/CHRG-111shrg54718/summary

Search Service - Public Preview

Here's an upcoming service we're thinking about. We'd love to have feedback on any additional features within this service.

Story

As a govinfo api user, I want to be able to get a limited subset of packages or granules based on a query.

Acceptance Criteria

  • search by keyword or specific search operators (similar to existing govinfo ui)
  • allow user to specify fields returned (based on availability within index)
  • field names should follow summary json naming convention
  • specify whether response should be at the default mix of package and granules or only packages
  • allow users to sort ascending or descending using a subset of fields
  • specify pageSize - upper limit still pending
  • default fields returned
    • packageId
    • granuleId
    • lastModified
    • dateIssued
    • lastModified
    • download links to individual content and metadata files
    • summaryLink to the package or granule summary

Examples

  • FR documents that have "bicycle" in the title, including xml and pdf links
  • Congressional Record entries for a particular speaking Member

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.