LoveShack-Inc / LoveShack-Inc/represent
Representative Table
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Create a table for representative information
- ID — Auto increment
- First name — nullable
- Middle name / initial — nullable
- Last name
- State
- Party — nullable
Constraints - composite, unique constraint
On insert, will check if attributes are unique across table
When processing PDFs, take rep name, lookup in table. If record exists, take representative ID, use as foreign key in vote results table. If not, insert into representative table, use ID generated from that instead.
For every table, there are two additional structural things in the code to support them
- Data Access Object (one per table)
- DataClass - mapping rows to Python objects
CRUD (create, read, update, delete)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing table Data Access Objects and DataClass mappings, then trace the PDF-processing path and the vote results table. Define the representative schema, its composite uniqueness rule, CRUD behavior, and lookup-or-insert flow; done means representative IDs can be used as vote-result foreign keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100