Yes, as you know, GenTags extends the tags operator to add tags:field[] so I can do something to get a list of tiddlers and then get the union of their tags:
[myfield[fieldcriteria]contains:myfield2[sometagcriteria]tags:myfield3[]sort[title]] It's something like that which I am doing to build the various filter drop downs for my cardiovascular observations. Each filter is based on the tags in a specific field and as one dropdown changes, the others change to only offer the tags in their field that are still available. To do this, I rely on the tags:field[] operator from https://github.com/OokTech/TW5-GenTags/tree/master/core%20updates But maybe the list or get operators can now do this? [image: ObsIndex.PNG] On Tuesday, September 29, 2020 at 11:24:45 PM UTC-5 TW Tones wrote: > Cade; > > You can access the tags filed with the tag operators or > as a field in its own right {{!!tags}} or has[tags] or has:field[tags] > these should work with gen tags fields > > If you are asking about operators for gen tags specifically refer to its > documentation. It adds a some operators. > > Regards > Tony > > > On Wednesday, 30 September 2020 10:59:10 UTC+10, Cade Roux wrote: >> >> Cool, is there also now a Core alternative now to the tags:field[] >> operator? I am using that extension from the GenTags plugin to build my >> dropdowns of tags across a set of tiddlers. >> >> Thanks, >> >> Cade >> >> On Tuesday, September 29, 2020 at 5:57:23 PM UTC-5 TW Tones wrote: >> >>> Cade, >>> >>> The contains operator is newer than GenTags. Also as I said earlier; >>> >>> >>> - *Instead I tend to use my own fields and list fields that in many >>> ways work not unlike tags if you want them to.* >>> - *See listops and other operators and widgets.* >>> >>> Tones >>> >>> >>> On Tuesday, 29 September 2020 02:11:22 UTC+10, Cade Roux wrote: >>>> >>>> OK, that appears to work. I was working from the readme on GenTags. I >>>> think to do what I need, I don't even really need the GenTags plugin >>>> anyway >>>> (I don't need to display the tags), and this wasn't relying on it. >>>> >>>> Thanks, >>>> >>>> Cade >>>> >>>> On Monday, September 28, 2020 at 9:26:34 AM UTC-5 Eric Shulman wrote: >>>> >>>>> On Monday, September 28, 2020 at 6:39:48 AM UTC-7, Cade Roux wrote: >>>>>> >>>>>> FWIW, to me it appears like the listed operator cannot be re-used in >>>>>> the run for some reason, even on a different parameter or different >>>>>> field. >>>>>> Yet by itself just once, combined with tag does work. I made my.field >>>>>> and >>>>>> my.field2 with combinations of A, B, C and X, Y, Z respectively and put >>>>>> alpha, beta, gamma in tags, and combining tag operator with listed works >>>>>> fine. And tag filter intersection seems to work as >>>>>> expected: [tag[alpha]tag[gamma]] >>>>>> >>>>>> Perhaps the clunky original plan of prefixing tags for the possible >>>>>> values of each field may have to be what I resort to. e.g. >>>>>> [tag[name-some >>>>>> name]tag[structure-some structure]tag[context-some context]] >>>>>> >>>>> >>>>> I think you might be using the wrong filter operator! Try using >>>>> "contains:fieldname[value]", like this: >>>>> >>>>> <$list filter="[contains:my.field[A]contains:my.field[C]]" /> >>>>> >>>>> (see https://tiddlywiki.com/#contains%20Operator) >>>>> >>>>> -e >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1afa94df-e1ed-4189-8873-71bb73ae4f98n%40googlegroups.com.
