nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Retrieve file path from Search Service

Tim Boyle

Hi,

I am currently using the SearchService to return a list of files from a specific root folder. When I return the results, I am including variables such as OTName, OTFileName, OTLocation, etc... What I am trying to figure out is if there is a way to return the actual Location of the file as:

instead of returning only the DataIds ( 2000 12344 23453), which is what I receive with the OTLocation variable.

Thanks,
Tim Boyle
Nanavati Consulting

Find more posts tagged with

Comments

Kyle_Swidrovich

Hi Tim,

Not from the SearchService web service.

If you use the RESTful Search API directly (?func=search, with &outpuformat=xml for programmatic use), you’ll see a synthesized OTLocationPath region that should provide you with the information you’re looking for.

Keep in mind that since container names can be similar across different volumes, the OTLocationPath data really just provides an easy cosmetic representation.

Regards,

Kyle

Kyle_Swidrovich

Actually, I checked with dev and it looks like that OTLocationPath will come back via the SearchService, as long as you have asked for OTLocation in the ResultTransformationSpec.

Tim Boyle

Kyle,

Currently, my query is set up like the following in C#:

string whereClause = searchCriteria.Text;   //This comes from form field
string docType = ConfigurationManager.AppSettings["docType"].ToString(); //Currently set to only return docs type 144
string rootFolder = ConfigurationManager.AppSettings["rootFolder"].ToString(); // Currently set to Enterprise Root 2000

SearchService.SingleSearchRequest query = new SearchService.SingleSearchRequest();
                query.DataCollectionSpec = "'LES Enterprise'";
                query.QueryLanguage = "Livelink Search API V1";
                query.FirstResultToRetrieve = 1;
                query.NumResultsToRetrieve = 500;
                query.ResultOrderSpec = "sortByRegion=OTFileName";
                query.ResultSetSpec = "where1=\"OTLocation\":" + rootFolder + " AND \"OTSubType\":" + docType + " AND " + whereClause;
                query.ResultTransformationSpec = new string[] { "OTName", "OTLocation", "OTLocationPath", "OTDataID", "OTSubType", "OTMIMEType", "OTDComment", "Attr_14093_6", "Author", "OTCreateDate", "OTFileName" };

I have gone into the regions of the Enterprise Search Manager, and set the desired items to Queryable, Displayable, and Search By
Default. However I do not see an OTLocationPath

My results are coming back looking like the following:

Search Results: 1 to 2 of about 2

Item #1 (ID=DataId=21243&Version=1):
      Attr_14093_6=
      Author=Admin
      OTDataID=21243
      OTDComment=?
      OTFileName=WEEK4.pdf
      OTLocation=2000 14094 21133 21243
      OTLocationPath=
      OTMIMEType=application/pdf
      OTName=Tim Week 4 picks
      OTSubType=144
      OTCreateDate=10/5/2012 @ 12:00 AM

Item #2 (ID=DataId=21353&Version=1):
      Attr_14093_6=Just jotting down some notes
      Author=Admin
      OTDataID=21353
      OTDComment=Tim in the Description
      OTFileName=TIMWEEK5.pdf
      OTLocation=2000 14094 21353
      OTLocationPath=
      OTMIMEType=application/pdf
      OTName=This is a PDF test
      OTSubType=144
      OTCreateDate=10/5/2012 @ 12:00 AM

As you can see, the OTLocation is there, but nothing for OTLocationPath. Can you lend any further insight?

Thanks,

Tim

Kyle_Swidrovich

Hi Tim,

As I noted, the OTLocationPath is synthesized – it’s not an actual region in the index. That’s why it won’t show up on the Regions tab of the Enterprise Search Manager.

What version + update of Content Server are you hitting with your request?

Kyle

Tim Boyle

Kyle,

We are using Content Server 10 Update 5 (version 10.0.0.1949)

Thanks,
Tim

Tim Boyle

Kyle,

Just wanted to check and see if you had any further information as to why the field is not returning data for me.

Thanks,

Tim

Tim Boyle

Kyle,

Any further word on why OTLocationPath might not be returning a value?

Thanks,

Tim

Quoted kswidrov@opentext.com on 2012-10-24 07:43:

Hi Tim,

As I noted, the OTLocationPath is synthesized – it’s not an actual region in the index. That’s why it won’t show up on the Regions tab of the Enterprise Search Manager.

What version + update of Content Server are you hitting with your request?

Kyle

Kyle_Swidrovich

Hi Tim,

I just stepped through our Oscript code and although the Search API is internally returning a location path string for each search hit, it’s not being mapped into an OTLocationPath region before it’s sent back to the web service from Content Server.

The Oscript side of web services appears to only provide result metadata for regions marked as Displayable by the administrator in the Regions tab of the Enterprise Search Manager.

This means that virtual regions (like OTLocationPath) can’t currently be retrieved through web services.

I’ve notified development and the PM of this behaviour.

Regards,

Kyle

Kyle_Swidrovich

Our R&D group has responded.

This behaviour is to spec. Search Services was designed to only bring raw region data back.

If you want additional Content Server context, you'll need to use the RESTful Search API (?func=search).

More information on that API can be found in this community:
https://knowledge.opentext.com/knowledge/cs.dll/Open/16579994

Regards,
Kyle