Modelling Learners Preferences

Created by Olga C. Santos, last modified by Olga C. Santos 09 May 2007, at 04:57 PM

Modelling Learners Preferences

 Overview

 

This wiki was started in the Workshop on Experiences on Accessible eLearning Platforms at OpenACS and .LRN Spring Conference, Vienna 2007. More info in the corresponding presentation. 

As pointed out by Daveb, the section has been renamed to Modelling Learnes Preferences, since user preferences are separate from a learning system.

The goal is to build in OpenACS support for learners modelling by gatherig data about learners from different sources:

• Learning Styles (Felder test)
• IMS-QTI questionnaires
• Active (create) and passive (read) interactions

There is a need for the integration with processing mechanisms and specifications representations, such as data mining algorithms (Weka), multi-agent sytems (JADE agents) or RDF management (Sesame toolkit), among others.

Two scenarios:

• Semantic based (specifications)
  
• Usage of the platform services
  

Other ideas:

• Use the same API to produce the layout (SCORM and IMS-LD)

Comments:

• bottom up approach
  

Standards and Specifications:

• IMS-LIP
• CC/PP
• SCORM CMI
• URC
  
• ...
  

Community members showing interest:

• aDeNu Research Group (UNED)
  
• UC3M: can offer the information gathered to the author to provide the learning path
  
• ...
  

TO DO:

• Extend user tracking
• Extend data model
•  
• ...

Last modified: 2007-05-09 16:57:54.231829+02 

Goals / Ideas

Created by Caroline Meeks, last modified by Nima Mazloumi 26 Apr 2007, at 05:16 PM

Goals

•  Adoption
• Recognized as a Web 2.0 Leader
• Documentation
• Training/ Learning Curve
• Brand recognition (OpenACS/dotLRN)
• Missing Functionality
• Consolidating Functionality
• Developer Collaboration
  

Ideas & Votes

Marketing	18
Top 10 Hall of Shame of Packages / Bugs	5
Better categorization of Bugs	5
Only include modules of certain quality in future releases	19
Incentive to announce code and/or allow charge of code	10
How to behave - when modifying code	5
Process for submitting & processing patches	9
Move official documentation to Wiki	15
Small chunks of advice / code , recipes	5
Create a way to contribute learning material, presentation, marketing material	13
Clean frontpage / website for .LRN / Openacs	16
OpenACS book	16
Move to sourceforge	17
Move to a non viral license like BSD	2

 

Notes

What are you working on?

• fix package per page
• create a "twitter" type page where you write what you are doing
• PO Client and Security service
• auto search of forums & wiki

Pimping the websites

• different sections for different persons (developers, users, ...)
• e-learning course on how to work with the toolkit, curriculum integration
  
• 
  

Members

Created by Rocael Hernández Rizzardini, last modified by Caroline Meeks 23 Mar 2007, at 01:34 AM

Consortium Members (2007)

---

 Representative / Organization

1. Janine Sisk, Furfly LLC *
   
2. Malte Sussdorff, Cognovís GmbH & Co. KG *
   
3. Erik Valevatn, University of Bergen *
   
4. Carl Robert Blesius, Mass General Hospital *
   
5. Caroline Meeks, SolutionGrove *
   
6. Rafael Pastor Vargas, CInDeTec, UNED *
   
7. Cyrano Ruiz, Universidad Galileo 
8. Dario Roig, Universidad de Valencia *
   
9. Alfred Essa, Minnesota State Colleges and Universities *
   
10. Vivian Aguilar, Viaro Networks *
    
11. Gustaf Neumann, Vienna University *
12. Carlos Delgado Kloos, UC3M *
    
13. Tracy Adams, ACSPropel *
14. Giancarlo Luxardo, SII *
15. Mark, pumptheory.com *
16. Gregory Hancock, University of Sydney *
17. Fernando Albuquerque, Tekne Digital *
18. Uiri Sapaio, YABT.
19. Pablo Arozarena, Telefonica I+D, Spain.
20. Rob Ross, Museum of Science Boston
    

* initial request for invoice sent
** invoice sent

 No reply from them yet.

.LRN Zen Project: Packages HTML clean-up

Created by Emmanuelle Raffenne, last modified by Carl Robert Blesius 20 Mar 2007, at 05:25 AM

