Need a little bit more help with search in EWS

I'm currently working with the search-part of the EWS and i'm running out of time. Hope someone can give me some help so that i hopefully can finish my work today.

I've managed to find documents now by using the following ResultSetSpec "where1=\"OTCreateDate\" : qlrange \"20100619~20100715\""

What i need now is either an answer if the following things is possible or how to supply it as a ResultSetSpec-string:

1. Who created the document. Is it possible to search by firstname and lastname(seemed like it was only possible to search by username).

2.File description

3.Include search for both folders and documents

4.Searching within a specific location specified with "/folder1/folder2"

5.Category descriptions and values

6. How to supply all of the above in one searchstring.

Hope someone can help me out because i don't have time to experiment with the querystring any more.

Thanks in advance.

Find more posts tagged with

Comments

sgrasley

It might be worth posting search-specific questions in the in the Search and Indexing Discussion, but I'll do my best to answer.

1. Who created the document. Is it possible to search by firstname and lastname(seemed like it was only possible to search by username).

OTCreatedByFullName might be the region you're looking for. I think you'll have to mark it as queryable (and displayable if you want to return it).

2.File description

The region OTDComment contains the description.

3.Include search for both folders and documents

By default both folders (OTSubType 0) and documents (OTSubType 144) will be searched. If you want to include only those subtypes, then use where1=[qlregion OTSubType] qlrange "0|144"&lookfor1=complexquery

4.Searching within a specific location specified with "/folder1/folder2"

The region OTLocation contains the patch to the document using IDs (e.g. "2000 2345 3456").

5.Category descriptions and values

On the Search Manager's Regions page, you'll see regions like Attr_####_# representing category attributes, provided Show In Search has been checked for that attribute and content has been indexed with that attribute applied. I believe there are other topics in this forum that will be helpful for this.

6. How to supply all of the above in one searchstring.

You can specify multiple criteria using "where1=clause&boolean2=and&where2=another clause"

Thanks,

Scott

Andre_Sovde

Quoted Scott Grasley (sgrasley) on 2010/07/19 17:11:

6. How to supply all of the above in one searchstring.

You can specify multiple criteria using "where1=clause&boolean2=and&where2=another clause"

And if i want to search for anything that begins with a certain string i supply it in the querystring like this?

"where1=clause&modifier1=wordbeginswith&boolean2=and&where2=another clause&modifier2=wordendswith"

If i've understood the manuals correctly, the modifier1 applies only to the where1 clause and the modifier2 applies only to the where2 clause?

sgrasley

Hi, Andre.

Yes, modifier1 applies to where1 only, etc.

Thanks,

Scott

Andre_Sovde

Thanks for the help. I'm starting to understand how to create searchstrings a little bit more. I'm currently trying out the following querystring:

query.ResultSetSpec = "where1=(OTName : \"Zapo\")&modifier1=\"wordbeginswith\"&boolean2=and&where2=([qlregion OTSubType] : qlrange \"0\")&lookfor2=complexquery\"";

I'm not able to make this work for some reason. I've also tried:

query.ResultSetSpec = "where1=([qlregion OTSubType] : \"0\")&lookfor1=\"complexquery\"&boolean2=and&where2=(OTName : \"Zapotec\")&modifier2=\"wordbeginswith\"";

Can you see what's wrong with this query?

sgrasley

Hi, Andre.

I think your first query is missing &lookfor1=complexquery and the second one is missing &lookfor2=complexquery.

Try "where1=[qlregion OTName] Zapo&lookfor1=complexquery&modifier1=wordbeginswith&boolean2=and&where2=[qlregion OTSubType] 0&lookfor2=complexquery"

Generally, I don't think you need to embed quotes unless you're using something like the qlrange operator: "where1=[qlregion OTSubType] qlrange \"0|144\"&lookfor1=complexquery".

Thanks,

Scott