Hi Josiah, Further to what Richard has said,
The best/simplest way to do this, in my experience, is to give them all > names that start the same "KUNDUN (1997) Cast", "KUNDUN (1997) Clip" etc. > and then have a 'master' tiddler called "KUNDUN (1997)" which gathers all > the pieces (by transcluding all the tiddlers prefixed with it's own title). > This way a search for "KUNDUN (1997)", for example, will return a list of > meaningful titles instead of "KUNDUN (1997)" 5 times, which is not very > informative. > Using this technique as described, you can also make use of the removeprefix Operator <http://tiddlywiki.com/#removeprefix%20Operator> when listing the tiddlers prefixed with KUNDUN (1997). Also, you can simplify your filter by filtering on the title field itself, using Richard's example. Here's some code you could use in those 'master' tiddlers. <$list filter="[prefix{title}]"> * <$link field="title"><$view field="custom-field" /></$link> </$list> This will generate a bulleted list of the tiddlers which are prefixed with the title of the current tiddler, and link to them while displaying instead the content of some other custom field. You could either place this code directly into your 'master' tiddlers, or better yet, put it into a ViewTemplate which is filtered by a tag identifying all those 'master' tiddlers. Hope this helps, Hegart. On Tuesday, 7 June 2016 12:21:48 UTC+12, Richard Smith wrote: > > Hi, > > As Hegart points out, the tension derives from the fact that the title is > the primary key in the data-store. > > How would you differentiate between your three tweets if they have the > same title and tags? > > The best/simplest way to do this, in my experience, is to give them all > names that start the same "KUNDUN (1997) Cast", "KUNDUN (1997) Clip" etc. > and then have a 'master' tiddler called "KUNDUN (1997)" which gathers all > the pieces (by transcluding all the tiddlers prefixed with it's own title). > This way a search for "KUNDUN (1997)", for example, will return a list of > meaningful titles instead of "KUNDUN (1997)" 5 times, which is not very > informative. The other advantage to this is you could make a button to > create new tweets about the film and take advantage of automatic > incrementation ie; "KUNDUN (1997) Tweet #1", "KUNDUN (1997) Tweet #2" etc. > > The other mechanism that's available is the 'caption' field - multiple > tiddlers can have the same caption field and, if it's present, it gets used > in favour of the title when the tiddler is displayed in certain contexts, > like when the tiddler is used as a tab in the sidebar or elsewhere. > > It should be possible to beef-up use of the caption field (by re-writing > the view templates?), so that it is displayed as the tiddler title when > present - basically start to try and separate the "human readable titles" > from the "data-store keys" but this is likely to be a bit of a rabit-hole, > there are good reasons for TW being how it is and I'm sure Jeremy is > entirely cognisant of the trade-offs he's made in this area. > > Bear in mind that if all 5 of your tiddlers end up with the same title, > you will no longer be able to refer to any of them by that title, so you > will need to remember, or easily refer to, their individual primary-keys > and thus some of the 'magic' of tiddlywiki is lost and you're a database > administrator. > > Are you using TW for both creating and displaying the content? Are you > able to post an example of your work so far or examples showing how you > would like it to work? In my experience, the best solution to your problem > will depend on the workflow you are trying to achieve. > > Regards, > Richard > -- 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/ad90a6b8-78c0-431d-9a1e-00a39f738e0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
