Filter by tags view includes files - or doesn't it?

I have two of what seem to me identical situations: 2 sets of a top level tag with a series of nested tags within, one layer deep. I can’t work out what is different between them, but they behave differently.

Example 1:
Top level tag ‘Themed Notes’ collects 9 nested tags. When I view by the top level tag, the next column displays all these nested tags AS WELL AS the files which have received this top level tag by inheritance. So the file ‘’ is listed twice, once in the first column since it received the top level tag ‘Themed Notes’, and again top right filtered by the nested tag, ‘lit crit’. This I understand.

Example 2:
Top-level tag ‘Sense of Place’ contains 12 nested tags. When I view by the top level tag, I only see the inherited tags, and none of the notes even though these have in fact inherited the top level as well (e.g. the file shown, 'Scott, ‘Of’ that has three of the nested tags plus the top level one, ‘Sense of Place’. Even though it has the top level tag it doesn’t show in the first column.

Why does these groups behave differently: i.e. one shows tags only and the other tags and files? I actually prefer the view of example 2, but don’t know how to enforce it.

I’m putting some time into designing a more robust tagging system (and am wary of nesting at all, certainly no deeper than 1 level!), but I have a series of tags that do specific work for specific groups of content. For other reasons, I prefer for all these groups to stay in the same db rather than be moved to a separate one.


1 Like

E.g. if the tags are not hierarchic initially, then adding tag 1 & 2 and afterwards moving tag 2 into tag 1 creates the first result.

Thank you. That’s indeed what’s happened, yes, I grouped some assorted tags into a new parent tag. So the only way to enforce the behavirour of my first example is deleting all tags; then rebuild the top-level tag set with inherited tags inside, before adding them to the files? That’s something I can do, as I’ve only just started tagging.

Actually I would recommend the second example as it’s easier to maintain.

1 Like

Sorry ‘second’ is what I meant when I said ‘enforce behaviour of my first example’. It’s the cleaner way of working for me. Cheers!