What is Endeca Precedence Rules? - Endeca Features

Precedence rules provide a way to delay the display of dimensions until they offer a useful refinement of the navigation state. Precedence rules are defined in terms of a trigger dimension value and a target dimension, where a user's selection of the trigger dimension value reveals the previously unavailable target dimension to the user.
Example: Assume we have two dimensions: Size Type and Size.

We have one precedence rules:   Size Type> Size

In this case, the Size dimension is displayed after a dimension value from Size Type dimension is selected.

Option	Description
Source dimension value	The dimension that serves as a trigger for the To (or target) dimension value to be displayed.
Target dimension	The dimension that serves as a target for the From (or source) dimension value.
Rule type	There are two types of source dimension values: The standard type means that if the dimension value specified as the trigger or any of its descendants are in the navigation state, then the target is presented (one trigger, one target). The leaf type means that querying any leaf dimension value from the trigger dimension will cause the target dimension value to be displayed (many triggers, one target).

 

How to find the list of all published projects status on the Authoring Instance? - Endeca Experience manager

This will help to find the list of projects saved on Authoring Dgraph using Endeca Experience manager and also who made those changes.

http://localhost:8006/ifcr/system/endeca/publishStatus?environment=Authoring&group=rules&site=ENDECA-APP-NAME

[{"status":"success","env":"Authoring","message":"Publish succeeded: 

AuthoringDgraph","id":"[PUBSERV4]",

"tool":["content"],"app":"CRS","time":"Tue Jan 19 2016 16:28:39 GMT-0600",

"timestamp":1453242519554,"user":["rhonakamble"]},

{"status":"success","env":"Authoring","message":"Publish succeeded: 

AuthoringDgraph","id":"[PUBSERV3]",

"tool":["content"],"app":"CRS","time":"Tue Jan 19 2016 16:27:11 GMT-0600",

"timestamp":1453242431229,"user":["admin"]}]

How to add Endeca SEO base-36 parameter Encoding? - Endeca SEO capabilities

You can use the URL Optimization API to apply base-36 encoding to numeric Endeca parameters. Only the numeric Endeca parameters can be encoded:

N

Ne

An

Dn

Here is an example on how to do it for N parameter in ATG & Endeca Integration platform:

 

/CRS/modules/endeca/config/atg/endeca/url/basic/SeoUrlFormatter.properties
urlParamEncoders=\
 /atg/endeca/url/basic/N-paramEncoder

/CRS/modules/endeca/config/atg/endeca/url/basic/N-paramEncoder.properties
$class=com.endeca.soleng.urlformatter.seo.SeoNavStateEncoder
$scope=request
paramKey=N

Ex:  http://www.barnesandnoble.com/b/books/_/N-29Z8q8
        http://www.grainger.com/category/electrical/ecatalog/N-bi5

How to find Endeca component versions Ex: Dgraphs, Deployment template, Forge, CAS and Tools & Framework? - Endeca component versions

MDEX: 

Use below command
C:\Endeca\MDEX\6.5.1\bin>dgraph.exe --version
Endeca dgraph version 6.5.1.829811
Supports opti-XML version : 2.00
Supports binary IR version: 640
Interface specification :
  READS:dgidx=6.3.0a WRITES:dgraph=IR640
ICU version 51.2
OLT version OLT 1.4 140319
OpenSSL 1.0.0k 5 Feb 2013 

Deployment Template:

Use below command
C:\Endeca\apps\Discover\control>runcommand.bat --version
Deployment Template: 11.1.0

Platform Services: 

Use below command
C:\Endeca\PlatformServices\11.1.0\bin>forge.exe --version
INFO    01/19/16 03:14:25.991 UTC (1453173265991)       FORGE   {config}: forge 4.1-Internal-foo@bar-baz-beetle ("i86pc-MINGW32_NT-6.1")
INFO    01/19/16 03:14:25.996 UTC (1453173265995)       FORGE   {config}: Copyright 2001-2012 Oracle Endeca Technologies, Inc.
INFO    01/19/16 03:14:26.000 UTC (1453173265999)       FORGE   {config}: Command Line: forge.exe --version
forge 4.1-Internal-foo@bar-baz-beetle ("i86pc-MINGW32_NT-6.1")
Copyright 2001-2012 Oracle Endeca Technologies, Inc.
INFO    01/19/16 03:14:26.041 UTC (1453173266040)       FORGE   {config}: Initialized cURL, version: libcurl/7.16.4 OpenSSL/0.9.8 zlib/1.2.3
INFO    01/19/16 03:14:26.045 UTC (1453173266044)       FORGE   {config}: Forge completed successfully.

CAS:

Use below jar to find the version: 
C:\Endeca\CAS\11.1.0\lib\cas-cmd>cas-cmd-11.1.0.jar

Tools and Framework: 

Version is displayed on the login screen

Stemming and Thesaurus - Endeca Features

Stemming  - The stemming dictionary is based on the common English dictionary, and doesn’t pluralize proper nouns, brand names, etc.  In order to ‘Stem’ a plural of a word that doesn’t occur commonly, a two way thesaurus entry should be made in the Workbench or update the stemming dictionary.

      Stemming  dictionary found at MDEX level /opt/app/endeca//MDEX/6.5.1/conf/stemming

    Thesaurus  -  The thesaurus is intended for specifying concept-level mappings between words and phrases.

There are two options available when configuring thesaurus entries:

1)      One-Way - This mapping technique specifies only one direction of equivalence. 

                 Ex: Assume you define a one-way mapping from the phrase “red wine” to the phrases “merlot” and “cabernet sauvignon”.  This one-way mapping ensures that a search for “red wine” also returns any matches containing the more specific terms “merlot” or “cabernet sauvignon.”

2)      Two-Way - This technique means that the direction of a word mapping is equivalent between the words.

                  Ex: a Two-way mapping between “laptop,” “desktop,” and “notebook” means that a search for one of these words will always return all results matching any of these words

Note: Only one global thesaurus is supported for an Endeca data domain. In other words, language-specific thesauruses are not supported (for example, one thesaurus for English, a second for French, and so on).