Search service - No results when multiple terms are concatenated

Hi,

I am faced with a strange problem. Months ago I used the following query and the result was correct, but for some time now the "AND" operator seems to no longer work between search term.

If I execute the following search request, the result is correct:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:SearchServices.service.livelink.opentext.com">
<soapenv:Header>
<urn:OTAuthentication>
   <urn:AuthenticationToken>TOKEN</urn:AuthenticationToken>
</urn:OTAuthentication>
</soapenv:Header>
<soapenv:Body>
<urn1:Search>
<urn1:queries>
   <urn1:DataCollectionSpec>'LES Enterprise'</urn1:DataCollectionSpec>
   <urn1:FirstResultToRetrieve>1</urn1:FirstResultToRetrieve>
   <urn1:NumResultsToRetrieve>100</urn1:NumResultsToRetrieve>
   <urn1:QueryLanguage>Livelink Search API V1</urn1:QueryLanguage>
   <urn1:ResultOrderSpec></urn1:ResultOrderSpec>
   <urn1:ResultSetSpec>where1="OTDCategory":1212536</urn1:ResultSetSpec>
   <urn1:ResultTransformationSpec>OTName</urn1:ResultTransformationSpec>
   <urn1:ResultTransformationSpec>OTMIMEType</urn1:ResultTransformationSpec>
      <urn1:ResultTransformationSpec>OTSubType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTDCategory</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTFileType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTLocation</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTObject</urn1:ResultTransformationSpec>
</urn1:queries>
</urn1:Search>
</soapenv:Body>
</soapenv:Envelope>

The following search result is correct:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:SearchServices.service.livelink.opentext.com">
<soapenv:Header>
<urn:OTAuthentication>
   <urn:AuthenticationToken>TOKEN</urn:AuthenticationToken>
</urn:OTAuthentication>
</soapenv:Header>
<soapenv:Body>
<urn1:Search>
<urn1:queries>
   <urn1:DataCollectionSpec>'LES Enterprise'</urn1:DataCollectionSpec>
   <urn1:FirstResultToRetrieve>1</urn1:FirstResultToRetrieve>
   <urn1:NumResultsToRetrieve>100</urn1:NumResultsToRetrieve>
   <urn1:QueryLanguage>Livelink Search API V1</urn1:QueryLanguage>
   <urn1:ResultOrderSpec></urn1:ResultOrderSpec>
   <urn1:ResultSetSpec>where1="Attr_1212536_3":Informatica</urn1:ResultSetSpec>
   <urn1:ResultTransformationSpec>OTName</urn1:ResultTransformationSpec>
   <urn1:ResultTransformationSpec>OTMIMEType</urn1:ResultTransformationSpec>
      <urn1:ResultTransformationSpec>OTSubType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTDCategory</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTFileType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTLocation</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTObject</urn1:ResultTransformationSpec>
</urn1:queries>
</urn1:Search>
</soapenv:Body>
</soapenv:Envelope>

But if I try to merge the two request with the following query:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:SearchServices.service.livelink.opentext.com">
<soapenv:Header>
<urn:OTAuthentication>
   <urn:AuthenticationToken>TOKEN</urn:AuthenticationToken>
</urn:OTAuthentication>
</soapenv:Header>
<soapenv:Body>
<urn1:Search>
<urn1:queries>
   <urn1:DataCollectionSpec>'LES Enterprise'</urn1:DataCollectionSpec>
   <urn1:FirstResultToRetrieve>1</urn1:FirstResultToRetrieve>
   <urn1:NumResultsToRetrieve>100</urn1:NumResultsToRetrieve>
   <urn1:QueryLanguage>Livelink Search API V1</urn1:QueryLanguage>
   <urn1:ResultOrderSpec></urn1:ResultOrderSpec>
   <urn1:ResultSetSpec>where1="OTDCategory":1212536 AND "Attr_1212536_3":Informatica</urn1:ResultSetSpec>
   <urn1:ResultTransformationSpec>OTName</urn1:ResultTransformationSpec>
   <urn1:ResultTransformationSpec>OTMIMEType</urn1:ResultTransformationSpec>
      <urn1:ResultTransformationSpec>OTSubType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTDCategory</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTFileType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTLocation</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTObject</urn1:ResultTransformationSpec>
</urn1:queries>
</urn1:Search>
</soapenv:Body>
</soapenv:Envelope>

The result contains 0 items:

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header>
<OTAuthentication xmlns="urn:api.ecm.opentext.com">
<AuthenticationToken>TOKEN</AuthenticationToken>
</OTAuthentication>
</S:Header>
<S:Body>
<SearchResponse xmlns="urn:SearchServices.service.livelink.opentext.com">
<SearchResult>
<ResultAnalysis>
<ID>Map from Region Names to Display Names</ID>
<N>
<ID/>
<S>Name</S>
<S>MIME Type</S>
<S>Category</S>
<S>File Type</S>
<S>Location</S>
<S>OTObject</S>
<Type>MRD</Type>
</N>
</ResultAnalysis>
<Results>
<ListDescription>
<ActualCount>0</ActualCount>
<IncludeCount>0</IncludeCount>
<ListHead>0</ListHead>
</ListDescription>
</Results>
<Type>
<ID>MRD</ID>
<Strings>OTName</Strings>
<Strings>OTMIMEType</Strings>
<Strings>OTDCategory</Strings>
<Strings>OTFileType</Strings>
<Strings>OTLocation</Strings>
<Strings>OTObject</Strings>
</Type>
</SearchResult>
</SearchResponse>
</S:Body>
</S:Envelope>

How is it possible? If I do the same search using the Content Server Advanced search, the results are correct.

Thank you,

Pamela

Find more posts tagged with

Comments

Riten

Just wondering what happens when you surround Informatica word with double quotes?

Sent from my iPhone

On Feb 19, 2018, at 9:41 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

eLink : Search service - No results when multiple terms are concatenated
Search service - No results when multiple terms are concatenated Posted by pamela.ferrari@lugano.ch (Ferrari, Pamela) On 02/19/2018 09:33 AM

Hi, I am faced with a strange problem. Months ago I used the following query and the result was correct, but for some time now the "AND" operator seems to no longer work between search term.If I execute the following search request, the result is correct:<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:SearchServices.service.livelink.opentext.com">
<soapenv:Header>
<urn:OTAuthentication>
   <urn:AuthenticationToken>TOKEN</urn:AuthenticationToken>
</urn:OTAuthentication>
</soapenv:Header>
<soapenv:Body>
<urn1:Search>
<urn1:queries>
   <urn1:DataCollectionSpec>'LES Enterprise'</urn1:DataCollectionSpec>
   <urn1:FirstResultToRetrieve>1</urn1:FirstResultToRetrieve>
   <urn1:NumResultsToRetrieve>100</urn1:NumResultsToRetrieve>
   <urn1:QueryLanguage>Livelink Search API V1</urn1:QueryLanguage>
   <urn1:ResultOrderSpec></urn1:ResultOrderSpec>
   <urn1:ResultSetSpec>where1="OTDCategory":1212536</urn1:ResultSetSpec>
   <urn1:ResultTransformationSpec>OTName</urn1:ResultTransformationSpec>
   <urn1:ResultTransformationSpec>OTMIMEType</urn1:ResultTransformationSpec>
      <urn1:ResultTransformationSpec>OTSubType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTDCategory</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTFileType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTLocation</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTObject</urn1:ResultTransformationSpec>
</urn1:queries>
</urn1:Search>
</soapenv:Body>
</soapenv:Envelope>  The following search result is correct:<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:SearchServices.service.livelink.opentext.com">
<soapenv:Header>
<urn:OTAuthentication>
   <urn:AuthenticationToken>TOKEN</urn:AuthenticationToken>
</urn:OTAuthentication>
</soapenv:Header>
<soapenv:Body>
<urn1:Search>
<urn1:queries>
   <urn1:DataCollectionSpec>'LES Enterprise'</urn1:DataCollectionSpec>
   <urn1:FirstResultToRetrieve>1</urn1:FirstResultToRetrieve>
   <urn1:NumResultsToRetrieve>100</urn1:NumResultsToRetrieve>
   <urn1:QueryLanguage>Livelink Search API V1</urn1:QueryLanguage>
   <urn1:ResultOrderSpec></urn1:ResultOrderSpec>
   <urn1:ResultSetSpec>where1="Attr_1212536_3":Informatica</urn1:ResultSetSpec>
   <urn1:ResultTransformationSpec>OTName</urn1:ResultTransformationSpec>
   <urn1:ResultTransformationSpec>OTMIMEType</urn1:ResultTransformationSpec>
      <urn1:ResultTransformationSpec>OTSubType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTDCategory</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTFileType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTLocation</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTObject</urn1:ResultTransformationSpec>
