TT, Tiddlers are already unique, but they need not be unique over time, if renamed. The relink plugin solves this for many but not all use cases. That's why I believe using a seperate field to store a serialy issued unique number, issued if that field is empty on the first save, is best way to go where relink does not work.
As you point out you may need to "disambiguate" the tiddler title, but this will only occur if there are titles to disambiguate. So if we used INSOMNIA we would be fine until another need for INSOMNIA arises, at which time a new tiddler with a new serial number could exist, and because we do not want to override the existing INSOMNIA the automatic response is to create "INSOMNIA 1", thus it has being disambiguated, since the tiddler is tolerant of renames you can use a better disambiguation process at anytime. Personally the way I create tiddlers always permits them to be renamed without consequence, it is the tags or fields already catagorising them, so a name change makes no difference. As soon as a disambiguation need arises I tend to build different tiddler "types" eg film/medical. If you do use a value in the title to do this, I recommend placing this in a field of its own (in addition to the updated title) so later you can programmatically interrogate the title, and subtract the disambiguation from it. We could even make a disambiguation tool. That store both the field and appends to the title. Adding it to the import process as well. So relink can do this most of the time, but having serial number is ideal if one needs to associate many tiddlers to one, and a few other cases, we just provide store the serial number of the "parent" as an example. Then whatever the name the tiddler with that serial number will be found. No need for relink. The only reason I have not published this is I have three solutions, one of which would need a core hackability improvement. To demonstrate the I need to have all four to demo. Custom Actions on standard buttons Automatic or selective unique serial numbers An auto tag generation facility ie given tiddler name there automatically exists a tagname (if not unused) for that tiddler action tags to allow actions tiddlers to be reused in multiple cases. This is my designer challenge to deal with, and attempt to seek assistance/a collaborator in the dev thread unfortunately got no where. Serial number may also need to be disambiguated by wiki name to support interwiki transfers. Regards Tony On Sunday, 24 May 2020 18:25:15 UTC+10, TiddlyTweeter wrote: > > bimlas wrote: >> >> I started working on a TiddlyWiki Zettelkasten edition, but it’s pretty >> hard because in Tiddly it’s hard to handle tiddlers named with a Unified >> Identifier (for example, the tag popup list becomes unusable). Is there any >> example TW from which ideas could be gained? >> > > Good point! > > TonyM replied about idea of using a subsidiary UID he has worked on. Maybe > a useful step. > > But think your point in using the TITLE field as a unique identifier is > right, as that is what it IS, built in. There are several ways of thinking > about it. To give an example of a possible Luhmann style indexing that auto > disambiguates for "Insomnia" ... > > 467-1a INSOMNIA (sleep disorder) > 732-2c IMSOMNIA , 1976 (film) > 1034-1a INSOMNIA, 1982 (film) > > > The point is this example is the shown "title" would be in the caption > field; the real Title is both a UID and human informative. > > Now, to your real QUESTION: "the tag popup list becomes unusable" > > Just wondering if, in the end, that popup could be modified to display a > different field than "title". > > The PROBLEM with going with an arbitrary UID (e.g. random nums; current > date-time) is it has *no semantic content*. > > Luhmann's approach was to have "titling" that is both a unique identifier > AND has some human meaningfulness > > Just thoughts > TT > -- 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/6c35d00b-c3e0-4d28-87cd-4e621bec3c05%40googlegroups.com.
