1. Community Development Platform
  2. Data model and migration order
Reference

The tables behind Community Development Platform

Community Development Platform ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
14
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Program context:

Organizations, Programs, team members and source mappings define ownership, program policy and source translation.

Case and needs:

Funding cases holds the request; community needs records each linked observation or requested item.

Review evidence:

Record attachments, review decisions and state history retain documents, revision-specific decisions and status movement.

Delivery:

Operation runs, execution attempts and operation receipts keep action attempts and their receipt trace.

Follow-up and access:

Follow up actions holds assigned open work; Users holds user accounts and role labels.

Every table, by feature

Programs and organizations

5 tablesAbout this feature
  • Organizations

    Agencies, departments and community organizations that own programs and funding cases.

  • Programs

    Published program definitions and eligibility offered by an organization.

    Linked to Organizations
  • Team members

    Staff, program officers, reviewers and assigned team members.

    Linked to Organizations
  • Source mappings

    Reviewed field mappings and transform rules between source payloads and target fields.

    Linked to Programs
  • Funding cases

    Funding requests, cases and awards submitted for a program.

    Linked to Organizations, Team members, Programs

Community needs

3 tablesAbout this feature
  • Community needs

    Community need, observation and line detail captured against a funding case.

    Linked to Funding cases
  • Funding cases

    Funding requests, cases and awards submitted for a program.

    Linked to Organizations, Team members, Programs
  • Record attachments

    Uploaded and verified supporting documents and source evidence.

    Linked to Funding cases, Team members

Funding cases

5 tablesAbout this feature
  • Funding cases

    Funding requests, cases and awards submitted for a program.

    Linked to Organizations, Team members, Programs
  • Community needs

    Community need, observation and line detail captured against a funding case.

    Linked to Funding cases
  • Record attachments

    Uploaded and verified supporting documents and source evidence.

    Linked to Funding cases, Team members
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Funding cases, Team members
  • State history

    Immutable workflow-written status transition history for each case.

    Linked to Funding cases, Team members

Independent review

6 tablesAbout this feature
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Funding cases, Team members
  • Funding cases

    Funding requests, cases and awards submitted for a program.

    Linked to Organizations, Team members, Programs
  • Community needs

    Community need, observation and line detail captured against a funding case.

    Linked to Funding cases
  • Record attachments

    Uploaded and verified supporting documents and source evidence.

    Linked to Funding cases, Team members
  • State history

    Immutable workflow-written status transition history for each case.

    Linked to Funding cases, Team members
  • Team members

    Staff, program officers, reviewers and assigned team members.

    Linked to Organizations

Delivery and receipts

4 tablesAbout this feature
  • Operation runs

    Workflow-maintained execution runs with operation key, input hash and persisted result reference.

    Linked to Funding cases
  • Execution attempts

    Each recorded attempt to execute an approved action for a funding case.

    Linked to Funding cases
  • Operation receipts

    Ordered steps inside an operation run with input, output and external receipt state.

    Linked to Operation runs
  • Funding cases

    Funding requests, cases and awards submitted for a program.

    Linked to Organizations, Team members, Programs

Follow-up and corrections

7 tablesAbout this feature
  • Follow up actions

    Assigned outstanding actions, corrections and outstanding requests for a case.

    Linked to Funding cases, Team members
  • Funding cases

    Funding requests, cases and awards submitted for a program.

    Linked to Organizations, Team members, Programs
  • State history

    Immutable workflow-written status transition history for each case.

    Linked to Funding cases, Team members
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Funding cases, Team members
  • Operation runs

    Workflow-maintained execution runs with operation key, input hash and persisted result reference.

    Linked to Funding cases
  • Operation receipts

    Ordered steps inside an operation run with input, output and external receipt state.

    Linked to Operation runs
  • Team members

    Staff, program officers, reviewers and assigned team members.

    Linked to Organizations

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

A case references its organization, owner and program. Community needs, attachments, review decisions, history, actions, runs and attempts each reference the case. A receipt references its run. A review decision has a source revision in addition to the case reference; preserve both during migration. Stable organization and program codes, together with the case number, help match legacy references. Retain source record IDs where outside systems provide them.

Migration order

  1. Load Organizations and Users, then team members with their organization links.
  2. Load Programs and reviewed source mappings under their definitions.
  3. Load funding cases with organization, owner, program, number, revision and status.
  4. Load community needs and record attachments against their cases.
  5. Load review decisions, state history and open follow up actions with the original revision and actors.
  6. Load operation runs, execution attempts and operation receipts, then reconcile external references before treating a case as delivered.

Set up Community Development Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started