I agree that is an annoyance in general, however, there is narrower sub-case of
@Imre Vogelezang 's idea which particularly irks me, and that sub-case might have a simpler solution because it pertains specifically to semantic parent-of fields and drill-downs in parent-child tree. Let me try to explain...
Depending on the current view context, I would like Tana to hide parent reference fields that have a semantic function and is referencing a parent in the viewing tre, because that is just uncessary visual clutter (in that view context)..
An illustration:
I REALLY would like something like would solve a LOT of these ugly awfulesses that often throws off my flow because of the duplicated reference in the above screenshot.
I still WOULD like to see the parent field when it's not part of me drilling down a tree, for example, when viewing the node from the example above in isolation like this, it's really nice to have the field as a navigation path to the parent:
For me, this is a bit related to this comment by Delgado on the Slack community:
"I see the PARENT and GRANDPARENT use as an outcome from the Outliner feature's inheritance. If we imagine, just per a second, the lack of outlining, thus any related parentship, we should probably rely 100% on attribute-based relationship. I.m.o. the last one feels more deliberate, unlike outlining which feels more contextual."
I strongly agree with Davids quote - the related parentship is just a nicer model - but an accidental drawback from it right now (that makes me yearn for the outline model) is the extra clutter it adds to the visual space when you do drilldowns exemplified above.
Perhaps add an extra "When viewed as a child of parent" option here:
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
I agree that is an annoyance in general, however, there is narrower sub-case of @Imre Vogelezang 's idea which particularly irks me, and that sub-case might have a simpler solution because it pertains specifically to semantic parent-of fields and drill-downs in parent-child tree. Let me try to explain...
Depending on the current view context, I would like Tana to hide parent reference fields that have a semantic function and is referencing a parent in the viewing tre, because that is just uncessary visual clutter (in that view context)..
An illustration:
I REALLY would like something like would solve a LOT of these ugly awfulesses that often throws off my flow because of the duplicated reference in the above screenshot.
I still WOULD like to see the parent field when it's not part of me drilling down a tree, for example, when viewing the node from the example above in isolation like this, it's really nice to have the field as a navigation path to the parent:
For me, this is a bit related to this comment by Delgado on the Slack community:
I strongly agree with Davids quote - the related parentship is just a nicer model - but an accidental drawback from it right now (that makes me yearn for the outline model) is the extra clutter it adds to the visual space when you do drilldowns exemplified above.
Perhaps add an extra "When viewed as a child of parent" option here: