search API query

Hi,

Im using the search service to search for items on LL 9.7.1

SingleSearchRequest query = new SingleSearchRequest();
                query.DataCollectionSpec = "'Enterprise'";               // use the Enterprise search slice
                query.QueryLanguage = "Livelink Search API V1";         // use the Search API for queries
                query.FirstResultToRetrieve = 1;                        // start retrieving results at Result #1
                query.NumResultsToRetrieve = 50;                         // retrieve up to 5 search results
                query.ResultOrderSpec = "sortByRegion=OTCreatedBy";     // sort by the OTCreatedBy region
                query.ResultSetSpec = "modifier1=wordbeginswith&modifier2=OTName&where1=" + whereClause;          // set the where clause of the query
                query.ResultTransformationSpec = new string[] { "OTDataID", "OTLocation", "OTName" };

i need to know how to write a query that would return me all folder starting with a particular value

eg: all folders starting with '1/1/1 - ' in the name

thanks in advance

Zak

Find more posts tagged with

Comments

shaik_zakariah

I managed to find this query <

OTName> prox[1,T] qlregex "^1/1/1 - ".

What I'm trying to do is return all folders with the starting with "1\1\1 - ". but whats happening is I am getting folders with names = "1\1\1\1" and "1\1\1\2". How can I rewrite this query to only retrieve "1\1\1 - " note the dash( - ) is part of the name and denotes a unique folder.

thanks

Zak

Kyle_Swidrovich

Hi Zak,

The difficulty you are experiencing is due to the way that strings are tokenized within search/indexing.

The dash is not normally considered to be a part of a “word” or “token”. The same goes for a backslash character.

They are typically dropped.

With that in mind, “1\1\1 -“ and “1\1\1\1” are very similar, as far as search is concerned.

They would be viewed as “1 1 1” and “1 1 1 1”.

So if you search for things starting with “1 1 1”, you would match on both.

Changing the tokenizer to include the “-“ in a word is simple enough to do, but requires reindexing everything in your system as the data would need to be reevaluated with the new tokenization rules.

However, keep in mind that this also changes things like “1-2-3” and “April-2009-Document.doc”. With that tokenization in place, searching for “2” or “April 2009” would not match.

To implement the “dash as a part of a word” logic, you need to modify the search.ini directives.

The way to do this differs between versions of the search engine.

In all cumulative patch versions of 9.7.0 and in all cumulative patch versions <= 09-2010 for 9.7.1, you need to modify the search.ini file.

If you are running the latest November 2010 Update 1 cumulative patch (or future patch), you would have had installed Search Engine 10 Update 1 as a necessity in Content Server 9.7.1.

So for cumulative patch versions Update 1+ for 9.7.1 and all versions of CS 10, you should be taking advantage of the search.ini_override file.

Documentation on this search.ini_override file is available in the Champion Toolkit area of the Knowledge Center and also in accompanying documentation for the Nov 2010 Update 1 cumulative patch for 9.7.1.

In the appropriate file, you need to specify the following in the the [DataFlow...] section for your Enterprise data source:

TokenizerOptions=1

This change should be made with services stopped.

And again, after this change, a full reindex is required.

Other available options are:

TokenizerOptions=

0 => normal tokenization

1 => "-" becomes part of stdword (standardword)

2 => XML Comments are indexed.

4 => enable the functionality that will treat an underscore as a word separator

8 => Version numbers, like V2.0 can be indexed as tokens.

If you wish to combine options, simply add them together.

For example,

3 ==> options 1 & 2

6 ==> options 2 & 4

7 ==> options 1 & 2 & 4

One other thing I’d like to mention is that you may find it easier to work directly with the XML Search API rather than the SearchService web service.

The data structures coming back from the SearchService are quite complex (graph theory based) whereas the XML Search API can provide a structure similar to what the search results page looks like.

It’s probably easier to parse.

Please see the Search API documentation for more information, provided in the Documentation area for Content Server.

Here’s a link to the 9.7.1 version:

https://knowledge.opentext.com/knowledge/llisapi.dll/Properties/15084344

Regards,

Kyle

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: March-01-11 9:31 AM
To: eLink Recipient
Subject: search API query

search API query

Posted by zshaik@datacentrix.co.za (Shaik , Zakariah) On 2011/03/01 09:28

I managed to find this query <

OTName> prox[1,T] qlregex "^1/1/1 - ".

thanks

Zak

[To post a comment, use the normal reply function]
Topic:	search API query
Forum:	Content Web Services Forum
Livelink Server:	knowledge-wlweb01

shaik_zakariah

Hi Kyle,

Thanks for this, however reindexing at this point is not an option for our client.

im using the following query to return all forders that start with '2/2/1':

query.ResultSetSpec = "lookfor1=complexquery&where1=(<OTName> prox[1,T] qlregex "^2/2/1")";

I am aware that livelink doesnt recognise the '/' but am i correct in asuming that the above query would return all folders that start with '2/2/1'?, because I am also getting folders with 2/2/1 in it e.g. 3/2/2/1. How can i rewrite this query to return only folders that start with 2/2/1

thanks in advance

Zak

Kyle_Swidrovich

Hey Zak,

Just take out your prox + qlregex directive.

<OTName>2/2/1 will look for names starting with 2/2/1.

BTW, qlregex only works on a per-token basis... not on phrases.

Kyle

shaik_zakariah

Hi Kyle,

Thanks for this, changing the query and running it in livelink directly gets me the results, coolio! but, I know this might sound like a dumb question, how do I write it for the ResultSetSpec property for the search api...I've tried this:query.ResultSetSpec = "where1=(<OTName>2/2/1)"; and query.ResultSetSpec = "lookfor1=complexquery&where1=(<OTName>2/2/1)"; both dont seem to work...please help.

thanks in advance

zak

Kyle_Swidrovich

Hi Zak,

Sorry... forgot to clarify that you need to encapsulate it in quotes.
So, where1="<OTName>2/2/1" should be what is used.
Depending on the language, you'll need to handle embedding double quotes in the string a certain way.

Cheers,
Kyle

shaik_zakariah

ahh perfect...that did the trick. Thanks Kyle