Project Zen Deadline / Goal: March, 2007

OpenACS packages

Package	Who's in charge	Comments
acs-subsite	Lee
acs-templating (this includes the form and list builder templates)	Avni, Emma	DONE!!!
acs-tcl
acs-lang
search
acs-admin

.LRN packages

Package	Who's in charge	Comments
new-portal	Don	Emma: "customize layout" page cleaned. HTML validation OK.
dotlrn + dotlrn-portlet	Mark, Carl	First pass done, need to review again after list builder additions
forums + forums-portlet	Mark, Carl
notifications	Carl	DONE - Carl is just going to double check
calendar + calendar-portlet	Avni, Mark Emma: HTML cleanup	Mark is done with this package
file-storage + fs-portlet	Mark
assessment + assessment-portlet	Carl, Mark
lorsm + lorsm-portlet	Emma	Form sections fixed.
news + news-portlet	Mark, Carl
faq + faq-portlet	Cynthia, Avni, Jeff, Rob	making slow progress
static-portlet
attachments
general-comments
bm-portlet	Rob
evaluation + evaluation-portlet
chat + chat-portlet	Rob
lars-blogger + weblogger-portlet
random-photo-portlet
dotlrn-homework
dotlrn-syllabus
photo-album + photo-album-portlet	Avni, Carl
survey + survey-portlet
categories

Documentation Credits

Created by OpenACS community, last modified by Torben Brosten 18 Mar 2007, at 09:38 AM

Documentation Credits

Bibliography: Where did this document come from?

This document is really just plagiarism from a number of documents that came before it. If something is used without proper credit, let us know so we can fix it right away.

The short bibliography:

• OpenACS Documentation Versions 4.6.2 to present were edited by Joel Aufrecht.
• ArsDigita installation guide
• OpenACS 3.x installation guide
• Gilbert Wong's FreeBSD installation guide
• Vinod Kurup's Brief OpenACS4 installation guide
• Joel Aufrecht's OpenACS 4.5 Quick Guide

Known authors and contributors

Acknowledgments for versions of the above documents go (in no particular order) to Bryan Quinn, Adam Farkas, Brian Stein, Doug Hoffman, Ravi Jasuja, Hiro Iwashima, Ryan Lee, Jonathan Goler, Audrey Mcloghlin, Doug Harris, Zvi Boshernitzan, Michael Yoon, Cesar Brea, Dennis Gregorovic, David Fullagar, Chris Spears, Kevin Tupper, Michael Duffy, Simon Carstensen, Dave Bauer, Tracy Adams, Greg Haverkamp, Philip Greenspun, Jin Choi, Sean Yamamoto, David Cohen, Chris Rasch, Richard Li, Jon Griffin, Roberto Mello, Gilbert Wong, Don Baccus, Ben Adida, Michael Cleverly, Janne Blonqvist, Jonathan Ellis, Janine Sisk, Jade Rubick, Chris Hardy, Jonathan Marsden, Vinod Kurup, Charles Hall, Tom Jackson and Karl Lehenbauer.

Others who have contributed to this document: Robert Taylor, Ryan Gallimore, Gustaf Neumann, Torben Brosten, Don Baccus, Roberto Mello, Talli Somekh, Dave Bauer, Jim Lynch, Jon Griffin, Daryl Biberdorf, Bjorn Thor Jonsson, Jade Rubick, Fred Yankowski, Dan Chak, Sebastiano Pilla, Reuven Lerner, Malte Sussdorff, Stan Kaufman, Pascal Scheffers and Rocael Hernández.

Contributers to xowiki documents, including this one: en:contributors 

Finally, much appreciation and thanks goes to the OpenACS community, who have provided much valuable feedback in the fora, which compromises the goals of this documentation.

.LRN Zen Project: Bug Bash Signup

Created by Avni Khatri, last modified by Avni Khatri 16 Mar 2007, at 07:06 AM

.LRN/OpenACS Zen Bug Bash Signup

Please signup for any day you can.
 

17 March 2007 (Saturday)

Name	Location	Hours Available (GMT)	Role(s)
Avni Khatri	Los Angeles	After 1PM PDT (20GMT)
Mark Wylie	Boston
Cynthia Kiser	Los Angeles

 

18 March 2007 (Sunday)

