About Services Tools Blog Contact us

Flexible Graph Modeller

An admin tree that holds projects, pages and their details in one place, so a new kind of record does not need a new database table.

  • Knowledge Base & SOPs
  • Cross-sector
  • Tool
  • Product
  • Local/private
  • 2025

The problem

Each new kind of record needed another table, another form and another database change, so adding a field meant calling a developer. Editors could not see which records were still incomplete. Nor could they control which parts a viewer was allowed to open.

What it does

Records, their children and their details live in one connected tree. Editors add top-level records and children, and a progress bar shows what is still missing. Viewers, editors and administrators each see different parts of the tree.

Outcomes

  • A new field is added as a new detail, with no database change.
  • Incomplete records show on a dashboard before they are published.
  • Projects, pages and metadata sit in the same tree.
  • Each role sees only the records it should.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

North Quay site

Every scope in this project, including who a node is shared with.

Graph
Home page
titleNorth Quay 20
summaryTrade desk, workshop rooms and how to book 20
hoursMon to Fri, 08:30–17:30 20
meta_descriptionmissing · 40
Publish score 60% Partial

Four keys on a page. Meta description is worth 40. A new key is a property, not a new column.

Add the missing property
Ready. Home is still short of a meta description.
Node JSON
{
  "type": "page",
  "key": "home",
  "parent": "public-site",
  "scope": "public",
  "status": "partial",
  "score": 60,
  "properties": {
    "title": "North Quay",
    "summary": "Trade desk, workshop rooms and how to book",
    "hours": "Mon to Fri, 08:30 to 17:30"
  }
}

Publish gaps

Morning board
Nodes
0
Still partial
0
Private
0
Publish score by node
Open a gap
NodeMissingScoreStatus
Home meta_description 60
partial
Public site locale 80
partial
Depot notes body 40
private
About none 100
complete

Same tree, two logins

Editors see the superuser tree for this project and cannot widen a scope. A viewer never receives Depot notes.

Superuser 5 nodes
North Quayproject
Public sitesite
Homepage
Aboutpage
Depot notesprivate
Viewer 4 nodes
North Quayproject
Public sitesite
Homepage
Aboutpage
Depot noteshidden

How it works

  1. Set up the storage and a first admin login.
  2. Add a top-level record, then children, then details on a record.
  3. Search the tree and open one record at a time.
  4. Score how complete a record is from the details its type expects.
  5. Hide records outside what the signed-in role may see.

Pipeline

flowchart LR
  Root["Project root"] --> Child["Child node"]
  Child --> Props["Typed properties"]
  Props --> Score["Completeness"]
  Score --> Dash["Incomplete list"]
  Role["Role scope"] --> Child