2 Replies Latest reply: Jan 4, 2013 3:48 PM by Pankaj.Rajankar RSS

    Help with ATG-Endeca Integration[Using Product Catalog Deployment Template]

    mk.s
      Hi All,

      We are evaluating ATG-Endeca Integration using product catalog deployment template and ATG Simple Indexing Configuration.

      The properties and dimensions are created dynamically using the ATG data. The data is then written to recordstores using CAS.[ http://docs.oracle.com/cd/E35318_02/Platform.10-1-1/ATGEndecaIntegrationGuide/ATGEndecaIntegrationGuide.pdf]

      The schemaexporter class and its related config file product-sku-output-config.xml does not seem to provide the capability to define all the attributes of a endeca property or dimension.

      For e.g,
      - adding a property to a search interface or making sure a number of properties can be added to a search interface in a particular order
      - Making a property as sortable
      - Enabling a property as roll up key

      All this have to be done at Endeca layer through csv overrides. But as the properties/dimensions are created dynamically , this does not seem to be a good generalised approach.

      Any thoughts or pointers towards best practices around this will be helpful.

      Edited by: user7615588 on Jan 2, 2013 6:21 AM
        • 1. Re: Help with ATG-Endeca Integration[Using Product Catalog Deployment Template]
          Pankaj.Rajankar
          That is an interesting observation. I checked the indexing-dependency-schema.dtd and did not find any tags/attributes for sortable or rollup either. Let's see if anyone else was able to figure this out.

          Regards.
          • 2. Re: Help with ATG-Endeca Integration[Using Product Catalog Deployment Template]
            Pankaj.Rajankar
            Hello,

            The answer lies in <application name>\config\api_input\schema.csv. Here are some of the attributes that might be of interest to you.
            attribute.record_filterable: Optional. A Boolean value indicating whether to enable recording filtering for this property or dimension. Record filtering presents a subset of the data to the end-user. A value of true enables the property or dimension for record filtering. The default value is false.
            attribute.rollup_key: Optional. A Boolean value that enables aggregated Endeca record creation by allowing rollups based on this property or dimension. The default value is false.
            attribute.search_interface: Optional. A pipe ( | ) separated list of search interfaces to which this attribute should be added as a member. The names must be pipe-delimited if specified in the CSV file, but when loading records into a Record Store instance, names may be either pipe-delimited or multi-valued.
            attribute.search.searchable: Optional. A Boolean value that indicates whether the property or dimension is enabled for record search and added to the “All” search interface. For Endeca properties, record search finds all records in an Endeca application that have a property whose value matches a term that the user provides. For dimensions, record search finds all records in an Endeca application that have a dimension whose value matches a term the user provides. If unspecified, the attribute is not searchable. The default value is false.
            Pankaj.