Name	Location	Hours Available (GMT)	Role(s)
Avni Khatri	Los Angeles	10AM-6PM PDT (17-1GMT)
Mark Wylie	Boston
Emmanuelle Raffenne	Madrid (CET)
Carl Blesius	Boston (15 Claremon 1st Floor, Somerville, MA)	10:30AM to 7:00PM Local Time (14:30 - 23 GMT)	Local Organizer
Cynthia Kiser	Los Angeles

 

 

 

 

10 March 2007 (Saturday)

Name	Location	Hours Available (GMT)	Role
Avni Khatri	Los Angeles
Mark Wylie	Boston
Emmanuelle Raffenne	Madrid (CET)
Malte Sussdorff	Hamburg (CET)		Learn about ZEN and the changes
Jeff Wang	LA/San Diego	10am-2 pm (PST)
Carl Blesius	Boston (15 Claremon 1st Floor, Somerville, MA, 02144)	10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)	Local Organizer

 

 

11 March 2007 (Sunday)

Name	Location	Hours Available (GMT)	Role
Avni Khatri	Los Angeles
Mark Wylie (absent for a few hours)	Boston
Emmanuelle Raffenne	Madrid (CET)
Malte Sussdorff	Hamburg (CET)		try to upgrade openacs.org to 5.3.1 with ZEN
Carl Blesius	Boston (15 Claremon 1st Floor, Somerville, MA, 02144)	10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)	Local Organizer
Michael Aram Christoph Haberberger	Vienna University of Economics	12:00 to 17:00 GMT (13-18 CET)
Michael Totschnig	Vienna University of Economics	19:30 to 21:00 GMT (20:30-22 CET)

 

3 March 2007 (Saturday)

Name	Location	Hours Available (GMT)	Role(s)
Avni Khatri	Los Angeles
Mark Wylie	Boston
Emmanuelle Raffenne	Madrid (CET)
Carl Blesius	Boston (15 Claremon 1st Floor, Somerville, MA)	10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)	Local Organizer
Cynthia Kiser	Los Angeles	after 4pm PST

 

 

4 March 2007 (Sunday)

Name	Location	Hours Available (GMT)	Role
Raúl Morales	Madrid
Mark Wylie	Boston
Emmanuelle Raffenne	Madrid (CET)
Carl Blesius	Boston (15 Claremon 1st Floor, Somerville, MA, 02144)	10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)	Local Organizer
Nima Mazloumi & Co.	Mannheim (CET)	12:00 AM - 6:00 PM

 

 

 

Installing OpenACS on Solaris

Created by OpenACS community, last modified by Torben Brosten 07 Mar 2007, at 05:18 AM

Should you decide to Install OpenACS from source using general en:openacs-system-install instructions, refer to these notes for changes:

See threads:

• Tips or Gotchas for Install on Solaris 10
• Solaris 10 fails to unpack openacs-5-2-*.tar.gz
• Missing tclsh on Solaris [9] - how to fix?

.LRN Zen Project: Bug Bash

Created by Avni Khatri, last modified by Nima Mazloumi 03 Mar 2007, at 10:12 PM

.LRN/OpenACS Zen Bug Bash

