Forum .LRN Q&A: Re: .LRN Roadmap (Request for Comments)

Collapse
2: Re: .LRN Roadmap (Request for Comments) (response to 1)
Posted by Rocael Hernández Rizzardini on 04/29/03 01:57 AM
Carl,
a few comments / questions:
Course evaluations or grade book is something like a grading system (for keeping all the grades that a student is having through the course)? and what about a online testing tool? is covered by one of the previously mentioned or by the complex survey?

new-portal means that an openacs installation will be able to handle multiple dotLRN instances?

Also I would like to see extension that defines an standard for creating a syncronization between university administrative system and dotLRN (class, users, user-class assigment, etc) creation.

Will be nice to have another package to have all the messages being sent to mobile phones (SMS), probably to make it wide useful by creating something to comunicate to provider sites that offer to send SMS to their subscribers.

I've been working on this and more stuff that I would like to see on dotLRN 2.0, when I have more info I could post it here.

Collapse
3: Re: .LRN Roadmap (Request for Comments) (response to 2)
Posted by Carl Robert Blesius on 04/29/03 02:53 AM
Rocael:

Yes, the grade book will be a place to store a users grades.

Complex Survey should cover most online testing needs.

New-portal in the diagram represents moving infrastructure out of .LRN that should be in OpenACS. https://openacs.org/forums/message-view?message_id=92143 We want to share as much infrastructure as possible with other projects forming around OpenACS. Another example would be getting .LRN to use a  new and improved acs-subsites https://openacs.org/forums/message-view?message_id=92524 (check out the mockup link in the first post)

Synchronization with back-end systems is something Heidelberg needs. We hope to cover do this with the cooperative funding of the AuthN work. https://openacs.org/forums/message-view?message_id=92263

A SMS broker exists (just search the boards).

Please post anything you would like to see in .LRN 2.0 here.

Collapse
14: Re: .LRN Roadmap (Request for Comments) (response to 3)
Posted by Oscar Bonilla on 05/14/03 04:53 PM
--- Carl Wrote ---
Synchronization with back-end systems is something Heidelberg needs. We hope to cover do this with the cooperative funding of the AuthN work. https://openacs.org/forums/message-view?message_id=92263
---

Synchronization is only part of the problem. For .LRN there should also be an API (or a standard way at least) for mapping users to courses, professors to courses, importing course catalogs, etc. Usually universities already have databases with all this info and .LRN needs to be able to communicate with this database.

One of the hardest jobs was integrating GES with the universities database.