Whereas I have been using Tagging over the past few years in all of my DBs - for a variety of reasons, just created a new INDEXED database, that contains many groups.
I also decided to give the “Groups as Tags” as go [Exclude Groups from Tagging unselected].
Can someone please advise on the following behaviour that I am seeing - and if it is supposed to work like this - what would an alternative be?
I have many groups called Committee A; Committee B; C D E F etc.
Under EACH of those, I have sub-groups for the years where work was done in those, i.e. 2010; 2011; 2012; 2013.
And inside each of those, further sub-groups.
By using the Tags as Groups, I then simply activated that option on those top two groups. That way, if I dove into the sub-groups, I would still see tag:Committee A and tag:2010 [or tag:Committee B and tag:2014], which is what I hoped for.
My “difficulty” comes in, when I jump to the “As Tags” view.
I thought that I would be able to use the As Tags view to quickly whittle down what I was looking for - by (for instance) selecting BOTH “Committee A” and “2013” (or “2012” or “2010”)…
But as can be guessed, the problem is that there are now numerous instances of “2010” and “2012” etc., so unless I select “Committee A” and the correct “2012” (that is a sub-group of it, as opposed to Committee B or E), I don’t get hits.
What I hoped would happen is that ALL tags/groups called “2011” or “2014”, irrespective of whether they were the child of Committee A or E or G, would be ‘treated’ the same/interchangeably for the purposes of the As Tags view – and they are not.
Would really appreciate some practical suggestions for how to work around the “year” issue. There are close to a hundred of them - so 1st prize would be not having to rename them…