Dear L.
we are working on some similar problems and solutions, turning
dokuwiki a logging platform as well as a non-sql database. I have
added two new fields to the bureaucracy plugin implementing selection
fields from file or from search queries in the page names of
dokuwiki. An early version I uploaded to the git website, but
so far none cared about it.
Here is the link:
https://github.com/splitbrain/dokuwiki-plugin-bureaucracy/issues/193
I am working on a search action to be integrated, which could pick up
values from pages based on the filled our form, and I will also need
a report generator feature, which is an extended version of the
include plugin.
Because the dokuwiki itself is an excellent non-sql system, I do not
talk here about the data / struct plugins, which are based on adding
an sqlite database to store extra data. But you still may find it
interesting.
Prefilling: on the one hand bureaucracy has default values possible.
On the other hand, making this dynamic is an interesting question. I
guess it would require parsing a page and assign default values
accordingly. As far as I can tell, this would be a new plugin
practically speaking.
One more thing: with the pagemod you can add new entries to pages
dynamically. Thus, with one form you create the page, with another
you can just add new entries to the table row-by-row. If that solved
your problem I can not tell. 8)
Bests,
Tamás
#This e-mail is a reply to the message of Lorenzo Bernardi
<lorenzo.bernardi@xxxxxxxxxxx>, sent on Tue, 3 Jan 2017 21:27:32
+0100:
#"--
Hello and happy new year to all,
we are using dokuwiki as a logbook for experimental setup. That
is
user after doing an experiment on a machine should record what they
have done to keep a trace and for some analysis and accounting. We
have different machines and so different form that were created
using the bureaucracy plugin and store in a sqlite3 database using
the data plugin. We are thinking of some improvements and we don't
know what would be the best choice. We don't have a lot of php
knowledge but depending on the response we might take time to gain
some knowledge.
One of the field that is needed for all experiment is the user and
this thanks to the authentication module and the bureaucracy plugin
is already available.
One other field is the project for which the experiment was made. The
project depends on the user. For now we have a list but it has to be
modified by hand for all the form that are in the dokuwiki. Can we
store a list of all the projects in a variable that can be used for
all the forms? or better can we set a variable per user?
One of the feature we have implemented with a workaround is to pre
fill the form by parsing a file. Some experiments use a recipe file
or produce a log that we can parse and upload to the form. For now
it is down by calling a url which is a django app that parses the
file and produce a url with POST variables that fill the forms (may
be I'm not clear here so if you need more explanation I can answer).
This feature is a key feature because it simplifies the input and so
we have less errors than if filled by hand. So the questions are is
there a way to make it already? Should we extend the bureaucracy
plugin or rethink a new plugin? I don't know if this would be easier
but I was wondering if you couldn't use a javascript code to parse
the file and preload the data. But here I'm not sure it would be
simpler. One of our problem is that some experiments are performed
on several samples and we would like to get a form for each sample.
So any idea here would be welcome.
A third point is that we would like user to perform queries in the
database by themselves is it possible to do this already?
Thank you for your attention
Sincerely,
L.
PS sorry if I submitted twice this email since I don know if my
first try succeeded or not
#end of previous message"
