Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notes about the meeting with Pablo. Oct 22/2012 #9

Open
sergiobuj opened this issue Oct 22, 2012 · 0 comments
Open

Notes about the meeting with Pablo. Oct 22/2012 #9

sergiobuj opened this issue Oct 22, 2012 · 0 comments

Comments

@sergiobuj
Copy link
Member

We discussed today with Pablo a few things about the LabManager-LMS-RLMS project and
here are a few notes.

  1. 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.

  1. 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.

  2. 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.

  1. We need a codename for the RLMS part, since it is difficult to pronounce.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant