Best approach for data into TW, every day?

[Mat]

What would it take for TW to be able to present external dataj so it is workable with, in TW?

 I.e if we assume data like; customer contact info, orders, billing, critical dates etc can be fetched from various places into one place... what would such a place be and what format should the data ideally be in for it to be used as seamlessly as possible with TW?

I assume there is no clean cut answer for this but I'd love to hear your thoughts on the matter.

The background is that I recently started working at a company that uses a load of software tools for internal admin and to capture the workflow....basecamp, freshdesk, highrise, several custom solutions as well as file storage solutions and tools for communication. Several attempts have been made to create some intranet solutions but it is really frustrating that for MANY of problems that we stumble on I feel I could make pretty good solutions with TW in a very short time. ..if it could just fetch the input data somehow.

Thanks!


<:-)

[xanato...@gmail.com]

If you have one TiddlyWiki that is run as a node.js server, it should be easy to write external programs that write tiddler files in the corresponding tiddler folder.

If you want a TiddlyWiki solo HTML file it can be possible only if your wished source is able to give that over a ajax api and it is allowed to get this data (see CORS https://www.w3.org/TR/cors/ )

[Andreas Hahn]

Hi Mat,

when it comes to things like this, it is important to be aware that the "good solution with TW in a very short time" is probably a bad idea in a professional setting. When it comes to sensitive and important data, you practically almost always want an established and tested (and secure, reliable...) solution.

I've played around with interfacing TW to various external data sources, but the way it always worked was that the TW becomes something of a central datastore (or the tiddlyweb-store behind it). And while there have been experiments to interface TW with various database applications, I imagine that if you want a _proper_ solution to your intranet problem, you would want this to go a lot further and get something where TW would be sort of a "User Interface" or "Client" to a more established storage solution in the background (with read and write access).

I think the cool thing is that with some clever engineering, you can make almost any dataset look like a collection of tiddlers.

/Andreas