Skip to content

Legislator Profile - Committee Votes #2135

@Mephistic

Description

@Mephistic

Summary

The issue covers the implementation of the Committee Votes tab on the Legislator Profile. There is an open question around how much

The data for these votes only just became available in the current general court - so we only need to cover this data from court 194 (2025-2026) onward.

Success Criteria

  • INVESTIGATE: Check Votes from API + PDFs (on the legislature's Committee page) for:
    • Floor Votes
      • Our test assumes this data is available, but we've only seen Committee Votes so far. Check with Matt Victor to see if we can find an example bill we'd expect this data for.
      • Depending on results of the investigation here, we may skip these for the first pass.
    • Amendment Votes
      • I don't know if we currently scrape these, but we do track some Amendment numbers on Bill documents and there is a Roll Call API that has some Yea/Nay votes (but there's no direct link to Bills at first blush, so I'm not sure what these even represent)
      • Check with Matt Victor to find some examples here.
      • Might be worth including either way, but we need a way to track what a Roll Call vote actually means (e.g. Roll Call 3 in the current court for the Senate has a Question Motion: Question on adoption of the amendment 9 - no idea what that amendment 9 is).
      • Depending on results of the investigation here, we may need to skip these for the first pass - there could be a separate scraper pipeline we need to build out.
    • Committee Votes
  • Implement the Committee Votes tab, including
    • Filter by Floor/Amendment/Committee Votes
      • As per investigation, this can be excluded if we can't find a reliable way to get Floor/Amendment votes - we'll just default to Committee votes to start
    • Statistics bar for all votes from the current general court
    • List of most recent 10 votes for each supported category
      • I would say not to worry about pagination for the first pass here - getting consistent and useful data is priority number one

Screenshots

Image

Additional Links

Metadata

Metadata

Assignees

No one assigned

    Labels

    Ready for DevelopmentAutomatically assigned to issues that are ready to be picked updatafrontendFrontend developmenthelp wantedExtra attention is neededscraperBackend work related to content scraping

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions