-
Notifications
You must be signed in to change notification settings - Fork 94
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
Mechanism for identifying active members #90
Comments
Hey @fowles, There are a few options available to determine who is active but it looks like they are missing from our docs. One option is to add the
Another option is to use our search api. A call to Our member data is updated manually, so at times it may be missing data or slightly out of date. If your looking for the most accurate and up to date info on current senators, https://www.nysenate.gov/senators-json may be a better source of data for you (unfortunately I'm not aware of a similar api for assembly members). I'm going to close this issue, but if you have any other issues or questions feel free to re open this or create a new issue. |
When I try this with full=true I see
but he is still an active member of the senate (I am pretty sure). Is there a data error? |
I don't appear able to reopen this issue |
Yes that does appear to be a data error, thanks for pointing it out. |
Consider. https://legislation.nysenate.gov/api/3/members/2022/senate?limit=1000&key=REDACTED
this responds with a large list that contains
and
CLEARE is the active member having replaced BENJAMIN in a special election, but the API does not provide a way of determining that.
Observationally, the
memberId
andsessionMemberId
are larger, which is likely to do with them being handed out in order, but this is not documented anywhere. Ideally, there would be a documented way to determine the active member in cases like this. I propose adding a boolean"active" : true
which will be true for the member that is currently serving andfalse
for a member that has been replaced.The text was updated successfully, but these errors were encountered: