Si, Many of us have being on this journey for some time, and I could overwhelm you with my view but trust the following advice;
- Unless its a very simple wiki I rarely use tags, since I want to reserve them for ad hoc grouping - I tend to organise with a fieldname object-type to differentiate between different tiddlers such as task/note etc... - In the case of subjects if I can have multiple on each tiddler I may use an alt tags field or build my own with listops functions - In the case of say a project name I also create a field, in this case it can only have one value, which is good. - You can have a keywords field that you enter multiple words but don't order and add except manually, but you can search for these keywords Each time you move some functionality from tag into fields you build yourself a method you can use and reuse in other circumstances. Lets say "every task has to have a project name, and only one", then you could use a select filter something like this [each[project-name]] to select from all existing projects. I am currently working on a way to create child tiddlers without the parent tag, that responds to the parent being renamed, although you can get relink to help. This is a very big subject. Keep it simple and use tags until it grow, or may grow large and complex. Regards tony On Wednesday, 7 October 2020 03:14:40 UTC+11, si wrote: > > Over the last few days I have been reflecting on the way that I use tags, > fields and links. I currently use tags both to indicate the *type *of > tiddler, as well as to *relate *tiddlers in a table of contents. I've > written a bit below about what I've been mulling over. I'm just trying to > think this through and would love to here the thoughts of people smarter > and wiser than me. > > I currently use tags in two ways: > > 1. As categories > 2. To relate tiddlers to a 'parent' > > The first is obvious - I might have a tiddler called "Sparrow" tagged > "Bird". The tag is a category and the tiddler is an example of that > category. > > As an example of the second use of tags I might have a tiddler called > "Beak" tagged "Bird". Unlike in the first case, a Beak is not an example of > a Bird, but is instead just related. I tend to think of the parent tiddler > as being constructed from its child, or that the child is a property of the > parent tiddler. This pretty much reflects the way that I structure my TOC > in the sidebar. > > I think that this pretty much covers all the ways I want to relate > tiddlers, but I'm considering using tags only for the first case > (categories). > > I think that links cover much of the second case, however there are a few > instances where I am still tempted to use tags. > > What do you think are the pros and cons of instead using a separate field > (i.e. a 'parent' field) for the second case? I know there is already a TOC > plugin for this. In addition the GenTags plugin would make the field behave > just like tags, and there would also be the added benefit of integration > with the Streams plugin (which I am just starting to use seriously). > > I understand that what I just wrote above may sound like the ramblings of > a madman. I guess what I am ultimately saying is: > > *How do you think about tags, and the type of relationship that they > represent? I am interested in your 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f76b4876-c0d6-4dfd-8b21-c32774ebeb3eo%40googlegroups.com.
