ParcelDraft Workflow

Use ParcelDraft workflow for all ordinary parcel changes. Official Parcel versions are read-only in normal operations.

Roles and actions

  • Editor: create draft, update draft in DRAFT, submit, cancel before approval.
  • Reviewer: review-accept (SUBMITTED -> REVIEWED), reject from SUBMITTED, cancel from SUBMITTED or REVIEWED.
  • Approver: final-approve (REVIEWED -> APPROVED), reject from REVIEWED, cancel from REVIEWED.
  • Viewer: read-only access.

Actions depend on the current draft state and an exact dataset role. Approver does not imply Reviewer or Editor for mutations, and Reviewer does not imply Editor.

Standard flow

  1. Create a draft from the current official parcel version (or as a new chain).
  2. Edit draft geometry/attributes while state is DRAFT.
  3. Submit draft (DRAFT -> SUBMITTED).
  4. Reviewer accepts (SUBMITTED -> REVIEWED) or rejects.
  5. Approver final-approves (REVIEWED -> APPROVED) or rejects.
  6. Final approval creates a new official Parcel version.

Draft geometry can also be edited in QGIS without changing this workflow. See Edit parcel drafts outside LMSTool.

State model

  • Active states: DRAFT, SUBMITTED, REVIEWED
  • Terminal states: APPROVED, REJECTED, CANCELLED
  • No transitions are allowed from terminal states.

Important rules

  • The creator or submitter cannot review their own draft.
  • The creator, submitter, or reviewer cannot give final approval.
  • Another eligible person must perform each decision stage.
  • Cancellation is role-based; an eligible non-owner may cancel an active item.
  • Only one active draft is allowed per (dataset, version chain).
  • Rejection requires a reason.
  • Approved/rejected/cancelled drafts are not editable.
  • Final approval fails if the draft source version is not the current official version anymore.
  • Draft saving remains available when overlap notices exist. Yellow identifies expected source overlap, blue identifies permitted legacy overlap, orange identifies another draft, and red identifies a blocking authoritative or reserved-area conflict.
  • Submit and review recompute current evidence. Final approval also checks every authoritative validity interval that would coexist with the new parcel version.
  • Select an overlap notice to zoom to the affected area. Conflict overlays are independent of surrounding-parcel visibility and never move or repair draft geometry.

History and audit

For each draft you can view:

  • draft metadata (created_by, submitted_by, reviewed_by, approved_by, etc.)
  • ordered workflow events with per-draft sequence numbers
  • linked resulting official version after approval

This supports full reconstruction of who did what and when.