Diego,, I love this kind of problem, and are yet to fully understand each contributors view of this. It is however my Gut instinct to suggest you can achieve what you are asking for using Jeds GenTags <http://ooktech.com/jed/ExampleWikis/GenericTagFields/> plugin to create generic tags fields. Basically you can create a separate tags field called relations and populate this as much as you wish knowing it is independent from your tags. When you want to place [[Tiddler 2]] [[Tiddler 3]] instead place the additional tag groupname for which [[Tiddler 2]] [[Tiddler 3]] (alternatively)tagged with groupname.
I suppose what I am saying is there is a relationship at any point in time you need a way to name the relationship, such that you can later alter the members in that relationship. In your example you are failing to encode this relationship as can be seen by you needing to visit multiple tiddlers to adjust it. One trick is to ensure you have a named relationship where ever possible eg; Call this the "somerel" with the members; * [[Tiddler 1]] * [[Tiddler 2]] * [[Tiddler 3]] All tiddlers that have this are tagged/Alt Tagged somerel So now you can change the members in one place in somerel Now you can clone this and create a new relationship called otherrel with different members * [[Tiddler 1]] * [[Tiddler 3]] But you can use the somrel relationship to find all tiddlers that are candidates to change from somerel to otherrel. For someone familiar with Databases and using a third table to index relationships between table1 and table2 the index table becomes two tables one for "table1 to table2" relationships, one for "table2 to table1" relationships, there are effectively two relationship tags. It depends if this is one-to-one (named tiddler) one-to-many (Relationship tag) or many-to-many (2 Relationship tags) Further with normal tags an alternative tags system in place you can clone or even have a custom Clone here button for new tiddlers and they can contain the original tiddlers tags and/or relationships fields and/or values. Thus as you build your tiddlers, you build the relationships. Also I love placing tiddlers that display their content based on conditions in the view template and where necessary have a tag or alternative tag that can also toggle the display on and off. For example if the Alternate tag field exists display the toggle, if toggled display all alternative tags, or provide a select alternative tag option and list all tiddlers tagged with that alternative tag. Jeds GenTags provides some of this out of the box. I do not yet have a way to prove it but I believe TiddlyWiki allows you to encode simple through complex relationships such that you need no other tool to represent any complex relationship (in the universe) . Now that is a Subject for a data science or mathematics PHD. Regards Tony On Friday, June 8, 2018 at 12:34:01 AM UTC+10, Diego Mesa wrote: > > Hello all, > > I've been thinking a lot recently about how to handle tiddler "relations". > That is, I have some tiddlers that are *related* to others, but not > necessarily through (my version) of a tag relationship. I first just > started typing out a related section in each tiddler like this: > > Tiddler 1 > ------------- > ... > my content > ... > > !! Related > > * [[Tiddler 2]] > * [[Tiddler 3]] > > > I quickly got tired of copy/pasting this into tiddler 2 and 3, so I turned > into a field, where each tiddler has a "related" field with the names of > tiddlers its related to. If this field is present, its automatically > displayed at the end as a list. > > I am still *building* and *learning* and so these relationships change. > Say I want to say that they are all now related to a Tiddler 4. I have to > now go back and make changes to 3 tiddlers. As the process continues this > gets cumbersome. > > So I thought, well I could just have some kind of tiddler like this: > > A Relation > ----------- > * [[Tiddler 1]] > * [[Tiddler 2]] > * [[Tiddler 3]] > > And then just go back and change that tiddler as the relationships of that > group change. This system is nonoptimal though, as: > > - What does its title mean? > - With this setup, every single time a tiddler is opened it has to > search ALL RELATION TIDDLERS and see if it's listed in any of them. This > doesnt make sense! > > Im envisioning some way to enter a new relation, and upon saving in this > one tiddler, it handles populating the related field somehow. > > Anyway, this is all just some random thoughts on this. > > Does anyone have any better ideas/systems for managing this? > > Thanks! > -- 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/97913cf2-74d3-46a7-b29a-fe5392d11492%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
