Thanks @Flibbles that gives me a lot to work with, but I will just illustrate the simple example to be addressed using relink, or some other rename handler.
If you use the currentTiddler title as the index to a JSON Data tiddler as I did in Tips and commentary - Notes on tiddlers stored in a data tiddler it will look like this;
{
"No-touch notes": "Original Idea",
"view/edit-notes": "New example as given"
}
- type = application/json
So in the above example and many other possible cases the title of a tiddler is the key
The above two tiddlers exist in my wiki âNo-touch notesâ and âview/edit-notesâ (without the quotes).
- It is true nothing defines the key as matching a title, and thus could be an appropriate subject of renames / relinks.
- however I imagine we could nominate itâs tiddler
$:/note-databaseas being a data tiddler whose primary key is a title and thus should be renamed.
I think this is an example of a common pattern that may be used more and more often given the primacy of the tiddler title, which is of course a very powerful feature in relink already.
Going forward
- I am hoping to achieve something related with a tiddler that has the compound title
tiddler1 & relationshipname & tiddler2that will be renamed if tiddler1 or tiddler2 is renamed.- In this case these titles may only be âbacklinksâ, or named in a fieldname value.
Absolutely no expectations/pressure from me, I am just raising it with you as you are the expert 