No person data attached to Alabama 2018rs bills


#1

Hi,

When using

  sponsorships {
    name
    person {
      id
      name
    }
  }

when looking up a bill person is returned as null for all 2018rs bills and some 2017rs bills I have tested. This data seems available via OpenStates.org though. Is this a bug or am I missing something?


#2

I ask because some bills on OpenStates.org associate the person correctly and link to that person. Some of them only include the last name with no link. This means that the relation is there on the OpenStates website but not in the API yet.

For example: https://openstates.org/al/bills/2018rs/HB100/ has a correct person relation and links to profile. This one does not:


#3

I haven’t looked at this specific case, but a name without a person usually means that, for some reason, OpenStates was unable to unambiguously match the name scraped from the bill with a saved legislator. If you look through the list of legislators from the relevant chamber, it may become clear why in this particular case.


#4

The link referenced is a high profile legislator (now Alabama’s LT Governor). I have not found any instance inside the Alabama 2018 data that correctly attaches the person data.

Here is the above example:

{
  b1: bill(jurisdiction: "Alabama", session: "2018rs", identifier: "HB 100") {
    id
    identifier
    title
    classification
    updatedAt
    createdAt
    subject
    legislativeSession {
      identifier
      jurisdiction {
        name
      }
    }
    actions {
      date
      description
      classification
    }
    versions {
      date
      note
      links {
        url
      }
    }
    sponsorships {
      name
      person {
        id
        name
      }
    }
  }
}

#5

When I said look at the legislators, I meant look at them via the OpenStates API, not via your personal knowledge. You may see something unusual about this person (e.g., that he’s inactive). Then you can look and see if other legislators in the same state have the same problem.


#6

I get that. I guess my question is what the relation is with the OpenStates website and the API is. The OpenStates website is able to make the relationship on their pages, such as this bill: https://openstates.org/al/bills/2018rs/SB354/ but asking the API for that bill does not return the person relationship. Why the difference and how soon can the API be updated to make that relationship that clearly exists on the main website?


#7

AFAIK, the website is still running https://github.com/openstates/openstates.org, using the v1 API, not https://github.com/openstates/new-openstates.org, using the v2 API, and a work in progress. BTW, I still suggest doing the same thing. The one guy doing most of the work, in his spare time from another significant job, on both the website and API, can use all the help he can get in diagnosing problems.


#8

I just checked the V1 API and none of the votes have person data attached either. All return null.

  ["yes_votes"]=>
  array(31) {
    [0]=>
    array(2) {
      ["leg_id"]=>
      NULL
      ["name"]=>
      string(9) "Alexander"
    }
    [1]=>
    array(2) {
      ["leg_id"]=>
      NULL
      ["name"]=>
      string(4) "Ball"
    }
    [2]=>
    array(2) {
      ["leg_id"]=>
      NULL
      ["name"]=>
      string(5) "Black"
    }

and it looks like Sponsors is gone as well, which used to be there as I used it previously.

  ["sponsors"]=>
  array(1) {
    [0]=>
    array(3) {
      ["leg_id"]=>
      NULL
      ["type"]=>
      string(7) "primary"
      ["name"]=>
      string(7) "Beasley"
    }
  }