Sorry to fill this thread with my ideas, but I feel like they fit the title of the topic.
I think on the one hand I understood how the concept of "hashtag" came into being, on the other hand I found a (I think) better use for it. I want to group the recipes to see their properties in a list, e.g. that if I look at the list of pasta foods, I want to know if that food also contains sour cream. The advantage of tags and fields is that you can easily group notes with them, so it's easy to filter recipes by ingredients field (this can include, for example, "cheese" and "pasta"). Notes can be grouped dynamically (although I am against the paper-based Zettelkasten), so I can create a view where foods are grouped by main ingredient (pasta dishes) and can be converted at the touch of a button to be grouped by additive (cheese dishes) . Thinking of Index notes and Link-based navigation, this is harder to accomplish than with fields: if I want to link to pizza, the pasta note index note should have a "cheese dishes" category, and the cheese food index should have a "pasta dishes" category to easily I can find it no matter where I start my search. This information is a duplication because we are talking about the same food (pizza), but depending on the view, I categorize it into several categories (in both cases it is the "cheese" and "pasta" categories, only the "parent category" is different). The solution is to have only one topic in an index without subcategories: pasta dishes should be just a simple list, there should be no "cheese" category in it, just as there should be no "pasta" category in cheese dishes. If I want to know about pasta dishes with cheese, I can only get it by query. One solution is for a note about a particular food (pizza) to link to the "properties" that are true to it (for "Cheese" and "Pasta" notes), so index notes are built based on backlinks, you don't have to list yourself them in each related index. This way I can find out which note has a link to both: I can either use the "[[Pasta]backlinks[]] ..." filter, or if the note title is like an API method <https://notes.andymatuschak.org/Evergreen%20note%20titles%20are%20like%20APIs>, just "[[Pasta]] [[Cheese]]" text. The problem with this is that I don’t want to disfigure useful backlinks with links that only use the ingredient at the mention level (any cheese dish would link to the “Cheese” note, though only to indicate that this ingredient needs to be added as well, but the note is not really about the cheese itself). In this respect, it would be worthwhile to create "property notes" that would only be used in this respect, e.g. "§Cheese" and "§Pasta": their backlinks are guaranteed to contain only notes that "use" that property. If I guess correctly, I now understood how the concept of the hashtag could have come into being ... o_O There is a clear identifier in the text ("§Cheese"), on which I only get notes where this identifier is also included, so with this I group the notes by an identifier according to some aspect. The advantage of this kind of "tagging" is that there is no duplication of information: if I used real tags (eg TiddlyWiki tags field), on the one hand I would have to add the tags corresponding to the components to the notes, on the other hand they would be in the text (where I describe the recipe itself). Instead, if I use "special links" as a tag, I only need to use it once, yet I can interpret the links as a tag. Eg the recipe for pizza: * Frozen [[§Pasta]] * 1/4 kg [[§Cheese]] * ... -- 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/89d29a7d-516d-4225-9fea-d464cba5ffc8n%40googlegroups.com.
