Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

Expose more full-text search controls to the API #49

Open
abargnesi opened this issue Feb 25, 2015 · 0 comments
Open

Expose more full-text search controls to the API #49

abargnesi opened this issue Feb 25, 2015 · 0 comments

Comments

@abargnesi
Copy link
Member

Derived from #45 #47

The FTS search filter is used like:

http://next.belframework.org/api/annotations/values?filter={"category":"fts","name":"search","value":"mandible"}

http://next.belframework.org/api/evidence?filter={"category":"fts","name":"search","value":"Approved"}

The syntax for the full-text search filter passes through to the implementation:

  • annotations/namespaces uses SQLite fts4 and wraps each word like *word*
  • evidence uses Mongo FTS and is passed through unmodified

We should provide a consistent API across all FTS filters. This might include:

  • Specifying AND (conjunction) or OR (disjunction).
  • Wildcard search
  • Exact match
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant