alembic migration for 3 new quality tables

[tombrooks248]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

Adding 3 new tables to the postgres DB

• provision_quality
• dataset_quality
• organisation_quality

Why

This is all part of the provision quality work, these database tables are required so that we can output the new data into the DB and be accessible to be exposed by the API as requested in the parent ticket.

Related Tickets & Documents

• Ticket Link
• Related Issue #
• Closes #

QA Instructions, Screenshots, Recordings

I have tested the migrations in a local postgres and upgrade and downgrade all ran without any errors.

Added/updated tests?

We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.

• Yes
• No, and this is why: don't really do tests for database migrations given they only run once.
• I need help with writing tests

[optional] Are there any post deployment tasks we need to perform?

[optional] Are there any dependencies on other PRs or Work?

Summary by CodeRabbit

• New Features
  • Added quality metrics for datasets, organisations, and dataset provisions.
  • Introduced tracking for entity totals, ownership, authoritative relationships, active resources, and quality scores.
  • Added database support for storing and querying these quality assessments.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2de09302-9f59-4406-9457-9fda118db477

📥 Commits

Reviewing files that changed from the base of the PR and between 73b2c08 and 35fa16f.

📒 Files selected for processing (1)

• migrations/versions/befd8e0ddca9_add_provision_quality_tables.py

---

Walkthrough

Adds database migration and SQLAlchemy ORM mappings for provision, dataset, and organisation quality aggregation tables, including primary keys, quality metrics, and an organisation index.

Changes

Provision quality schema

Layer / File(s)	Summary
Create and reverse quality tables migrations/versions/befd8e0ddca9_add_provision_quality_tables.py	Adds an Alembic migration that creates and removes the three quality tables and the provision organisation index.
Map quality tables to ORM models application/db/models.py	Adds ORM models for provision, dataset, and organisation quality records, with corresponding keys, metrics, scores, and index metadata. Reformats the SQLAlchemy import block.

Estimated code review effort: 3 (Moderate) | ~20 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the change: an Alembic migration adding three new quality tables.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/alembic-for-quality-tables

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[eveleighoj]

need to ad the relevant ORM models