Document location

Document location is one of Demiton's published registers for Australian civil construction. Where an entity's source documents live: a SharePoint or Dropbox folder. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.

Part of Documents in the register catalog.

Register ID

document_locationUse this name to ask for the register. The API calls it a shelf ID.

Each record is

A stateThe current value of something, replaced when it changes.

Status

DeclaredDefined, and fills when a source produces its first record.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1 (1.0.3)Current version.

Download JSON SchemaSee an example record

Standards

This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.

• ISO 19650Organization and digitization of information about buildings and civil engineering works, including BIM - Information management using BIM - Part 1: Concepts and principlesAustralia · 2019 · public summary
• ISO 19650Information management using BIM - Part 2: Delivery phase of the assetsAustralia · 2019 · public summary
• ISO 19650Information management using building information modelling - Part 1: Concepts and principlesInternational · 2018 · public summary
• ISO 19650Information management using building information modelling - Part 2: Delivery phase of the assetsInternational · 2018 · public summary

Connectors

Connected today

Demiton keeps this register current from these systems now.

No system fills this register yet.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

• MittiPartial
• Oracle AconexPartial
• PayappsPartial
• SitematePartial
• Xero AccountingPartial

Fields

16 fields: 5 required, 7 optional, 4 defined by each organisation.

Required

Every record carries these fields.

systemText

The storage system of one source; only SharePoint and Dropbox are crawlable.

Example: SHAREPOINT

sourcesList

The ordered list of places to look: each element is one complete declarative locator.

entity_typeText

The entity kind whose documents this binding locates; part of the binding's own supersede key.

Example: project

connector_refText

The logical alias of the connector that reaches this source; also the field the export/import scope filter compares.

Example: sharepoint-bridgeworks-projects

coordinate_keyText

The override discriminator stored in the fact's identity — bare when there is no coordinate override, else an 8-hex hash of the coordinate selector.

Example: project:BWG-2025-001

Optional

Present when the source system records them.

doc_typeText

The specific document type this binding locates, or null for the entity type's general home; part of the supersede key.

file_globText

The file match for this doc type, either * (no filter) or a single *.ext glob.

store_rootText

The path under the store root to start from (null/empty for systems addressed by site+drive)

store_site_idText

The store's site identifier; required to reach a source on systems that address by site.

Example: bridgeworksgroup.sharepoint.com,projects

binding_statusText

Whether the operator has confirmed the binding or it is still a candidate.

store_drive_idText

The store's drive identifier.

store_drive_nameText

The drive's display name, used to translate between the store root and display paths.

Example: Documents

Defined by each organisation

Their contents come from the organisation's own forms or systems, so they differ between organisations.

doc_subpathText

An optional fixed sub-path inside the entity folder where this doc type's files sit.

folder_patternText

A case-insensitive regex matched against folder names at any depth, used where no single sub-path name holds.

Example: Projects/{job_no}

lifecycle_foldersList

The status-tagged folders to traverse, each with a folder name and the entity status it holds.

entity_folder_patternText

How each entity's own folder is named, binding a folder to an entity by its number token.

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

document_location.example.json

{
  "connector_ref": "sharepoint-bridgeworks-projects",
  "coordinate_key": "project:BWG-2025-001",
  "entity_type": "project",
  "folder_pattern": "Projects/{job_no}",
  "source_system": "SHAREPOINT",
  "sources": [
    "ITP",
    "SWMS",
    "Variations"
  ],
  "store_drive_name": "Documents",
  "store_site_id": "bridgeworksgroup.sharepoint.com,projects",
  "system": "SHAREPOINT"
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL

https://docs.demiton.io/registers/document_location/v1.json

Show the full JSON Schema

Loading the schema…