[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-139) New system query option $search for free-text search within an entity set
[ http://tools.oasis-open.org/issues/browse/ODATA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32006#action_32006 ]
Stefan Drees commented on ODATA-139:
------------------------------------
I really like the storage model agnostic offering of a search capability, where the server MAY do a lot of lookups and thus satisfice the clients commander (a human being possibly just in an explorative seek). This should render the protocol in itself even more useful than just something being somehow non-relational sitting mostly on top of a relational store and denying to answer "broad queries", that might not be servable by each and every type of possible backend stores.
Can we try to "fill in" some answers for the questions raised by [Mike's comment from 28/Nov/12 06:13 PM](https://tools.oasis-open.org/issues/browse/ODATA-139?focusedCommentId=31847&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_31847) and left open until now?
> New system query option $search for free-text search within an entity set
> -------------------------------------------------------------------------
>
> Key: ODATA-139
> URL: http://tools.oasis-open.org/issues/browse/ODATA-139
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData ABNF Construction Rules v1.0, OData Protocol v1.0, OData URL Conventions v1.0
> Affects Versions: WD01
> Reporter: Ralf Handl
> Fix For: WD01
>
>
> Searching a list of entries by entering a free-text search phrase in a single input field is a very common UI pattern in mobile and browser-based applications.
> Translating this (typically case-insensitive) search phrase into an OData filter string is cumbersome and error-prone.
> A better alternative is providing a specialized query option that takes a search term and allows the server to interpret this search term.
> GET ~/Orders?$search=blue
> could return sales orders that somehow match the phrase "blue", without the client needing to specify where this phrase may occur. It even could appear in related entities, e.g. the description of one of the products ordered.
> This is comparable to Level 0 Conformance in CQL, see ODATA-3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]