"Something like:$("myinput").freebaseSuggest({ filter: function(data,..."
Freebase search currently supports a subset of the Lucene search syntax.
Supported
- Single term and phrase term are supported. A phrase term is just a quoted string, such as "Brave New World"
- Wildcard search is supported for terms greater than two characters. This includes single character wildcard as well ("ba?l" would match "bail" and "ball").
- Fuzzy search for single word term is supported. You can add a tilda to indicate "fuzziness" for a word. So "roam~" may also match for "yoam" or "rolm". It does not support a fuzziness parameter after the tilda.
- Term boosting is supported, but because queries are forced to be boolean AND queries (see below), this doesn't make too much difference. This makes more sense in a boolean OR search which's lucene's default action for a multi-termed search. This is done by appending a caret and a number to the end of a single term, like "robert^10 cook".
Not supported
- Boolean search is not supported. Boolean operators are quoted out: "and", "or" and "not" and all queries are converted into a boolean AND search. This allows the user to search for names containing these terms without worrying about escaping them.
- Grouping is not supported, or is not applicable since all terms are AND'ed together.
- Field specification is disabled. This is the feature where you can specify which field to search over. The fields a user can search on are prespecified (display name, article, or a single data field) so this doesn't make sense to support.
- Field grouping is not supported since fielded search isn't supported.
- Proximity search is the phrase term version of fuzzy search. This is not currently supported.
- Range search is not supported, because it depends on specifying the field to search, and it doesn't make sense for the field being searching on.
