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

Aye/Yes Nay/No #221

Open
ElleNajt opened this issue Dec 2, 2017 · 1 comment
Open

Aye/Yes Nay/No #221

ElleNajt opened this issue Dec 2, 2017 · 1 comment

Comments

@ElleNajt
Copy link

ElleNajt commented Dec 2, 2017

Depending on the bill, the senators who voted for it are sometimes given the key 'Yea' and other times 'Aye.' Similarly, 'Nay' and 'No' are both used to indicate the senators who voted against the bill.

It would be nice if this could be standardized, since I would have to put less exceptions in my code, and that would make it more readable. Alternatively, it takes only a few lines to go through the data and do this by hand; but the less data processing done on the users end the better. So, this is low priority but an easy and possibly helpful fix if you think it's appropriate.

(I assume that these don't have some subtle legal difference that would be lost if they were standardized?)

@JoshData
Copy link
Member

JoshData commented Dec 2, 2017

There is a subtle legal difference, in so far as sometimes it's a yea/nay vote and sometimes it's an aye/no vote, but the difference has no practical meaning.

I would be fine with a normalization in the JSON output so long as the XML output is unchanged. See https://github.com/unitedstates/congress/blob/master/tasks/vote_info.py#L130 which performs normalization already in the XML output.

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

No branches or pull requests

2 participants