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; } } }

ApplyQuery

dsta001_dsta001_(dsta001_-_(deleted))

hi all,

In the where clause, there region like OTName , OTLocation. Where do get all these regions, How ur guys knows that there are these regions around.. thanks

Find more posts tagged with

Comments

Kyle_Swidrovich

Hello,

The Admin Help lists a variety of core search regions accompaniedby their descriptions.

A complete list of regions for your particular system can befound on the Regions tab of the properties pages of the Enterprise SearchManager of the Enterprise Data Source Folder in your System Object Volume.

Regards,

Kyle

From: eLink Entry:Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Monday, September 27, 2010 3:10 AM
To: eLink Recipient
Subject: ApplyQuery

ApplyQuery

Posted by dsta001 (dsta001, dsta001) On 2010/09/27 03:07

hi all,

In the where clause, there region like OTName , OTLocation. Where do get all these regions, How ur guys knows that there are these regions around.. thanks

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Livelink Server:	knowledge-wlweb01

dsta001_dsta001_(dsta001_-_(deleted))

Hi,

Thanks for the prompt reply. I have taken a look. In my Enterprise Data Source Folder, the properties page only have General, Categories and Control Rules Tabs. There no regions tabs.

Regards.

dsta001_dsta001_(dsta001_-_(deleted))

Apologies i saw the link.. Thanks

dsta001_dsta001_(dsta001_-_(deleted))

Apologies for multiple reponse. Looking throught he list of regions, can i add in new regions. For example, in the DTree table, there a column name orginDataID. I wish to make that column queryable. IS it Possible Thank

Kyle_Swidrovich

Please review the Admin Help for region settings for more information about changing these.
In short, the columns mean the following:

Search By Default = list of metadata regions for which search terms will be searched against, if a particular region isn't explicitly stated in the query; too many of these will slow down search

Queryable = list of metadata regions that will appear on the Advanced Search page in the System Attributes section; it just makes regions easily selectable in the GUI for end users so they don't have to memorize region names

Displayable = list of metadata regions for whose values a user can request back from the Search grid for every search hit (chosen in the GUI on the Display Options page of the search template); essentially the SELECT part of the query

Sortable = list of metadata regions for which a user can sort the results by (chosen in the GUI on the Display Options of the search template or on the search results page itself)

dsta001_dsta001_(dsta001_-_(deleted))

Hi,

Have been looking through the Admin help. Could not find any regarding adding regions to the search manager

Raymond_Tsui

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

The Search Manager region list is returned by the Search Federator. New regions are added to the index as they are discovered by the index builder during indexing. There is no manual way of adding regions.

Kyle_Swidrovich

Please see the following area of the Admin Help:

Livelink Index and Search Administration
-> Search Administration
-> Administering Searching
-> Configuring Index Regions

The Administering Searching point also gives some brief notes on regions as well.

dsta001_dsta001_(dsta001_-_(deleted))

Hi,

Think raymond is correct, the regions cannot be added in manually. As in one cannot decide which column in the database to index. I need to do a query base on the orgindataid column in the DTree table.

But after looking through the Admin, it did mention about adding nested region in the LLFieldDefinitions.txt. I can give it a try but doubt that it will work. Although i still not too sure what is a nested region.

Kyle_Swidrovich

My responses were regarding making a known region queryable.

If a region has not been produced by the system for a certain piece of metadata, then you cannot just add it without an Oscript customization. I've checked the Oscript code and I don't see anything there that explicitly pulls OriginDataID data from DTree for extracted shortcuts/generations.

Playing with the LLFieldDefinitions.txt file is strongly not advised, especially for your case as it will not achieve your desired end result. A region would be created in the index, but the Oscript code would not know to populate it with data.

If you would like to see this extracted in core product, please feel free to open a Customer Support ticket for a new feature request.

In the mean time, exposing this information through search would require an Oscript customization.

Phil_Halder

Kyle,

you mentioned Oscript code would need to know how to populate a newly declared region.

Do you have some examples from exisitng modules (maybe physicalObjects) on how this isdone? I am an Oscript developer and have added a widget in Advanced search but now need to search on some data from some custom tables associated with DTREE.

phil halder (logica)

Kyle_Swidrovich

Hi Phil,

There are two things to consider:
1) Case where you have your own custom subtype to be extracted and indexed
2) Case where you want a custom region extracted for every object (with optional logic to exclude certain items)

If it's #1, then you would need to look at creating your own INDEXLIBRARY : IndexLibraryNode, customized for your subtype. This will allow you to define what "MetaData" and "Content" means for your subtype.

If it's #2, then look at adding your own INDEXLIBRARY : IndexLibrary Root : MetaDataCallback object. This is what modules like Physical Objects use to add additional regions to the metadata string that is output into IPool messages by the extractor.

Cheers,
Kyle