Actualy I did something similar for what I call Data Tiddlers (plugin-type=data). The data tiddlers exist as shadows until intentionally edited, come out of the archive in effect (tiddlers). I also added a tab to the plugins along with plugins/themes designed to handle data tiddlers.
Something I have intended to do for a long time is build a mechanisum to update the data plugin tiddler, in this case the archive tiddler, by writting back all the edited tiddlers into the archive and updating a version. I must admit it seems to have a high cognative demand, so have experimented but not built it yet.
An interesting use would be to
- Build a data/archive plugin from filtered or selected tiddlers (option to delete on archive)
- move or copy tiddlers to archive/data plugin
- export a “data/archive” plugin
- import it elsewhere,
- archive more tiddlers (option to delete on archive)
- return to 1 and move onto another wiki
Similarly one could do with this;
- code and plugins to build a package that would accumulate content from multiple wikis and happily be imported to multiple wikis.
- One could remove the achive data plugin and reimport only when needed or to archive more tiddlers including updated ones
- Capture a set of config and interface customisations - config plugin
- use this to capture changes to a wiki as a reviewer and send to the wiki owner for review and acceptance (include a diff viewer) difference between tiddler and shadows.
- I have long wanted to provide this as a type of multi-user/contributor method
This is related to Allow control of fieldnames included in JSON and CSV exports/imports Export to tiddler not only download files
Save into a archive/data would also benifit from setting an archive timestamp
[Edited] See example here https://test-data.tiddlyhost.com/