personal-projects/personal-portfolio
Template
1
1
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Sprint 3: Schemas, models, and parser structure #13

New Issue
Closed
opened 2026-01-11 19:51:43 +00:00 by lmiranda · 0 comments
lmiranda commented 2026-01-11 19:51:43 +00:00
Owner
Copy Link

Sprint 3 Deliverables

Pydantic Schemas

  • portfolio_app/toronto/schemas/trreb.py - TRREB record schema
  • portfolio_app/toronto/schemas/cmhc.py - CMHC rental record schema
  • portfolio_app/toronto/schemas/dimensions.py - Dimension schemas

SQLAlchemy Models (Star Schema)

  • portfolio_app/toronto/models/base.py - Base model setup
  • portfolio_app/toronto/models/facts.py - fact_purchases, fact_rentals
  • portfolio_app/toronto/models/dimensions.py - dim_time, dim_trreb_district, dim_cmhc_zone, dim_neighbourhood, dim_policy_event

Parser Structure

  • portfolio_app/toronto/parsers/trreb.py - TRREB PDF parser (structure)
  • portfolio_app/toronto/parsers/cmhc.py - CMHC CSV processor

Database Setup

  • Alembic or raw SQL migrations
  • PostGIS geometry columns for districts/zones

Acceptance Criteria

  • All schemas validate sample data
  • Models create tables in PostgreSQL
  • Parser structure ready for testing with real PDFs
## Sprint 3 Deliverables ### Pydantic Schemas - [x] `portfolio_app/toronto/schemas/trreb.py` - TRREB record schema - [x] `portfolio_app/toronto/schemas/cmhc.py` - CMHC rental record schema - [x] `portfolio_app/toronto/schemas/dimensions.py` - Dimension schemas ### SQLAlchemy Models (Star Schema) - [x] `portfolio_app/toronto/models/base.py` - Base model setup - [x] `portfolio_app/toronto/models/facts.py` - fact_purchases, fact_rentals - [x] `portfolio_app/toronto/models/dimensions.py` - dim_time, dim_trreb_district, dim_cmhc_zone, dim_neighbourhood, dim_policy_event ### Parser Structure - [x] `portfolio_app/toronto/parsers/trreb.py` - TRREB PDF parser (structure) - [x] `portfolio_app/toronto/parsers/cmhc.py` - CMHC CSV processor ### Database Setup - [x] Alembic or raw SQL migrations - [x] PostGIS geometry columns for districts/zones ### Acceptance Criteria - All schemas validate sample data - Models create tables in PostgreSQL - Parser structure ready for testing with real PDFs
lmiranda added this to the Launch: Host, Bio and Toronto House Market Analysis project 2026-01-12 15:00:47 +00:00
lmiranda self-assigned this 2026-01-12 15:00:54 +00:00
lmiranda moved this to Done in Launch: Host, Bio and Toronto House Market Analysis on 2026-01-14 19:34:00 +00:00
lmiranda removed their assignment 2026-01-14 19:34:46 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project Launch: Host, Bio and Toronto House Market Analysis
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/personal-portfolio#13
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?