My own findings:
Anyone?
At the moment, bulk import is possible via code you would make
yourself that uses the API[1].
I do have plans to make bulk import easier for various use cases and
for TWC in particular I've created a ticket[2].
[1] https://tank.peermore.com/tanks/docs/API
[2] https://github.com/cdent/tank/issues/126
Assuming you have a bag named "extendedbrain" which contains some
tiddlers that are tagged "ExtendedBrain" you can get all the tiddlers
in that bag as:
https://tank.peermore.com/bags/extendedbrain/tiddlers
and just the ones that are tagged "ExtendedBrain" with:
https://tank.peermore.com/bags/extendedbrain/tiddlers?select=tag:ExtendedBrain
Assuming you have a bag named "extendedbrain" which contains some ...
You'll need to read more than just those two pages, also pages
linked from them, for example [...]
If you're goal is only to allow something people can import, then
you ought to be able to put the wiki HTML file on a web server as a
static file and have people import that URL from within their twc.
The reason for using a server side would be if you want to allow
easy access to updating the content on the server (that will later
be downloaded by other people).
If you're goal is only to allow something people can import, then
you ought to be able to put the wiki HTML file on a web server as a
static file and have people import that URL from within their twc.
Just tried that out: the server needs to be CORS enabled. At least that is what the import functionality is telling me if try to open my TWC on this server.Darn.
Header set Access-Control-Allow-Origin "*"
Although if TWC is static on the server it is not possible to filter via URL like ?select=tag:ExtendedBrain.
[1] http://enable-cors.org/server_apache.html
That's not going to work for the describe hack because you're at the
wrong layer. [...]