When creating a tag like “foo/bar” via the Tag bar and pressing Enter, the tag is “bar” is created nested under “foo” (as expected). In the items list the tags are shown as “foo” and “bar” (separate), but the Tag bar keeps showing “foo/bar” unless I switch to another document and back again.
I would expect that the Tag bar would be updated to show “foo” and “bar” as separate tags after pressing Enter. Or is this intended behavior?
It’s nothing more than an artifact, as evidenced by this comment.
Not sure I understand; shouldn’t the UI update on Enter? As it does e.g. when adding foo/bar via the item list? After pressing Enter it creates the two tags: foo and bar.
Are the tags created? Yes, so it’s not a functional bug.
It’s merely a cosmetic effect, as shown by the fact the tags are shown separately when reselecting the item.
The tags are created and it’s not a bug, it’s merely a perceived inconsistency from other places in DT where the UI does immediately refresh after creating a tag with slashes which results in two different tags
Understood but development would have to weigh in on it.
The next release will fix this inconsistent handling.
I believe this inconsistency persists?
Actually, I’d prefer nested tags to always show their nested status (people/creativity) rather than become separate tags (creativity,people) after creation. I nest tags to impose some sort of hierarchical order on what is otherwise a messy, unstructured list of words, so why not reflect that order in the tag bar?
Perhaps an option in Settings to either show the nested status of tags, or disaggregate them?
We might consider a preference for future releases but the current approach has also advantages, especially if an item has multiple nested tags sharing the same parent tag(s). Instead of parent/A parent/B parent/C right now you just see parent A B C
Nested tags help me remember what the tag represents. I might have tags “people/principles” and “nature/ethics”. In isolation the words “principles” and “ethics” don’t remind me that one applies to the natural world, one to the human.
Unfortunately Devonthink doesn’t seem to recognise nested tags in autocomplete, although it autocompletes solo tags. Having nested tags visible in autocomplete would be very useful as an aide-memoire for recalling what tags apply where.
Some will undoubtedly prefer Devonthink’s current approach, but hopefully concessions can be made to those of us who use nesting to guide us through the tag tangle.
A similar situation is when a single child tag has multiple parents, which could be the result of assigning multiple tags to a tag item.
And depending on how deeply nested tags are, someone could end up with very long tags being shown.