Typical use case: Evaluate plural attribute

A tuple search should evaluate all tangible instances of the entity type 'Address book entry' (AdressBookEntry, see Address book entries) that reference exactly one address (see Addresses) via the 'Address' (address) property and provide an overview of the data stored there via the 'Communication information' (CommunicationInfo) attribute type.

Specifically, exactly one tuple is output for each address book entry, which contains, among other things, a list (or collection) of all communication information.

Configuration:

Runtime example:

• Each row element ('tuple') contains a list of 'Communication information' assigned to the address book entry as the fourth item.

• The sample data shows attribute values with different Communication type (EMAIL, PHONE) and 'context' (info, alternate, noreply) for classifying the specific information specified as 'value' (communicationValue).

Variant: In order to 'serve' the 'Communication information' in a CSV search as direct readable text, a slightly different formatting of the return values from the Attribute projection is recommended:

• Instead of a 'list column' (collection) in a tuple, the 'Communication information' is output on several lines with repetition of the header data of the address book entry.

• The payload properties from the attribute should be distributed to individual columns.

Configuration:

Runtime example:

For the same section of the sample data, the CSV search returns the text shown below, in which address book entries (see second column, id) with multiple lines of 'Communication information'.

addressBookId,id,address.accMatchCode,orderIndex,communicationType,communicationContext,communicationValue
...
1051,953,EDDH,0,EMAIL,noreply,noreply@ema.il
1051,953,EDDH,2,PHONE,info,+49 (40) 50750
1051,953,EDDH,1,EMAIL,alternate,noreply2@doma.in
1051,952,EDDF,0,PHONE,info,+49 (180) 6 3724636
1051,951,EDDL,0,PHONE,info,+49 (211) 4210
...

Special use case: Evaluating typed attributes of a type

A CSV search should visualize the 'progress' in the life cycle of Shipments through a list column that names the Date types for each date attribute used.

Configuration:

Runtime example:

id,DATE_ATTRIBUTES
...
4802,[DISPATCH_DATE_PLANNED]
4701,[ARRIVAL_PLANNED]
4651,[ARRIVAL_PLANNED]
4402,[]
4401,[]
4301,[ARRIVAL_PLANNED]
4253,[ARRIVAL_PLANNED]
4203,[]
4202,[ARRIVAL_PLANNED]
4201,[]
4151,[]
4101,"[VESSEL_DEPART, WAYPOINT_ARRIVAL_DATE, WAYPOINT_ARRIVAL_DATE, VESSEL_ARRIVAL, LOADING_DATE]"
4051,"[TEST_DATETYPE, ARRIVAL_PLANNED]"
4006,[]
...

►NOTE◄

• The example shows items with date attributes with subtypes that can be singular or plural.

• Only the Date types WAYPOINT_ARRIVAL_DATE can be clearly recognized as plural, as it appears several times in the same Collection for one shipment.

• Whether a Date types that only appears once is singular by definition would also not be clear from the complete attribute value. An index property with the value 0 also appears for singular attribute values.

►IMPORTANT◄ The procedure demonstrated here for evaluating attribute subtypes is only really practical if the following restrictions are not a problem:

1. The individual values in a Collection projection cannot be sorted. The Date types values also do not appear in a logical or chronological order (see LOADING_DATE).

2. The Attribute projection takes into account all attributes of the selected type, including those that are not currently 'filled'.
   Digression;
   If an attribute value is deleted, not only the associated attribute entity is usually retained in the data of the attribute owner entity, but also the attribute value itself, as this continues to refer to the subtype:
   

         <shp:ShipmentDate id="1852" ... >
            <value dateType="TEST_DATETYPE"/>
         </shp:ShipmentDate>

   
   The search shown above therefore returns the Date types in this case, although the attribute value does not contain any further 'payload'. The Attribute projection also provides no option for a corresponding restriction. Only an Attribute join could do this.