search

usgpo / api

services to access govinfo content and metadata
https://api.govinfo.gov
Other
170 stars 55 forks source link

(BillStatus): missing legislation #151

Open ryparker opened 2 months ago

ryparker commented 2 months ago

The BillStatus collection (list), package summary, and package xml APIs are missing the following 118 legislation from the 118th congress:

hr3
hr4
hr6
hr8
hr9
hr10
hr13
hr18
hr19
hr8060
hr8061
hr8062
hr8063
hr8064
hr8065
hr8066
hr8067
hr8068
hr8069
hr8070
hr8071
hr8072
hr8073
hr8074
hr8075
hr8076
hr8077
hr8078
hr8079
hr8080
hr8081
hr8082
hr8083
hr8084
hr8085
hr8086
hr8087
hr8088
hr8089
hr8090
hr8091
hr8092
hr8093
hr8094
hr8095
hr8096
hr8097
hr8098
hr8099
hr8100
s4156
s4157
s4158
s4159
s4160
s4161
s4162
s4163
s4164
s4165
s4166
s4167
s4168
s4169
s4170
s4171
s4172
s4173
s4174
s4175
s4176
s4177
s4178
s4179
s4180
s4181
s4182
s4183
s4184
s4185
s4186
s4187
s4188
s4189
s4190
s4191
s4192
s4193
s4194
s4195
s4196
s4197
s4198
s4199
s4200
hjres129
hjres130
sjres73
hres1157
hres1158
hres1159
hres1160
hres1161
hres1162
hres1163
sres648
sres649
sres650
sres651
sres652
sres653
sres654
sres655
sres656
sres657
sres658
sres659
sres660

I've verified that all of these legislation are available on the Congress.gov API, but not GovInfo.

Examples of the APIs i'm using:

Example BillStatus collection (list) request:

curl --location 'https://api.govinfo.gov/collections/BILLSTATUS/2021-1-3T00:00:00Z?offsetMark=*&pageSize=250&congress=118'

Example package summary request:

curl --location 'https://api.govinfo.gov/packages/BILLSTATUS-118s4167/summary'

Response:

{}

Example package xml request:

curl --location 'https://api.govinfo.gov/packages/BILLSTATUS-118s4167/xml'

Response:

{
    "message": "The requested resource does not exist."
}

In addition to the list above, the following 2 legislation are not available in the GovInfo API, but they're also not available in the Congress.gov APIs:

s2
s3

Even though these are likely reserved, would it be possible to have these return a response that verifies it is reserved?

Similar missing legislation issue on the congress.gov repo: https://github.com/LibraryOfCongress/api.congress.gov/issues/233

jonquandt commented 2 months ago

Looking into this to determine why some of those packages listed are returning just {}, but two quick points:

  1. Our BILLSTATUS XML doesn't currently follow the normal /packages/packageId/xml pattern in the xmlLink-- it points to the Bulk data location. For example, in the BILLSTATUS summary above, the xmlLink points to: https://www.govinfo.gov/bulkdata/BILLSTATUS/118/s/BILLSTATUS-118s4167.xml

This isn't very consistent and I'm putting in a backlog item to address this.

  1. We aren't able to determine why a bill or other package doesn't exist in our system, so we would be unable to positively affirm that something is reserved or not.
ryparker commented 2 months ago

Thanks for looking into this.