We are planning on having 2 weekend bug bashes. The goal of these bug bashes is to facilitate the OpenACS core and dotLRN package cleanups in order to meet the Zen Project goals and deadline (12 March 2007).  Please signup for any of the four days you can help.  We can use people at all skill levels. You only need to have basic HTML knowledge.  (i.e. you don't have to be an OpenACS expert)

Please try to signup atleast 2 days before the scheduled bash. Once people have signed up, we will assign packages / pages and roles to people.

Dates & Signup

1. 3 March 2007
   
2. 4 March 2007
   
3. 10 March 2007
   
4. 11 March 2007
   

Locations and Coordinators

1. Boston/Somerville, MA - Carl Robert Blesius & Mark Wylie
   
2. Madrid - Emmanuelle Raffenne
   
3. Portland, OR - Don Baccus
   
4. Los Angeles - Avni M. Khatri
5. Virtual World - IRC at the #openacs channel
6. Mannheim - Nima Mazloumi, Sven Schmitt, Stefan Wurdack, Ke Zhang
7. please add your city and name if you can help coordinate

Guidelines

1. Goals of the Zen Project
   
2. Zen Standards (Go here to get details on how to make OpenACS Zen)
3. Package & Page Assignment
4. Package & Page Completion
   

Bug Bash Jobs and Directions

Before you start, join the online bug bash space by logging into the openacs chat: https://openacs.org/irc/ 

Bug Tester

Job description: test, resolve, close, reopen, comment, add info below to tickets 

Bug Sorter

Job description: check, sort, assign, set priority, add info below to tickets

Bug Basher

1. Check Zen and 2.3 Bugs
2. Grab bug (assign it to yourself)
3. Make sure it is correctly prioritized (1 and 2 will be fixed for 2.3 release)
   
4. Make sure it is labeled for the 2.3 and/or Zen
   
5. Paste the following info into the ticket:

   		Key: [+]=done/yes/selected, [-]=does not apply, [?]=I have no idea
   
   		[ ] Filename: packages/
   		[ ] URL: 
   		[ ] HTML 4.01 Transitional
   		[ ] 508 Bug
   		[ ] Level A Bug
   		[ ] Level AA Bug
   		[ ] Level AAA Bug
   		[ ] Contrast
   		
   		Comment/Details: 
   		
   		
   	

6. Follow the pathway to Zen as outlined on the Zen Standards Page
7. Close or reassign as you complete steps outlined on that page (make sure and check items off in the list above and categorize bugs as you make progress)
   

Pastebin for irc

Created by Torben Brosten, last modified by Dave Bauer 12 Feb 2007, at 08:37 PM

debian:/usr/local/aolserver/bin# ldd /usr/local/aolserver/bin/nspostgres.so
+ ldd /usr/local/aolserver/bin/nspostgres.so
                libpq.so.5 => not found
        libnsdb.so => /usr/local/aolserver45/lib/libnsdb.so (0x40007000)
        libnspostgres.so => /usr/local/aolserver45/lib/libnspostgres.so (0x40010000)
        libnsd.so => /usr/local/aolserver45/lib/libnsd.so (0x40018000)
        libnsthread.so => /usr/local/aolserver45/lib/libnsthread.so (0x4007a000)
        libtcl8.4.so => /usr/local/aolserver45/lib/libtcl8.4.so (0x40083000)
        libdl.so.2 => /lib/tls/libdl.so.2 (0x40135000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40139000)
        libm.so.6 => /lib/tls/libm.so.6 (0x40148000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4016a000)
        libc.so.6 => /lib/tls/libc.so.6 (0x40173000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

.LRN Motions (DRAFT)

Created by Carl Blesius, last modified by Gustaf Neumann 01 Feb 2007, at 10:43 AM

[DRAFT] .LRN Motions Document

Background

A .LRN motion is a formal statement of a proposal or question to the .LRN Core Team for consideration and action.

Steps in Presenting .LRN Motions 

1. Items are presented by .LRN members to the .LRN Core Team in the .LRN Motions Forum. The title must have the motion number, "Proposed", and a short description in it. Example: ".LRN Motion #1 (Proposed): .LRN Motion Rules"
2. A .LRN Core Team (LCT) member then must second motion. The title must have "Seconded" in it. Example: ".LRN Motion #1 (Seconded): .LRN Motion Rules"
3. Debate. Anyone may post a thread followup. Thread followups must directly address the original .LRN Motion.
4. Any LCT member may vote Approval or Disapproval of a Motion. These replies can be titled "Seconded", "Thirded", or "Vetoed".
5. Once we have a final status for a TIP, the original title is edited to reflect that.
   ".LRN Motion #1 (Approved): .LRN Motion Rules"
6. All LCT members must subscribe to the forum.
7. If a new Motion gets Seconded and Thirded and not Vetoed in the first week after posting, it is Approved. If it gets at least one Veto, the proposer must summarize objections and call for a full vote in a reply titled "Call for Full Vote". Previous Second/Third/Veto votes are then null, and the LCT members vote with replies titled "Approve" or "Disapprove". If, after two weeks of full voting, the Motion has two thirds approval, it is Approved. If not, it is Disapproved.
8. After a Motion is Approved or Disapproved, the thread is closed to new posts.
9. If a Motion is approved, a ticket is entered into the bugtracker under the proposer's name.