Jeremy,
Some thoughts on this;
In my view there are some configuration options that may be helpful in this and other solutions; The need here is for them to be standard tiddlers so different designers and developers can refer to the same tiddler.
- A tiddler containing a wiki-name eg $:/config/wiki-name (not unlike site title but URI compatible)
- A tiddler containing a wiki-address eg $:/config/wiki-address (Such as domain/path or IP address, must be populated, and could be used to add a source field to tiddlers to be dragged.
- A separate wiki-registration tiddler eg; $:/config/wiki-registration this would allow people to uniquify a reference to a specific wiki by combining this value with $:/config/wiki-name and perhaps in future we could obtain a registration number from a shared resource to get a form of Global wiki identifier.
- Possibly a transfer-date field so tiddlers can retain there modified and created dates but record when the tiddlers were obtained from the source tiddler. In effect supporting change control and listing transferred tiddlers.
The tiddler names and fieldname are irrelevant, you choose. What is important is that they are chosen and documented so that they become a naming standard from an authorative source. They may not even need to be in the core just a standard.
If you went ahead to add a few such tiddlers, the community could possibly suggest a few more. I have at least two others in mind.