OPDA Knowledge base
Schema Page 38b1 Generated 2026-05-17 DAMA · Data Modeling & Design · Reference & Master Data

Title · number & extents

2 leaves 0.0% Declaration 100.0% Evidence 0.0% Derivation 0 in overlays 0 with worked example

Entity relationships

--- config: layout: elk elk: direction: DOWN nodePlacementStrategy: BRANDES_KOEPF mergeEdges: false --- erDiagram Transaction ||--o| PropertyPack : "propertyPack" PropertyPack ||--o{ TitlesToBeSold : "titlesToBeSold" Transaction { } PropertyPack { } TitlesToBeSold { string titleExtents "Title Extents" string titleNumber "Title Number" }
Physical model — every JSON object owned by this page is a node, every scalar field a row. 3 objects, 2 scalar fields. Generated from the schema walk; click any node to jump to its table.

Object model

Title · number & extents

Transaction

transaction (root)

No scalar fields on this object — pure container.

Property Pack

propertyPack

No scalar fields on this object — pure container.

Titles To Be Sold[]

propertyPack.titlesToBeSold[]
Title Description Type Kind Field Required Overlays Affordance
Title Extents One or more index polygon describing indicative location of registered title from National Polygon Dataset, JSON.stringified to ensure compatibility string Evidence titleExtents
Title Number string Evidence titleNumber

Comments

Loading comments…