Attribute ordering strategy

A sorting strategy for an attribute used to visually sort multiple instances of a nested or reference attribute.

Attribute Ordering is a sorting strategy for an attribute and is used to visually sort multiple instances of a nested or reference attribute. Attribute ordering strategy is defined in the Attributes configuration. All supported options are listed in the table below.

Table 1. Attribute Ordering Strategy
Strategy	Description	Attribute Configuration Examples
LUD	Last Update Date strategy. The most recently updated attribute values will have the highest sort priority. By default, all attribute values are ordered by this strategy. The value with the maximum update date comes first. Maximum update date for the value is calculated as follows: For each crosswalk bound to the value we take a `singleAttributeUpdateDate`. If the current crosswalk doesn't contain such a date, we take the `updateDate` of the whole crosswalk. Now, we have the list of update dates from each crosswalk. Then, we choose the maximum date among the obtained update dates for the value. The attribute values are then sorted by such dates in descending order.	`{ "uri":"configuration/entityTypes/Individual/attributes/FirstName", "name":"FirstName", "label":"First Name", "attributeOrdering": { "orderingStrategy": "LUD" }, "type":"String" },`
FieldBased	Only for complex attributes like nested or reference. This ordering strategy defines that complex attribute values should be sorted in accordance with some attribute value inside these attributes. For example, for the nested attribute Education, we can use ordering based on the `YearOfGraduation` value. See the note below the table for additional information.	`{ "uri":"configuration/entityTypes/Individual/attributes/Education", "name":"Education", "label":"Education", "type":"Nested", "attributeOrdering": { "orderingStrategy": "FieldBased", "fieldURI": "configuration/entityTypes/Individual/attributes/Education/attributes/YearOfGraduation" }, ...`

Note:

Optionally, an order type property can be defined (for example, orderType:DESC or orderType:ASC). This indicates that the property applies an ascending or descending order to attributes values sorting. By default, ascending order is used.
If the LUD is the same for two or more nested attributes, the sort order for those nested attributes may change each time you perform a load.

LUD Strategy Example

L3 Tenant Configuration Example: LUD Sort

{
     "URI":"configuration/entityTypes/Individual/attributes/FirstName",
     "name":"FirstName",
     "label":"First Name",
     "attributeOrdering": {"orderingStrategy": "LUD"},
     "type":"String"
}

Data Example: LUD Sort


Education
Student	University	Degree	Year of Graduation	GPA	Last Updated Date
C	University of Toronto	MBA	2006	3.5	3/11/15
C	University of Toronto	PhD	2010	3.8	2/11/15
C	University of Minnesota	BA	2004	3.7	1/11/15

Field-based Strategy Example

L3 Tenant Configuration Example: Field-based Sort


{
     "URI":"configuration/entityTypes/Individual/attributes/Education",
     "name":"Education",
     "label":"Education",
     "type":"Nested",
     "attributeOrdering": {
     "orderingStrategy": "FieldBased"},
     "fieldURI": "configuration/entityTypes/Individual/attributes/Education/attributes/YearOfGraduation"
 },
 ...

Data Example: Field-based Sort


Education
Student	University	Degree	Year of Graduation	GPA	Last Updated Date
C	University of Minnesota	BA	2004	3.7	1/11/15
C	University of Toronto	MBA	2006	3.5	3/11/15
C	University of Toronto	PhD	2010	3.8	2/11/15

Unify and manage your data

Attribute ordering strategy

LUD Strategy Example

Field-based Strategy Example

Footer