marklogic-fasttrack

MarkLogic FastTrack

FastTrack is a React component library over MarkLogic's Search API. The UI is driven almost entirely by a stored search options set — get that right and the components mostly configure themselves.

Order of work

1. Confirm the indexes exist (ml_indexes_list). Every facet constraint needs one.
2. Write the search options and store with ml_search_options_put.
3. Verify server-side with ml_search before touching React.
4. Scaffold the React app.

Skipping step 3 is the usual reason a FastTrack UI shows no facets — the options set was rejected or the index is missing, and the component just renders empty.

Constraint index rules

Prefer path indexes. For JSON content, a path-index with path //fieldName uses a range-path-index, creatable via admin:database-add-range-path-index through ml_eval_xquery.

json-property is the fallback — it needs a range-json-property-index, which is only creatable through the Management API on port 8002.

// string facet
{"name":"field","range":{"type":"xs:string","facet":true,"path-index":{"text":"//field"}}}

// numeric facet
{"name":"field","range":{"type":"xs:decimal","facet":true,"path-index":{"text":"//field"}}}

// date facet (with buckets)
{"name":"field","range":{"type":"xs:date","facet":true,"path-index":{"text":"//field"}}}

Dates stored as ISO strings (YYYY-MM-DD) should use xs:string, not xs:date — ISO strings sort chronologically, and this avoids a cast that will fail on any malformed value.

Geospatial (map widget) — a geo-elem-pair constraint with parent/lat/lon. Only add it if the schema actually has geo fields.

⚠ Bucket syntax: name, not label

CORRECT: {"name":"Under 80k","lt":"80000"}
CORRECT: {"name":"80-100k","ge":"80000","lt":"100000"}
WRONG:   {"label":"Under 80k","lt":"80000"}

label produces XDMP-VALIDATEMISSINGATTR and a 400 from the REST API. Every bucket needs a name.

Options skeleton