Aditya, so my guidance is this. I don't know how many combinations and permutations there would be in your circumstance but I would advise against creating too many different relationship types because it might be hard to manage and may grow over time and become even harder to manage. But if the number is few and manageable then it might work well to establish a finite set of relationship types, each with its own forward and reverse label that supports the specific nature of entities being connected by the relation . You probably noticed and know that the primary and secondary label of an entity can be dynamic via use of variables and literals declared within the label pattern, but this flexibility is not provided for a label associated with a relationship type. For labels embedded in a relationship type, you only have the flexibility of establishing a reverse label different than a forward label which helps with directed relationships, and the ability as you saw in the docs to have a label get set on the fly, based on an entity attribute value (e.g. IF gender = 'male' THEN label = 'father'). It would interesting to see if in this last case, the attribute that drives the label being used, can be a reference attribute which references the Relation Type you mentioned exists in the relation itself. Not sure about that but feel free to do that experiment. Hope this helps.
Original Message:
Sent: 01-10-2024 00:04
From: Aditya Somayajula
Subject: Direction based Attribute/Label Value for a Relation
Hi Curt, Shantanu,
Thank you for the info and your thoughts . I understand the above configuration piece would work when the type of Substance is Monohydrate but when the Substance is Salt the labels should be Salt to Parent and Parent to Salt. Apologies for the incomplete info.
Please see the attached file and we are trying to achieve something similar.
As we have only 1 entity - Substance and only 1 relation - SubstancetoSubstance. Can this be achieve with only 1 relationship or do we need to have multiple relations?
If you look at the first sample code in this page - https://docs.reltio.com/en/model/construct-your-data-model/define-or-refine-your-data-model/define-relationships/configuring-relationship-types, the start object label pattern is being set dynamically based on the Gender attribute of start object.
------------------------------
Aditya Somayajula
AstraZeneca India Private Limited
Original Message:
Sent: 01-09-2024 11:54
From: Curt Pearlman
Subject: Direction based Attribute/Label Value for a Relation
Hi Aditya, if I understand you, it seems you want to dynamically change the value held within the Relation Type attribute that exists in SubstanceToSubstance so that the reference attribute within the Substance communicates to the user (or a calling application) the role that the Start entity is playing (in relation to the end entity, i.e. Monohydrate or Parent). That's in interesting idea, although likely an uncommon one. To Shantanu's point, have you considered using the directional labels feature on the relation? Reltio allows you to define a label for the direction of start-to-end, and a different one for end-to-start. In this way, as long as the user or calling application is careful to assign the Substance in question to the appropriate end of the relationship (start or end), then the directional label will automatically provide the insight regarding the directionality of the relation between the two entities.
And I usually find it very useful to construct the directional label as a phrase that uses the start and end entities to form an intuitive sentence. See attached example. The forward and reverse labels for the relation display in the UI in light-grey. In the examples, you can see how navigating to SodiumChloride or conversely to SodiumChloride Monohydrate displays the appropriate label to provide clarity about the relation. The way one reads these labels is as follows. Begin inside the facet and read from left to right, then finish the sentence with the name of the primary entity of the profile. In the left example, you would say, "Sodium Chloride Monohydrate is a monohydrate to Sodium Chloride". By clicking on the Sodium Chloride Monohydrate entity, you would be navigated to a profile that features Sodium Chloride Monohydrate as the primary entity and as shown in the right example, you would use the same approach and say "Sodium Chloride is a Parent to Sodium Chloride Monohydrate".
Calling applications that don't have the benefit of viewing a UI can get the same insight by merely querying the relation to understand which entity is in the start position and which is in the end position.
Hope this helps.
Curt
------------------------------
Curt Pearlman
Original Message:
Sent: 01-08-2024 23:58
From: Aditya Somayajula
Subject: Direction based Attribute/Label Value for a Relation
Hi Folks,
We have an entity named "Substance" configured in our L3. We also have a bi-directional relation configured named "SubstanceToSubstance" with only one attribute (Relation Type) in it.
The Substance entity has a reference attribute within which we are calling this Relation Type to be displayed.
The problem we have is that from child entity perspective the Relation Type value should something and from parent entity perspective the Reltio Type value should be something else.
For Example :-
1) Entity 1 - Sodium Chloride Monohydrate
2) Entity 2 - Sodium Chloride
3) Relation 1 - Entity 1(Start) and Entity 2(End) are related and the Relation Type value is Monohydrate to Parent
From Entity 1's perspective the Relation value is Monohydrate to Parent which is as per requirement.
But from Entity 2's perspective also the Relation value is Monohydrate to Parent, however we want it to be Parent to Monohydrate.
But since we are referencing the relation attribute it always remains the same.
Could you suggest a way to achieve the above functionality that would involve minimal effort/changes? Please note that we don't want to go the LCA or an event driven process route.
We are trying to achieve the above stated requirement via label pattern in the directional context. Sample Code below from Reltio Doc, but it doesn't seem to be working.
{
"URI": "configuration/relationTypes/Parent",
"label": "Parent",
"name": "Parent",
"implicit": false,
"direction": "directed",
"typeColor": "#AA3A44",
"startObject": {
"objectTypeURI": "configuration/entityTypes/Individual",
"directionalContext": [
{
"rule": [
{
"attribute": "configuration/entityTypes/Individual/attributes/Gender",
"type": "condition",
"condition": "=",
"value": "Female"
}
],
"labelPattern": "mother"
},
{
"rule": [
{
"attribute": "configuration/entityTypes/Individual/attributes/Gender",
"type": "condition",
"condition": "=",
"value": "Male"
}
],
"labelPattern": "father"
},
{
"labelPattern": "parent"
}
]
},
"endObject": {
"objectTypeURI": "configuration/entityTypes/Individual",
"directionalContext": [
{
"labelPattern": "child"
}
]
}
}
------------------------------
Aditya
------------------------------