Thanks Mark!
Ultimately, what I need is some way to hide / not display certain tags.
Fields seemed like the way to do it, but maybe not.
As you'll see below, if I tag everything the way I need, my tag "cloud"
will be like 3 inches long, and that's way too much. I tried the whole $:/
trick I found in my googles, but that didn't work - they were still visible.
I'd like to see SOME tags, specific ones, but all 4589 that apply... no
thanks. I think I could remove the whole tag display field and then make my
own, maybe, that gets filtered for the stuff I want to see only?
If I understand right, I'd have my fields
partofspeech: V:Tr11 N:IN V:In1 V:St V:Tr12:Caus:Ins
semanticdomain: 31201 60512 80403 70600
a code for generic semantic domains that the word would fit into,
to make vocab gathering easier, and to make education easier as well
all the colors are in one semanticdomain code, for example, and
31201 is the code for frogs and related vocab
and then, when I want to filter by that field, I just use the enlist. So if
I wanted to list all the Transitive verbs about frogs (partofspeech = V:Tr
and semanticdomain = 31202), how would i do that?
If I just used tags, it would just be filter="tag[V]tag[Tr]tag[31201]]" -
easy.... except for the 3 inches of tags :)
As to atomization - I already tried that and got halfway in before I
realized it wouldn't work for me. It gets complicated:
Go 1
1. Intransitive Verb: move; attack; be known; empty the bladder or bowels
2. Transitive Verb: afford; proceed along
3. Noun: act of going; a turn
4. Adjective: functioning properly and ready (all systems go)
Go 2
1. Noun: Japanese board game
For me, that's 2 separate tiddlers, one for the english word go, one for
the japanese word borrowed into english
the English one, though, has 4 different parts of speech, Intr. Verb, Tr
Verb, Noun, and Adjective. For some words/languages, it won't stop there -
there can be multiple kinds of intransitive verbs, and so on. Unless I make
a separate tiddler for every distinct sense / use of a word (which is too
much), I couldn't use the atomized approach. There are contexts it's good
for, but unfortunately this isn't one of them.
And to satisfy the curiosity: this is for a polysynthetic language, which
has different classes or person markers. 22 indicates that the verb uses
class 2 markers for both subject and object. 12 indicates class 1 for the
subject, 2 for the object. And so on.
On that point, because it's polysynthetic (gloms a lot of stuff into the
verb), it's entirely possible to have even more complex details:
V:Tr11:DirIns:Caus:AppBen is a causative transitive verb, with directional
and instrumental, and a benefactive. An example of this might be:
"she killed it for him by (throwing/stabbing) a knife into it"
She = the first 1 of 11
kill = causative of die: she made it die
it = the second 1 of 11
Dir = Directional = into the middle of
Ins = Instrumental = with a knife
AppBen = Applicative (Benefactive) = for him/her
Hopefully the reason for field lists and/or hidden tags is much more
apparent.
On Thursday, July 18, 2019 at 12:02:54 PM UTC-6, Mark S. wrote:
>
> 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/1e3ec88c-5d74-4efb-8578-f03e08acd23e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
