Thank you so much for the detailed and clear information. I can live
with the scripts on a terminal window, but I imagine that others will
be clamoring for a GUI admin page.
I never thought the "Database Manager" doc would be about
administration. Perhaps another set of links that says "How to manage
accounts", "How to add students," etc. would be helpful. This is
because when I think about database management I'm thinking about back
ups, roll backs, and major surgery of the db. It's something I would
not dare touch if I'm admin of a remote lab software. I'm too scared
to mess with it as I might whack the system, specially if its a
A separate list of documents, or links to these documents but retitled
and minus the scary dev details may be useful for newbs like me. I'm
thinking in terms of very basic manuals and walkthroughs for students,
teachers, and non-techie admins. This would be within the theme of
teaching...involving pedagogy, assessment and learning theories. But
I'm saying this openly to the community of weblab users, and not
necessarily to devs. The devs had already done a fantastic job at this
software and had been gracious enough to share it to the world. There
might be other users who might have applied this software, or are
thinking of using this in general science education (probably in K-12
or introductory science courses) whose users are not as sophisticated
as students of engineering or advance sciences; users who might have
the time to blog or share a tutorial about this software. At least
this is what I have in mind while trying to evaluate weblab.
Again, thanks for the response. It's another step forward for me in
learning more about weblab and how to implement a remote teaching
> Added a link <http://code.google.com/p/weblabdeusto/source/detail?r=1159
> the database manager.
> How do you set a weblab administrator account?
> Here in the University of Deusto, we are the developers and the maintainers
> at the same time. Therefore, we have made scripts of the common tasks we do
> (add user, add group, add user to group, grant experiment to user, grant
> experiment to group...). Previously we did this in a bunch of separated
> but now they're integrated in the Database
> Since it is a script, only the system administrator of the servers can
> perform these tasks, and we want teachers to be able to handle their
> students. We placed efforts in creating an initial version of the
> the moment, it only shows experiment usage in an graphical,
> easy-to-filter way. It does not still handle user management (although
> efforts are being
> the next release). You can check it with the "student1" account by
> clicking on the "Administration panel" in the client.
> However, sometimes we haven't made a script for the very uncommon tasks,
> such as creating administration accounts, and instead we have directly added
> it with SQL code in production. At the moment, "administration account" is
> only used to grant privileges to the web administration panel, which still
> does not provide too much functionality. You can check this by comparing the
> behaviour of the user "student1" with "password" and the user "any", with
> "password", which does not have privileges to use the administration panel.
> However, you can perform common administration tasks by clicking on.
> > The deployment steps did not ask for this and there is only
> > the student1, password account that is preset.
> There are a couple of accounts