-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Labels
backendIssues that are mostly for the backend code.Issues that are mostly for the backend code.frontendIssues that are mostly for the frontend codeIssues that are mostly for the frontend code
Description
Currently, there is no way to determine the overall status of legislation when a bill is passed from one chamber to the other or to view how the bill evolves between versions in the House and Senate. To enhance the user experience and provide greater visibility into legislative processes, we need to implement a feature that links bills passed between chambers.
Requirements:
-
Identify Related Bills
- Implement logic to identify bills that are the same legislation but originate in different chambers (e.g., House and Senate).
- Use shared attributes such as bill numbers, titles, or legislative history to match bills.
-
Display Overall Bill Status
- Show the overall status of the bill, including which chamber has passed it and where it is currently under review.
- Add a summary of key milestones (e.g., introduced, passed one chamber, passed both chambers, sent to the president).
-
Provide Link Between Versions
- Add a visual link or button that allows users to toggle between House and Senate versions of the bill.
- Include metadata for each version (e.g., chamber, sponsor, key changes).
-
Version Comparison
- (Optional, stretch goal) Allow users to compare differences between House and Senate versions of the bill, highlighting changes in text or structure.
Technical Considerations:
- Update the bill data model to track related legislation across chambers.
- Ensure database and API integrations support linking bills and their statuses.
- Maintain scalability and performance when handling large datasets.
- Design a user-friendly UI element to navigate between versions of the same bill.
Acceptance Criteria:
- Users can see if a bill has passed one chamber and moved to the other.
- Users can navigate between the House and Senate versions of the same bill.
- The UI clearly displays the overall status of the legislation.
- Backend logic reliably links related bills across chambers.
Notes:
- This feature should align with the overall mission of making legislative processes transparent and easy to understand.
- Consider reusing or adapting existing UI components where possible.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
backendIssues that are mostly for the backend code.Issues that are mostly for the backend code.frontendIssues that are mostly for the frontend codeIssues that are mostly for the frontend code
Type
Projects
Status
No status