Data Set Fields

What it’s for: A description of what data this set contains and its purpose in the solution.
What to include:
- What the data represents in business terms.
- Which application, service, or store owns or produces this data.
- The scope: what is included and, where helpful, what is explicitly excluded.
- Any key characteristics — e.g. whether it is a master record, a transactional record, an archive, or a reference data set.
Examples:
- "The canonical customer master record held in the CRM. Covers all active and archived customer accounts. Excludes prospect records, which are held in the Marketing platform (DSet-7)."
- "The JSON event payload published to the order-created topic on the event stream when a new order is placed. Consumed by the fulfilment service and the data warehouse ingestion pipeline."

Group	Options
Relational	Relational Tables · Relational Tables (Geospatial) · Relational Star Schema
Other databases	Structured Documents · Graph Databases · Key-Value Stores
Files	CSV · JSON · XML · Text · Excel · Word · PDF · RTF · PNG · JPG · Video · Binary · Parquet · Avro · Delta Lake · Delta Sharing · ORC · GeoDB · Other
Message Payloads	Message Payload: JSON · Message Payload: XML · Message Payload: Text · Message Payload: Binary
API contracts	API: JSON · API: XML · API: CSV · API: Text · API: Binary
Other	Other

Guidance: Choose the structure that best represents the technical nature of this data. The structure type communicates how the data is stored or transmitted and guides how the data model entities should be interpreted — e.g. Relational Tables implies entities map to database tables with columns and foreign keys; API: JSON implies entities map to JSON object schemas with properties and nested objects.

Relationship	What to link
Contains Business Information	Business Information items that this Data Set is the technical implementation of; provides the bridge between business-level information and the data structures that support it
Has Implementation Acceptance Criteria	Technical acceptance criteria for verifying this Data Set is correctly designed and implemented
Has Test Data	Test data sets used to populate and validate this Data Set during development and testing
Supports Business Requirement	Business Requirements that this Data Set is needed to satisfy
Has Risk	Risks associated with this Data Set — data quality risk, schema instability, volume risk
Has Assumption	Assumptions made about this Data Set (e.g. assumed structure, assumed ownership, assumed data quality)
Has Issue	Known issues affecting the definition or implementation of this Data Set
Has FAQ	Frequently asked questions about this Data Set
Has Task	Tasks assigned to this Data Set (e.g. data modelling work, schema sign-off, data quality investigation)
Implements Business Reference	Standards, policies, or regulatory documents that govern this Data Set (e.g. data retention policy, GDPR, industry data standards)