This content has been marked as final. Show 2 replies
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.
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.Pankaj.
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.