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

house support offices missing #284

Open
timball opened this issue May 17, 2015 · 3 comments
Open

house support offices missing #284

timball opened this issue May 17, 2015 · 3 comments

Comments

@timball
Copy link
Member

timball commented May 17, 2015

there currently doesn't exist a place to fit the following house support offices (and their websites which is what i care about for the next day or two) . proposal is to create another file like house-support-offices.yaml . Oh and also a complimentary senate-support-offices.yaml .

example of entities that should be listed in file:

  • Clerk of the House
  • Chief Administrative Officer
  • Sergeant at Arms
  • Chaplain
  • Inspector General
  • Historian
  • Law Revision Counsel
  • Legislative Counsel
  • Office of Congressional Ethics
  • Office of the General Counsel
  • Office of Interparliamentary Affairs
  • Parliamentarian
  • Bipartisan Legal Advisory Group
  • senate DPC and SRC

--timball

@konklone
Copy link
Member

This data is going to be a lot more static than the legislator/committee data. If it's useful, then I think this is worth capturing, and worth capturing here, assuming there's some sort of support system for it. Is this going to be used somewhere that will incentivize its accuracy?

I also personally think that #284, #285, and #286 could all be handled by an offices.yml that captures House and Senate support offices, Congressional support offices, and House and Senate leadership offices. We're not trying to encode the formal hierarchy of the legislative branch into data, so it's okay to flatten it. We'd just be capturing what is basically the same data for all of them: name, phone, URL, email, etc.

@timball
Copy link
Member Author

timball commented May 17, 2015

mixing house and senate data together in one file sounds like a bad idea .

@konklone
Copy link
Member

konklone commented May 18, 2015 via email

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