Skip to content
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

"passed" or "failed" is incorrectly determined on search results and vote pages #58

Closed
lukesonnet opened this issue Oct 14, 2016 · 6 comments
Labels
Milestone

Comments

@lukesonnet
Copy link
Member

On both the search_list and the individual votes the "passed" or "failed" label is simply determined by whether the yea_count is greater or less than the nay_count. This isn't quite correct.

Some rollcalls have "majority_requirement" which denotes the needed support to pass but not all votes have this. It could also be possible to use the vote_question as a rough guideline for this given we create a dictionary of questions -> needed votes. Again, though, vote_question is not on old rollcalls.

@lukesonnet lukesonnet added the bug label Oct 14, 2016
@lukesonnet lukesonnet added this to the Launch milestone Oct 14, 2016
@lukesonnet
Copy link
Member Author

@adamboche, if I look at the description files here: http://adric.sscnet.ucla.edu/rollcall/ I see a column called result. Do we have this field, can we regurgitate it in some way for our front page?

@adamboche
Copy link
Collaborator

For recent congresses, there is a field called vote_result. I'm not sure if
there's a way to do this for earlier congresses. For rollcalls that have
it, vote_result can be like 'Passed' or something else, like with
{'question': 'On the Motion to Table', 'vote_result': 'Motion to Table
Agreed To'}

On Sat, Oct 15, 2016 at 8:48 PM, Luke Sonnet notifications@github.com
wrote:

@adamboche https://github.com/adamboche, if I look at the description
files here: http://adric.sscnet.ucla.edu/rollcall/ I see a column called
result. Do we have this field, can we regurgitate it in some way for our
front page?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#58 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS6Qi55l9SY8nkf_dOqgInUGAvQNjv68ks5q0Z6egaJpZM4KXghe
.

@lukesonnet
Copy link
Member Author

Thanks adam, we now replace (passed) and (failed) with vote_result where available and fall back on (passed) or (failed) based on a simple majority.

It may still be worth building a dictionary of if "cloture" in question then (passed) if support > 60 or something so I'm going to leave this issue open.

@adamboche
Copy link
Collaborator

I'm not sure we should rely on simple majority. The rule will depend on the
specific vote, and we probably don't want to present information that's
wrong.

Jeff, do you have thoughts on this?

On Oct 16, 2016 1:42 PM, "Luke Sonnet" notifications@github.com wrote:

Thanks adam, we now replace (passed) and (failed) with vote_result where
available and fall back on (passed) or (failed) based on a simple majority.

It may still be worth building a dictionary of if "cloture" in question
then (passed) if support > 60 or something so I'm going to leave this issue
open.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#58 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS6Qi0BzDglBfItBtu3Tc84Sw53cRn9_ks5q0ow2gaJpZM4KXghe
.

@JeffreyBLewis
Copy link
Collaborator

Right. We can't count on majorities particularly for the senate. At the
same time, I am not sure we have what we need to figure out passage for
the older votes.

Jeff

On Sun, Oct 16, 2016 at 1:52 PM, adamboche notifications@github.com wrote:

I'm not sure we should rely on simple majority. The rule will depend on the
specific vote, and we probably don't want to present information that's
wrong.

Jeff, do you have thoughts on this?

On Oct 16, 2016 1:42 PM, "Luke Sonnet" notifications@github.com wrote:

Thanks adam, we now replace (passed) and (failed) with vote_result where
available and fall back on (passed) or (failed) based on a simple
majority.

It may still be worth building a dictionary of if "cloture" in question
then (passed) if support > 60 or something so I'm going to leave this
issue
open.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#58 (comment)
254073325>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AS6Qi0BzDglBfItBtu3Tc84Sw53cRn9_ks5q0ow2gaJpZM4KXghe>

.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#58 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEinZRYw2YnJw2kpaexdjGXSyffAjqnNks5q0o6lgaJpZM4KXghe
.

Jeffrey B. Lewis
Professor and Chair
Department of Political Science
University of California, Los Angeles
BOX 951472, 4289A Bunche Hall
Los Angeles, CA 90095-1472

President
The Society for Political Methodology

lukesonnet added a commit that referenced this issue Oct 16, 2016
@lukesonnet
Copy link
Member Author

Okay, that is definitely the best choice. We always display the yea and nay counts and only the result if it is in vote_result in the database. Inferring passage on older votes from the question could be opened as a new issue as an enhancement if we wish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants