The documents are returned sorted on relevance depending on order, proximity, frequency of terms.
Default search behavior
By default, all search terms are optional. It behaves like an OR logic. Objects that contain the more terms are rated higher in the results and will appear first in their type. For example, wiki forum will find:
- objects that include both terms
- objects that include the term wiki
- objects that include the term forum
Requiring terms
Add a plus sign ( + ) before a term to indicate that the term must appear in results. Example: +wiki forum will find objects containing at least wiki. Objects with both terms and many occurences of the terms will appear first.
Excluding terms
Add a minus sign ( - ) before a term to indicate that the term must not appear in the results. To reduce a term's value without completely excluding it, use a tilde. Example: -wiki forum will find objects that do not contain wiki but contain forum
Grouping terms
Use parenthesis ( ) to group terms into subexpressions. Example: +wiki +(forum blog) will find objects that contain wiki and forum or that contain wiki and blog in any order.
Finding phrases
Use double quotes ( " " ) around a phrase to find terms in the exact order, exactly as typed. Example: "Alex Bell" will not find Bell Alex or Alex G. Bell.
Using wildcards
Add an asterisk ( * ) after a term to find objects that include the root word. For example, run* will find:
- objects that include the term run
- objects that include the term runner
- objects that include the term running
Reducing a term's value
Add a tilde ( ~ ) before a term to reduce its value indicate to the ranking of the results. Objects that contain the term will appear lower than other objects (unlike the minus sign which will completely exclude a term). Example: +wiki ~forum will rate an object with only wiki higher that an object with wiki and forum.
Changing relevance value
Add a less than ( < ) or greater than ( > ) sign before a term to change the term's contribution to the overall relevance value assigned to a object. Example: +wiki +(>forum < blog) will find objects that contain wiki and forum or wiki and blog in any order. wiki forum will be rated higher.
OGC 06-131r6 & OGC 06-141
Hello!
Could you please explan which services should be used together to provide catalogue with ordering feature?
We've implemented EOLI service some time ago, but for now it seems to be outdated. If I not mistaken, state of the art interfaces are OGC (draft or approved) standards which are developed within HMA project? Correct me, if not.
We've tried to implement OGC 06-141 for data order but eventualy it appeared to be not compatible with EOLI (due to some SSE Portal issues). So, we've decided to implement modern interfaces both for catalogue and ordering.
06-131r6 looks like perfect choice for catalogue, being approved as OGC standart recently. Infortunately, I was unable to register one together with OGC 06-141. It looks like a bug: when I try to add 06-141 to 06-131r6 Portal "forgets" that I've registred last one. Also, it becomes disabled in the list of the interfaces available when I go there next time.
The exact interfaces I mean are:
Order Interface: OGC 06-141 v1.0.4 Draft, Ordering Services for Earth Observation ProductsThe other facet of the problem is the SSE Toolbox DE. Some test requests for OGC 06-141 are invalid. While 06-131r6 isn't supported by TDE at all. Browsing the installation folder I've discovered templates and the stuff for more interfaces. They don't appear in the Toolbox for some reason.
We would be thankful for any information that could make things clear. Thanks for reading this anyway
Regards,
Ilya Nedoluzhko