Skip to content

Create Organization model based on Popolo schema - #160

Open
VirginiaDooley wants to merge 4 commits into
mainfrom
155-create-organization-model
Open

Create Organization model based on Popolo schema#160
VirginiaDooley wants to merge 4 commits into
mainfrom
155-create-organization-model

Conversation

@VirginiaDooley

@VirginiaDooley VirginiaDooley commented Aug 17, 2026

Copy link
Copy Markdown
Member

Change Type

  • YAML data change (divisions / jurisdictions)
  • Code change

Summary

Note on naming convention: Popolo's schema suggests other_names for alternative organization names. However, following @kstohr's suggestion in #155, this PR uses common_names.

Note on scope: The initial issue provided a starting point for the Organization model design. This PR implements a minimal version with only essential fields (name, common_names, url, classification, sourcing). Additional Popolo-compliant fields (like contact_details, image, parent_id, etc.) can be added in future PRs as needed.

What was updated:
src/models/organization.py
tests/src/models/test_organization.py


Code Change

Linked Issue: Closes #155

Validation:

  • uv run ruff check .

@github-actions

Copy link
Copy Markdown

⚠️ This PR contains changes outside the allowed YAML paths (/divisions or /jurisdictions). Auto-merge is disabled. Manual review and merge required.

@github-actions

Copy link
Copy Markdown

⚠️ This PR contains changes outside the allowed YAML paths (/divisions or /jurisdictions). Auto-merge is disabled. Manual review and merge required.

@VirginiaDooley VirginiaDooley changed the title Create Organization model based on Popolo schema including classifica… Create Organization model based on Popolo schema Aug 17, 2026
@VirginiaDooley
VirginiaDooley marked this pull request as ready for review August 17, 2026 10:28
@VirginiaDooley
VirginiaDooley requested a review from kstohr August 17, 2026 10:28
@github-actions

Copy link
Copy Markdown

⚠️ This PR contains changes outside the allowed YAML paths (/divisions or /jurisdictions). Auto-merge is disabled. Manual review and merge required.

@shelltr

shelltr commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Original ticket exists because of my ask. Minimum fields I want/need are "url" and "name".

Note that the attribute "common_names" differs from the popolo/civic tech field which uses "other_names". Nit (on the issue/repo models), but this looks good to me, thank you!

@github-actions

Copy link
Copy Markdown

⚠️ This PR contains changes outside the allowed YAML paths (/divisions or /jurisdictions). Auto-merge is disabled. Manual review and merge required.

@VirginiaDooley

VirginiaDooley commented Aug 30, 2026

Copy link
Copy Markdown
Member Author

Original ticket exists because of my ask. Minimum fields I want/need are "url" and "name".

Note that the attribute "common_names" differs from the popolo/civic tech field which uses "other_names". Nit (on the issue/repo models), but this looks good to me, thank you!

@shelltr Renamed “common_names” to “other_names” to match Popolo standard in befa2bd and ed1d19c

@shelltr

shelltr commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Organization - create pydantic model to capture organization-level information within Jurisdictions

2 participants