</urn1:queries>
</urn1:Search>
</soapenv:Body>
</soapenv:Envelope>  But if I try to merge the two request with the following query:<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:SearchServices.service.livelink.opentext.com">
<soapenv:Header>
<urn:OTAuthentication>
   <urn:AuthenticationToken>TOKEN</urn:AuthenticationToken>
</urn:OTAuthentication>
</soapenv:Header>
<soapenv:Body>
<urn1:Search>
<urn1:queries>
   <urn1:DataCollectionSpec>'LES Enterprise'</urn1:DataCollectionSpec>
   <urn1:FirstResultToRetrieve>1</urn1:FirstResultToRetrieve>
   <urn1:NumResultsToRetrieve>100</urn1:NumResultsToRetrieve>
   <urn1:QueryLanguage>Livelink Search API V1</urn1:QueryLanguage>
   <urn1:ResultOrderSpec></urn1:ResultOrderSpec>
   <urn1:ResultSetSpec>where1="OTDCategory":1212536 AND "Attr_1212536_3":Informatica</urn1:ResultSetSpec>
   <urn1:ResultTransformationSpec>OTName</urn1:ResultTransformationSpec>
   <urn1:ResultTransformationSpec>OTMIMEType</urn1:ResultTransformationSpec>
      <urn1:ResultTransformationSpec>OTSubType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTDCategory</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTFileType</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTLocation</urn1:ResultTransformationSpec>
       <urn1:ResultTransformationSpec>OTObject</urn1:ResultTransformationSpec>
</urn1:queries>
</urn1:Search>
</soapenv:Body>
</soapenv:Envelope>  The result contains 0 items:<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header>
<OTAuthentication xmlns="urn:api.ecm.opentext.com">
<AuthenticationToken>TOKEN</AuthenticationToken>
</OTAuthentication>
</S:Header>
<S:Body>
<SearchResponse xmlns="urn:SearchServices.service.livelink.opentext.com">
<SearchResult>
<ResultAnalysis>
<ID>Map from Region Names to Display Names</ID>
<N>
<ID/>
<S>Name</S>
<S>MIME Type</S>
<S>Category</S>
<S>File Type</S>
<S>Location</S>
<S>OTObject</S>
<Type>MRD</Type>
</N>
</ResultAnalysis>
<Results>
<ListDescription>
<ActualCount>0</ActualCount>
<IncludeCount>0</IncludeCount>
<ListHead>0</ListHead>
</ListDescription>
</Results>
<Type>
<ID>MRD</ID>
<Strings>OTName</Strings>
<Strings>OTMIMEType</Strings>
<Strings>OTDCategory</Strings>
<Strings>OTFileType</Strings>
<Strings>OTLocation</Strings>
<Strings>OTObject</Strings>
</Type>
</SearchResult>
</SearchResponse>
</S:Body>
</S:Envelope>  How is it possible? If I do the same search using the Content Server Advanced search, the results are correct.Thank you,Pamela
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: My Support

Pamela Ferrari

The result is the same: 0 items returned.

AKropp

Hi Pamela,

Parser changes in 16 and 16.2 September updates. Per release notes:

“The behavior when searching for “any words” or “all words” in advanced search has been changed to ignore Boolean operators (such as “and”, “or”, “not”) and treat them as keywords. This makes the behavior consistent with other search operators. Depending on configuration, this may also change the default search bar behavior.”

Reason for change outlined nicely by the PM over here:

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=69431471&objAction=viewincontainer&ViewCommentsByReply&ListView&ListViewID=69463712

Knock on effect is that now you have to be sure to specify Complex Query. Thankfully the service obeys the same kind of syntax as the more modern search APIs despite only allowing a single where. On your resultsetspec, just add &lookfor1=complexquery and it should work fine, i.e.:

<urn1:ResultSetSpec>lookfor1=complexquery&where1="OTDCategory":1212536 AND "Attr_1212536_3":Informatica</urn1:ResultSetSpec>

Would suggest considering the XML or REST APIs for future development if you can. Hope this helps in the meantime.

Cheers,

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, February 20, 2018 1:27 AM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: Re Search service - No results when multiple terms are concatenated

Re Search service - No results when multiple terms are concatenated

Posted bypamela.ferrari@lugano.ch (Ferrari, Pamela) On 02/20/2018 01:24 AM

The result is the same: 0 items returned.

[To post a comment, use the normal reply function]
Topic:	Search service - No results when multiple terms are concatenated
Forum:	Content Web Services Forum
Content Server:	My Support