Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
← Back to post

Revisions 2

Enrollment via Unauthenticated Extension
Enrollment via Unauthenticated Extension
Great question Mark! It sparked some good conversation withinthe Q2 team. The only hesitation with saying The Caliper API is due to the network effect you mentioned. However we don't really like making you recreate all the steps that enrollment endpoint on the API covers for you either (for all the reasons you mentioned). Use the Caliper API endpoint at this time and perhaps we will begin work on making that workflow a common object that could be utilized by both the API and our SDK users like yourself without the additional network requirment.
Great question Mark! It sparked some good conversation within the Q2 team. The only hesitation with saying The Caliper API is due to the network effect you mentioned. However, we don't really like making you recreate all the steps that enrollment endpoint on the API covers for you either (for all the reasons you mentioned). Use the Caliper API endpoint at this time and perhaps we will begin making a workflow object that could be utilized by both the API and our SDK users without the additional network requirement.
one year ago
Enrollment via Unauthenticated Extension

Great question Mark! It sparked some good conversation within the Q2 team. The only hesitation with saying The Caliper API is due to the network effect you mentioned. However, we don't really like making you recreate all the steps that enrollment endpoint on the API covers for you either (for all the reasons you mentioned). Use the Caliper API endpoint at this time and perhaps we will begin making a workflow object that could be utilized by both the API and our SDK users without the additional network requirement.