Import confirmed Project seeds with responsibility and Matter Types #5

Closed
opened 2026-06-14 10:21:20 +00:00 by liang · 1 comment
Owner

Parent

Parent PRD: #2

What to build

Import reviewed Project Candidate seed files into the rebuilt schema. Confirmed rows should create or update Projects, Project Titles, Project Aliases, Project Identifier Variants, Project Responsibility, and the initial maintained Matter Type vocabulary so email re-import can match against clean, user-reviewed Projects.

Acceptance criteria

  • Confirmed seeds import Projects with stable Project codes and editable Project Titles derived from reviewed aliases.
  • Project Aliases and Project Identifier Variants are stored separately and Project Identifier Variant normalization strips leading zeros only from the final numeric segment.
  • Project Responsibility supports Owned, Observed, and Delegated Projects with enough data to drive later workflow behavior.
  • Initial Matter Types are seeded as database-maintained records with stable keys, Chinese display labels, descriptions, enabled flags, and sort order.
  • Automated tests verify seed import, responsibility behavior data, Matter Type seed data, and identifier normalization edge cases.

Blocked by

## Parent Parent PRD: #2 ## What to build Import reviewed Project Candidate seed files into the rebuilt schema. Confirmed rows should create or update Projects, Project Titles, Project Aliases, Project Identifier Variants, Project Responsibility, and the initial maintained Matter Type vocabulary so email re-import can match against clean, user-reviewed Projects. ## Acceptance criteria - [ ] Confirmed seeds import Projects with stable Project codes and editable Project Titles derived from reviewed aliases. - [ ] Project Aliases and Project Identifier Variants are stored separately and Project Identifier Variant normalization strips leading zeros only from the final numeric segment. - [ ] Project Responsibility supports Owned, Observed, and Delegated Projects with enough data to drive later workflow behavior. - [ ] Initial Matter Types are seeded as database-maintained records with stable keys, Chinese display labels, descriptions, enabled flags, and sort order. - [ ] Automated tests verify seed import, responsibility behavior data, Matter Type seed data, and identifier normalization edge cases. ## Blocked by - #4
Author
Owner

Implemented issue #5.

Summary:

  • Added services.project_seed_importer.import_project_seed and identifier normalization.
  • Imports confirmed Projects, Project Titles, Project Aliases, Project Identifier Variants, Project Responsibility, and initial Matter Types.
  • Normalizes only the final numeric identifier segment for leading zeros.

Verification: .venv/bin/pytest tests/test_project_seed_importer.py -q -> passed.

Implemented issue #5. Summary: - Added `services.project_seed_importer.import_project_seed` and identifier normalization. - Imports confirmed Projects, Project Titles, Project Aliases, Project Identifier Variants, Project Responsibility, and initial Matter Types. - Normalizes only the final numeric identifier segment for leading zeros. Verification: `.venv/bin/pytest tests/test_project_seed_importer.py -q` -> passed.
liang closed this issue 2026-06-14 10:54:22 +00:00
Sign in to join this conversation.
No labels
ready-for-agent
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
liang/sales-ai#5
No description provided.