Null "id" fields V1 API (Bills, Votes, and Legislators)


#1

Currently, when requesting bill detail data from the V1 API, many ‘id’ fields are returned as null, white space, or “~not available~”, namely ‘id’ from the master bill object, ‘vote_id’ and ‘id’ inside the “votes” object, and then each “leg_id” inside of “yes_votes”, “no_votes”, and “other_votes” objects. See bold text below,

Example call:
http://openstates.org/api/v1/bills/fl/2019/SB%207020

Result:
“title”:“OGSR/University Direct-support Organization/Research Funding or Research Plans”,
“summary”:"",
“created_at”: "2019-02-07 11:41:27 ",
“updated_at”: "2019-02-10 12:01:19 ",
"id":"",
“all_ids”:[
“”
],
“chamber”:“upper”,
“state”:“fl”,
“session”:“2019”,
“type”:[
“bill”
],
“bill_id”:“SB 7020”,

“votes”:[
{
“session”:“2019”,
"id":"~not available~",
"vote_id":"~not available~",
“motion”:“Submitted and Reported Favorably as Committee Bill”,
“date”: “2019-02-05T10:00:00-05:00 “,
“passed”:true,
“bill_chamber”:“upper”,
“state”:“fl”,
“bill_id”:””,
“chamber”:“upper”,
“yes_count”:8,
“no_count”:0,
“other_count”:0,
“yes_votes”:[
{
"leg_id":null,
“name”:“Baxley”
},
{
"leg_id":null,
“name”:“Berman”
},
{
"leg_id":null,
“name”:“Cruz”
},
{
"leg_id":null,
“name”:“Perry”
},
{
"leg_id":null,
“name”:“Simmons”
},
{
"leg_id":null,
“name”:“Stargel”
},
{
"leg_id":null,
“name”:“Montford”
},
{
"leg_id":null,
“name”:“Diaz”
}
],

Additionally,46 legislator results from either the search or detail access display “~not available~” for the “leg_id” value, see bold text below:

Example call:
http://openstates.org/api/v1/legislators?state=fl

Result: (one example out of many)

"id": “~not available~”,
"leg_id": “~not available~”,
“all_ids”: [
“~not available~”
],
“full_name”: “Elizabeth Anne Fetterhoff”,
“first_name”: “Elizabeth Anne”,
“last_name”: “Fetterhoff”,
“suffix”: “”,
“photo_url”: “http://www.flhouse.gov/FileStores/Web/Imaging/Member/4717.jpg”,
“url”: “http://www.myfloridahouse.gov/Sections/Representatives/details.aspx?
MemberId=4717&LegislativeTermId=88”,
“email”: null,
“party”: “Republican”,
“chamber”: “lower”,
“district”: “26”,
“state”: “fl”,

Finally, one of the applications I now maintain relies on many of these ‘id’ values for most of the app to function properly because of the way the original developer created it, and I’d like to know if this will be resolved or if I will need to make major code changes to accommodate the removal of this data.

Best,
Robert


Null 'id' values from v1 API
#2

Any chance that there will be some feedback on this soon?

Thanks,
Robert