On this page
Dataset token reference
Look up the semantic token values supported by Trazadera Golden dataset columns.
A dataset column token describes the value’s semantics, not only its storage
shape. The values below belong to the documented Golden release. The resources
enums endpoint supplies configured references and roles, not this static
token vocabulary.
| Family | Token values |
|---|---|
| Country and language | COUNTRY_CODE, COUNTRY_NAME, LANGUAGE |
| Phone | PHONE_COUNTRY_CODE, PHONE_NUMBER, PHONE |
| Name | NAME_PREFIX, NAME_FIRST, NAME_MIDDLE, NAME_LAST, NAME |
| Address | ADDRESS_STREET_TYPE, ADDRESS_STREET_NAME, ADDRESS_NUMBER, ADDRESS_STREET, ADDRESS_CITY, ADDRESS_POSTCODE, ADDRESS_STATE, ADDRESS |
| Geographic | GEO_LONGITUDE, GEO_LATITUDE, GEO_COORDINATES |
| Identity and common values | ID, FOREIGN_ID, EMAIL, NUMBER, DATE, ENUM, URL |
| Text | TEXT, TEXT_AS_IS |
| Excluded value | IGNORE |
Use GEO_COORDINATES for a coordinate pair in longitude-and-latitude order.
Use TEXT_AS_IS only when the value must retain its supplied text treatment.
IGNORE declares that Golden should not treat the column as a managed semantic
value.
SOURCE is retired. Use a mandatory ENUM column with enumerations for a
business value that identifies a source system. Existing SOURCE columns are
converted to mandatory ENUM columns when Golden updates their stored
definitions. Record provenance remains in _source: _src names the source
system and _src_id identifies the record there. Neither is a SOURCE token.