I think you may want to look at the word query configuration to include/exclude elements:
http://docs.marklogic.com/guide/admin/wordquery#id_77008 John On Thu, Oct 17, 2013 at 6:52 AM, Erik Hennum <erik.hen...@marklogic.com>wrote: > Hi, Gnana: > > Can you provide more detail about what you're trying to accomplish? > > I'm wondering with the requirements can be met through booleans in > structured search: > > http://docs.marklogic.com/guide/search-dev/structured-query#id_83674 > http://docs.marklogic.com/guide/search-dev/structured-query#id_65108 > > To set a scope in string search, you can use the equivalent cts:* queries > in: > > http://docs.marklogic.com/search:search#opt-additional-query > > > Hoping that helps, > > > Erik Hennum > > ------------------------------ > *From:* general-boun...@developer.marklogic.com [ > general-boun...@developer.marklogic.com] on behalf of > gnanaprakash.bodire...@cognizant.com [gnanaprakash.bodire...@cognizant.com > ] > *Sent:* Thursday, October 17, 2013 12:57 AM > *To:* general@developer.marklogic.com > *Subject:* [MarkLogic Dev General] Defining The Search Scope > > Hi > > > > Is there any way to include/exclude set of elements in a fragment while > searching? > > > > For example: > > > > <root> > > <element1/> > > <element2/> > > ……. > > <element10/> > > </root> > > > > While performing search (REST API based), I want my search (keyword or > constraints based) to look into few elements like (element1, element 3, > element4). > > > > What is the best approach to define the scope of search? > > > > Regards, > > Gnana(GP) > > > This e-mail and any files transmitted with it are for the sole use of the > intended recipient(s) and may contain confidential and privileged > information. If you are not the intended recipient(s), please reply to the > sender and destroy all copies of the original message. Any unauthorized > review, use, disclosure, dissemination, forwarding, printing or copying of > this email, and/or any action taken in reliance on the contents of this > e-mail is strictly prohibited and may be unlawful. > > _______________________________________________ > General mailing list > General@developer.marklogic.com > http://developer.marklogic.com/mailman/listinfo/general > >
_______________________________________________ General mailing list General@developer.marklogic.com http://developer.marklogic.com/mailman/listinfo/general
