Hi Dave, Interesting use case.
On Sunday, September 27, 2015 at 4:42:25 PM UTC+2, Dave wrote: > > (having decided that I'll be using TW5 with nodejs) Would it be better to > make one TW per client and import any design changes from a "master" TW > file (that was the plan with the TWc version), or would it be better to > have one single TW5 (synced between computers) and access the multiple > client "files" by unique tag in the one system? I think your usecase can be achieved, with some clever designed tiddlywiki.info files. ... eg: - You can create a so called TW edition per patient. - This edition can include the basic layout + eventual modifications from a UI-master edition. The tiddlywiki.info file supports an option: includeWikis see: https://github.com/Jermolene/TiddlyWiki5/blob/master/editions/de-DE/tiddlywiki.info#L18 ... - I'm using it for the German translation editions. Where de-AT contains most of the content and de-DE only contains the differences. - In your case the "UI-master" can contain your layout changes and the patient edition contains the individual content tiddlers. - If you need some information, that should be global for every patients eg: a collection of useful exercises, you could include a second edition, that contains them. So you only need to edit / add new exercises once in eg: exercises-master. > And if that were the case would it be better to develop it in tiddyweb > (accessible only through intranet)? TiddlyWeb would be a possibility, if you know hot to work with the python programming language. At the moment there is no easy way to work with tiddlyweb and TW5. > Here's the use case: I'm a chiropractor seeing multiple patients a day, > keeping track of various symptoms and test results that change gradually > over time and depending on progress generates the need for various > modifications of treatment modalities, e.g. exercises, etc, as well as > running suggested prioritized diagnosis suggestion lists and plans of > management options. > As I wrote. One edition per patient. > Although it would be nice and tidy to have one file per patient, I also at > one point in the future want to be able to compare findings between > patients, like for research (how many patients that I treated by method X > got better by Y points over timespan Z; or, what's the average first > measurement of neck range of motion between age 30 and 50?)), mainly using > fields and tags. > As Andreas wrote, having a good concept for tag and field names at the beginning, will help you in the future. With the above mentioned tiddlywiki.info file, it would be possible to create a "big" edition, that "includes" all patients. You only need to take care, that there are no "naming problems". Eg if there are 2 tiddlers named "Mario", that last one, that is included will win. > Any time I describe what I want, most people just say I should build a > database program, but a) I have no experience with them and b) I just > really like tiddlywiki because its so flexible. > > Lastly, I'm an intermediate level user with no formal computer programming > training, slow but steady learner. I've modified plugins (TW classic) but > never made one from scratch. > You are right. "Feeding" a database with all the info is an option, but you will need to create a UI. ... With TW you get an advanced UI and very powerful tagging options and "list-widgets" to create different overviews. ... So imo it depends on your own preferences. .. > Any suggestions for a scenario like this? > > Oh, one last thing... if I ever actually achieve what I'm dreaming of, > what are the monetization implications given the current licence? Could I > sell this to other chiropractors/ companies? If not, that's fine - I'm > going to proceed anyway and may just eventually just release it if it > passes muster. > As Andreas wrote. TW is BSD licensed <https://github.com/Jermolene/TiddlyWiki5/blob/master/licenses/copyright.md>. that lets you sell your modifications. Conclusion: IMO a basic "single user" application, for your own use case, should be relatively straight forward. - It is possible to start several servers at the same time. - You just need to take care, that you don't insert content into the "wrong" user page, if you opened several of them at the same time! - You'll need to start a new nodejs server if you want to access a new user. - This can be a disadvantage, since such servers need to be started from the command line. - Depending on your operating system, starting new users can be automated. Question: Which OS do you use? have fun! mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6f8a63da-94e6-48b4-9f4c-e1f7d58057b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
