In reply to
Maciej Smoła
Maciej Smoła
May 4, 2023
Maciej Smoła
Maciej Smoła
@Olli Tiainen @Andric Tham wouldn't mentioned "connection between supertag instance fields information" be contained within the field title and description?
In simple relationships, yes, such as:
- Person (supertag) is a member of a Project (Field instance for Projects)
- Project (supertag) has a Team member (Field instance for Persons)
But in more complex relationships, this doesn't work anymore:
- Nutrient (supertag) "Lack thereof causes" (Field title for #symptoms)
- Symptom (supertag) "Is caused by the lack of these nutrients" (Field title for #nutrients)
It doesn't work because field titles don't capture the context of these relationships (the edges). For example, Vitamin D (#nutrient) reduces osteoporosis risk (#symptom). But the context is that this is because Vitamin D helps the intestines absorb calcium from your food. However, neither the fields nor the field titles can capture this explanation of the connection. Instead, the information must be recorded either "under" the medicine or the symptom node, where it doesn't directly explain the relationship and isn't available bidirectionally through the fields or even via backlinks.
I see, so then we would be able to for example explain the mechanism of Vitamin D by describing the relation itself.
Have you seen that implemented in UI anywhere? Where should it go in the app like Tana? Curious to see if there are any which could be helpful for devs