Using a field like that is possible, with the operators that work with
lists.
As a starter, you will want to convert your list field into a title list.
There are two main approaches
* Method 1
<$list filter="[enlist{TestData!!mylist}prefix[V:]\"/>
* Method 2
<$list filter="[list[TestData!!mylist]jprefix[V:]]"/>
You may also want to use the "contains" operator
<$list filter="[title[TestData]contains:mylist[V:Tr22]]"/>
The contains operator looks for the whole value in the list field.
Which brings me to a larger point about database design. Although it's
initially convenient
to make designations like "V:Tr22", it can lead to headaches down the road.
It might be better to
have each word in it's own tiddler and it's qualities identified
separately, e.g.
wordtype: V
verbtype: TR
verbvalue: 22
(I didn't know what the 22 represented).
In database parlance, this is know as "data atomization" -- having each
field do just one job. You can look up
"data normalization" to learn more about it. It makes creating reports and
data extractions easier down the road.
If you do it this way, you can use existing filter operators to list all
of your transitive verbs sorted by verb value without having to split the
field into it's sub-components.
Good luck!
On Thursday, July 18, 2019 at 9:43:38 AM UTC-7, Aidan Grey wrote:
>
> Can someone ELI5* how to use / work with fields as lists of tags? What are
> the limitations and methods for using them?
>
> I understand that you can use buttons to edit the list, thanks to the
> listops widget (I think it's a widget), but I don't understand how it all
> goes together. Is it really just create a field and put items in it, like
> this?
>
> partofspeech: N:IN V:Tr22 V:Di12 Part:Case
>
> where V:Tr22 is a whole "tag" that I can subject to filters like
> [prefix[V:Tr], [suffix[22], and so forth?
>
> I'm particularly interested because I have fields in a dictionary TW that
> really should have multiple items, like part of speech above. A word can be
> a noun, several kinds of verbs, and an adverb, for example, and ideally,
> I'd like to be able to tag them all in there, filter on the tags in the
> field, etc. In other words, treat them just like a list. They wouldn't
> change a lot and I don't really need the tags visible since they're in the
> dictionary entry. I just need them for filtering.
>
> I also think using fields this way might be a way to solve another issue -
> some tags I don't want visible on certain kinds of tiddlers, but the
> solutions I've seen so far have been ... aesthetically unappealing to me
> ($:/ will work for some, but not all of them). Multicol dropdowns are
> great, but when I have literally 100 tags, it's impossible.
>
> Thanks,
> Aidan
>
> * just in case, ELI5 = Explain Like I'm 5
>
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/a8d36e5b-eacf-4477-a528-93f0cea67b1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
