You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We discussed today with Pablo a few things about the LabManager-LMS-RLMS project and
here are a few notes.
About the project ownership, the labManager code was moved to an organization
in Github and is now hosted in https://github.com/lms4labs
About the project structure, an idea now is to try to separate the different parts of the project. That
means that we will move out the parts that belong to the LMSs and the parts that are specific to each
RLMSs, so that basically we can start removing the hard coded parts.
We asked Pablo for the documentation about the different interactions between the LMS, LabManager and RLMS.
What we have at the moment is a first call that has the authentication/identity of a user and that call goes through
all the parts of the architecture (from user's browser to LMS to labmanager to RLMS) and after that, the requests differ
depending on the response of the requested RLMS.
Right now, the experiment booking process that iLabs has would not be completely supported, and that is why
we have to look into extending the set of calls that will be performed from the user's end to be able to chain a process
of booking and launching.
One approach that could work here, as we discussed, is to implement the RLMS as a base class and have every RLMS
specific code to implement a set of calls.
Another idea is to try to make the most of the SCORM-SCO runtime environment and make the student go through the
'prerequisites' of booking and when that is done, the student can then launch the experiment.
We need a codename for the RLMS part, since it is difficult to pronounce.
The text was updated successfully, but these errors were encountered:
We discussed today with Pablo a few things about the LabManager-LMS-RLMS project and
here are a few notes.
in Github and is now hosted in https://github.com/lms4labs
About the project structure, an idea now is to try to separate the different parts of the project. That
means that we will move out the parts that belong to the LMSs and the parts that are specific to each
RLMSs, so that basically we can start removing the hard coded parts.
We asked Pablo for the documentation about the different interactions between the LMS, LabManager and RLMS.
What we have at the moment is a first call that has the authentication/identity of a user and that call goes through
all the parts of the architecture (from user's browser to LMS to labmanager to RLMS) and after that, the requests differ
depending on the response of the requested RLMS.
Right now, the experiment booking process that iLabs has would not be completely supported, and that is why
we have to look into extending the set of calls that will be performed from the user's end to be able to chain a process
of booking and launching.
One approach that could work here, as we discussed, is to implement the RLMS as a base class and have every RLMS
specific code to implement a set of calls.
Another idea is to try to make the most of the SCORM-SCO runtime environment and make the student go through the
'prerequisites' of booking and when that is done, the student can then launch the experiment.
The text was updated successfully, but these errors were encountered: