Skip to main content
Data objects and data attributes provide a structured data layer within KDDB documents. Data objects represent extracted entities (e.g., an invoice line item, a person, an address), while data attributes store the individual fields and values associated with those entities.

Overview

The data layer is separate from the content node tree and designed for storing extraction results:
  • Data Objects: Entities with parent-child relationships and taxonomy references
  • Data Attributes: Typed fields attached to data objects (string, decimal, date, boolean)
  • Confidence Scores: Each attribute can have an extraction confidence score
  • Taxonomy Integration: Objects and attributes can reference taxonomy definitions

Data Objects

Creating Data Objects

Retrieving Data Objects

Updating and Deleting Data Objects

Data Attributes

Creating Data Attributes

Retrieving Data Attributes

Updating Data Attributes

Batch Writes

Document.batch_transaction() queues data object and attribute operations and applies them in a single atomic call. Operations inside a transaction carry the same payload as the direct accessors: a created attribute persists its value, tag_id, data_features, confidence and timestamps, and formulas that depend on an attribute the transaction creates or updates are recalculated. See Transactions for the full API.

DataObjectInput Reference

DataAttributeInput Reference

Accepted date formats. dateValue is parsed flexibly, so you do not have to pre-format dates: RFC 3339 (2024-01-15T00:00:00Z), a date-time with no timezone (2024-01-15T15:04:05), a bare ISO date (2024-01-15), month-name forms (2026-Mar-01, 1-Jan-2025) and US numeric forms (04-30-2025, 1-2-2026) all resolve to a stored date. Numeric dash dates are read as month-day-year. A string that cannot be parsed leaves the attribute’s stored date unchanged rather than writing a wrong one.

Complete Example