Introduction Endeca the company has been around since and was based in Cambridge, MA. Endeca technology primarily targets the following objectives. Endeca Queries Oracle Endeca Commerce uses two types of queries: navigation queries and keyword search queries. Navigation queries return a set of records based on application-defined record characteristics such as wine type or region in an online wine store , plus any follow-on query information. Keyword search queries return a set of records or dimensions based on a user-defined keyword, plus any follow-on query information. Records are the fundamental units of data.
|Published (Last):||6 May 2008|
|PDF File Size:||6.84 Mb|
|ePub File Size:||11.46 Mb|
|Price:||Free* [*Free Regsitration Required]|
Oracle Endeca accepts any of the following formats till date. Forge in action: Once the data is in the ITL process Forge maps the source data to Oracle Endeca Properties and Dimension along with all configuration applied that were developed using Developer Studio. Dgidx in action: Once data is forged, dgidx index the data and converts it to Endeca records which are finally given to Dgraph. Records, Dimension and Properties Records Endeca records are the entities in your data set that users are navigating to or searching for.
Below image show endeca record information Dimensions Dimensions provide the logical structure for organizing the records in your data set. For example below categories are user to narrow down the result to specific product user is looking for. Guided Navigation Guided Navigation is the presentation of valid follow-on refinement queries to the user. You can think of Guided Navigation as the elimination of invalid refinement queries, or dead ends. An example below shows when user navigates to Carpet Kit.
User still has options to navigate to more targeted records he is looking for. Here user can further drill down on Brand, Price, etc.
Oracle Identity Management
Oracle Endeca Tutorial
Oracle Endeca Commerce Training
Oracle Endeca Getting Started