@Tobias - what a fast reply, fantastic!
True, but for the rest of us it is important to understand why you want to > do the things you want to do. > I'm experimenting and kind of felt the context is both a bit too big for the question but mostly that it would take over the question. Buuut, since you ask, I'll describe it below especially since it's concerning something I know you also care about. Here's one way using tobibeer/filter > <http://tobibeer.github.io/tw5-plugins/#filter>: > Great! that does work. So, TW does not have enough core features for this, right? Ok, here's the context: It concerns typed tags, tag categories, semantic tagging - pick your poison. We (I and you and surely many others) have long played around with the idea of taking advantage of fields "name:value" pair to replace tags and to instead use fiels as *tagtype:tagname.* At least that is how I have envisioned it until an hour ago... when it struck me that maybe I have it backwards! It should be *tagname:tagtype* Possibly obvious to others, I don't know. Anyway, it seems obvious now - one only uses a tag once in a tiddler, thus it must be the unique field name- but you should be able to use tags of the same type multiple times in a tiddler, thus the field value. A drawback is that field names, i.e what woudl be displayed on the tagpill, ehm *fieldpill*, is limited lowercase etc... j.k_rowling:Author (On the other hand, the tag types can be pretty). A more serious drawback is what you and I touched on the other day; There is currently no way to substring search field names. Thus searching for "rowling" doesn't currently work, if I understood you right. (Searching for the full j.k_rowling or author should work though as you showed me, even "auth", right?) A niciety, when I use your filter, is that it even works to set the field value to be the string "tag" ! So, I figure one could have an "add field" feature up where the tags field currently resides and with the default field value (i.e the "type" for the supposed tag) set to be the string "tag", but changeable into anything of course (like "author" or "pupil"). I'm sure there are problems with this whole approach, but on the other hand it doesn't change any existing infrastructure. The tags field can still be around, it just wouldnt' be used, or it could be used in parallel. Maybe even practicing a distinction between tags vs categories <https://www.google.se/search?q=tags+vs+categories&ie=utf-8&oe=utf-8&gws_rd=cr&ei=GmyVVpX6FMuhsgHEkI_YAw>, i.e dedicating the tags field to one thing and fieldtags to the other. @Tobias - but also anyone Please come with input on these thoughts. <:-) -- 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/6e24fc62-02dc-49ca-8fa7-3381e12e592f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
