lms4labs/labmanager — pull request #8 by sergiobuj (2012-12-12 19:56:18+00:00)
Title: Lms admin workflow

I changed the workflow according to the new requirements.

Now the procedure is the following:

[After having the LMS registered in the Labmanager and the tool configured in the LMS]
1. The LMS admin creates an admin tool as an activity (could be set invisible) and will request access
to all the experiments that the context needs.

2. The Labmanager admin will make a decision on every request.

3. Instructors and Learners will get a complete list of allowed/pending experiments when they use a tool.

A list of all experiments will be visible on every tool, the standard defines an attribute to determine which tool under the context is requesting the information, but since the workflow changed, maintaining this information was adding complexity to the model.
If having this information proves to be a requisite, then it should be easy to add.

After pulling this changes, the database needs to be recreated.
python deploy.py -cdu

Please review the changes, and let me know if something is missing.