Dates, Value Ranges, and Structured Fields
VagueDate
Use VagueDate when you know a date only approximately or at limited precision. Enter natural date text accepted by the date parser, such as a year or a more precise date. The field validates and canonicalizes recognized input while retaining its precision for sorting. Choose this for a single point in time, such as a document date or memory date.
VagueDateRange
Use VagueDateRange for a span or period, including uncertain endpoints. It accepts a human-readable date-range expression, validates it, and stores the range with a sort value. Treasure uses it for Date Acquired, Date Appraised, and Date Made. Choose VagueDate when you mean one date and VagueDateRange when you mean a period.
VagueValue
Use VagueValue for an amount that may be approximate or expressed as a range. Examples include $500, €100-€200, and > £1000. The field captures numeric bounds and currency. It is a useful fit for estimated or historical valuations where a single exact number would imply too much certainty.
Composite
A Composite field groups named subfields into one structured value. The Person type's Home Address uses Street Address, Address Line 2, City, State/Province, Postal Code, and Country. A display template controls how the parts are combined in compact views. Composite fields are more structured than a single text field and are useful when users may want to search or reuse individual parts.
PhoneNumber
PhoneNumber provides a phone-specific input and normalization. Values are stored in international E.164 form; the current parser accepts US-style numbers, including a leading country code. For example, (555) 123-4567 is normalized to +15551234567.