View · Index

Weblog

Filtered by category .LRN, 1 - 10 of 23 Postings (all, summary)

2006 Fall Conference Submissions and Program

Created by Carl Robert Blesius, last modified by Gustaf Neumann 22 Mar 2019, at 11:17 PM

OpenACS/.LRN Fall Conference 2006

 

Day 1 (Nov. 1) - International Workshop on Community Based E-Learning Systems

Location: Harvard Conference Center Rotunda  

07:30-08:30 Continental Breakfast and onsite registration

08:30 Opening Remarks and Orientation

08:40 Keynote: Creating Passionate Users

What do game designers, neuroscientist, and filmmakers know about creating passionate users? How can we exploit the way the brain works to reach our users/learners at a deeper level that inspires their attention, enthusiasm, long-term loyalty, and evangelism? New research points to a different way to craft interactive experiences that get the user's attention and--most importantly--KEEP it. For today's learners, sound instructional design is no longer enough.

In this session, we'll explore ways to work around the brain's natural filters that keep our message from getting in. We'll cover how to give interactive experiences an almost addictive quality--to keep our users engaged and wanting more. There's a place where science and entertainment meet that knows what turns the brain on, and we'll look at simple, powerful, easy-to-implement ways to make that happen. Whether you're building e-learning or plain old paper documentation, you'll learn techniques for creating passionate users/learners that you can put to work immediately.

Kathy Sierra

Kathy Sierra spent the last decade as a game developer, master trainer for Sun Microsystems, and creator of the first New Media Interaction Design courses for UCLA Extension's Entertainment Studies Department at the IBM New Media Lab. Together with her partner Bert Bates, Kathy created the bestselling and award-winning "brain-friendly" Head First book series. She's the original founder of the largest non-commercial software development community, Javaranch.com, and author/creator of a Technorati Top 100 Blog. When she's not working on ways to help humans learn more quickly, she's playing with her three super-smart Icelandic horses.

09:40 Keynote: Photo.net and ACS

Philip Greenspun will talk about: 

  • How is it possible that ACS is still viable?
  • The history of photo.net and ACS
  • stuff he and others are working on at photo.net

Philip Greenspun has been in and around the Massachusetts Institute of Technology since 1979. He alternates between teaching traditional electrical engineering classes and teaching "Software Engineering for Web Applications" (6.171), a course that he co-developed with Hal Abelson. This has been a successful course at MIT and is being used by computer science departments at 20 other universities around the world. Greenspun is the author of two textbooks used at MIT, including Internet Application Workbook (available at http://philip.greenspun.com/internet-application-workbook/). Greenspun is an instrument-rated private pilot and has flown his Diamond Star across most of the North American continent and two-thirds of the Caribbean islands.

In the mid-1990s, Greenspun founded the Scalable Systems for Online Communities research group at MIT and spun it out into ArsDigita, which he grew into a profitable $20 million (revenue) open-source enterprise software company. The software is best known for its support of public online communities, such as www.scorecard.org and photo.net, which started as Philip Greenspun's home page and grew to serve 500,000 users educating each other to become better photographers.

The learn@wu project

Gustaf Neumann - Chair of Information Systems and New Media at the University of Economics and Business Administration (WU) in Vienna, Austria

How do you create one of the most intensively used e-learning platforms worldwide? Gustaf explains.

Communities of users to support an open LMS: the Moodle perspective

Martyn Cooper - Head of Accessible Educational Media group at the Open University of UK

Martyn gives us a little peek into an alternate universe.

10:45-11:00 Coffee Break  

User-centred approach in LMS: Adaptiveness and Accessibility

Jesús G. Boticario - Head of aDeNu Research Group at The Universidad Nacional de Educación a Distancia (Spain)

Jesús introduces a new (.LRN related) European funded project focused on making sure that the technology that mediates lifelong learning does so accommodating the diversity of ways people interact with technology and the content and services it delivers.

E-Lane: European and Latin American New Education

Carlos Delgado-Kloos - Head of the Department of Engineering and Telematics at Universidad Carlos III de Madrid

Carlos gives us a quick overview, summary, and results of the E-Lane project that is coming to a close, but will live on in our software.

E-Learning in a Disconnected and Low Bandwidth Environment

Álvaro Rendón - University of Cauca Columbia

Álvaro will give an example of the E-Lane project in action that is based on .LRN and used in rural Colombia. It addresses network environments with low bandwidth connectivity and low cost access infrastructures.

01:00 PM Lunch

02:00 Afternoon sessions

2:00 PM Track 1: Accessibility and Technical Track

Towards Full Accessibility in LMS

2:00 PM Track 2: Case Studies and Theory

Education Talks and Demos

2:00 to 2:30 pm

Keynote: Accessibility in Community and Open Source Software Developments: the Moodle perspective

Martyn Cooper - Head of Accessible Educational Media group at the Open University of UK

Among diverse research and internal consultancy roles, Martyn Cooper has overall responsibility for accessibility in the Open University's Virtual Learning Environment which is based on Moodle.  The Open University has nearly 10,000 disabled students and takes its legal and moral responsibility to give them equal access to its teaching and learning very seriously.  It has been making substantial investments within the Moodle community to address the current deficits in accessibility of the software.  This paper reflects on this process and the more general issues of accessibility in community based and open source software developments.

2:00 to 2:30 pm

The Educator’s Guide to the Flat World: Flatteners and Convergences That Change Everything in Education

Steve Wilmarth

This workshop will focus on Thomas Friedman’s book, The World is Flat, and the theses that are driving globalization and multi-cultural educational issues.  Participants will develop ideas on how to think creatively and innovatively about changes that impact the purpose and value of education in the 21st century.  Participants will be challenged to see how the themes and concepts articulated in The World is Flat can or should be applied in classroom practices.

 

 

2:35pm to 3:05pm

Innovation and Research Accessibility Issues on eLearning: a user modelling approach

Jesús G. Boticario - Head of aDeNu Research Group at UNED (Spain)

 

 

 


 

2:35pm to 3:05pm

E-campus implementation: experiences at Galileo University

Rocael Hernandez 

Integration is a key factor for creating an e-campus initiative comprised of various systems. While there are multiple technical options for e-campus dynamic web services, we have chosen to use OpenACS for most of our web services.OpenACS has been an extremely powerful development framework to create new modules and achieve simple integration. Services provided in the e-campus initiative include .LRN, a Learning Management System (LMS), public news and institutional small Content Management System (CMS), tuition payment, course assignments, professor profiles, work opportunities and single account creation.

3:10pm to 3:40pm

Accessibility Requirements in dotLRN

 Olga C. Santos - R&D Technical Manager of aDeNu Research Group at UNED (Spain)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Coffee Break 3:40-4:00 pm

3:10pm to 3:40pm

The DGSOM Personnel System, Weekly Message Digest, Room Reservation System, and Calendar Application

 Avni Khatri, UCLA - CTRL

Many universities, like the David Geffen School of Medicine at UCLA (DGSOM), are busy, heterogeneous organizations of people and resources alive with meetings, presentations, and cross collaborations. Perhaps because of our size, DGSOM is more like a federation of city-states than a well-structured hierarchically administered organization. Consequently, common problems are often encountered and addressed in isolation of one another, and this has led, in our case, to a morass of incompatible partial solutions to similar problems. A few of examples if this include Web-presentation of faculty member profiles, shared management of resources like conference rooms, and the dissemination of events and other timely information.

The Computing Technologies Research Lab (CTRL) at UCLA is a software development group within DGSOM that provides open source solutions to research and clinical data collection, management and reporting problems. Members of CTRL have used the AOLserver (p.k.a NaviServer) to build web-based applications at UCLA since 1994.

Using the OpenACS framework (and Oracle RDBMS), CTRL has developed several applications that address a set of problems that all universities face in one form or another: centrally managing faculty information and integrating the information with heterogeneous departmental web sites (using ACS subsites), and centrally managing shared resources, like conference rooms, in a fashion that protects departmental control over the resources.

The presentation will include requirements, design, and technical details of how we have tailored the OpenACS to address the faculty database, room reservations, and the weekly message digests.

Coffee Break 3:40-4:00 pm 

4:00pm to 4:30pm

Federated Search for Locating Learning Resources from Heterogeneous Learning Repositories

Stefan Sobernig

Stefan will talk about using OpenACS/DotLRN in a federated search environment for locating learning resources from heterogenous learning repositories (usage of OpenACS in the EU research projects iCAMP and Prolix, learning networks, SQI).

4:00pm to 4:30pm

ePortfolios: Using Personal Learning Landscapes, Student Performance Evaluation and Life-Long Learning Opportunities

Steve Wilmarth

This workshop will explore the use and application of ePortfolios as an alternative and/or supplemental assessment practice.  Participants will develop ideas on how to use ePortfolios as an essential component of a personal learning landscape.

4:30pm to 5:00pm

Implementation of IMS-LD in .LRN

Luis de la Fuente Valentin - Universidad Carlos III de Madrid

Applying pedagogical models to e-learning courses is the aim of the IMS Learning Design Specification, which can be used to describe educational processes by defining the flow of e-learning activities. Its design is wide enough to manage any methodology, and it provides a way to add services as a support tool for the learning activities. A .LRN player for IMSLD packages has been developed by the University Carlos III of Madrid, and is designed from scratch and fully integrated with the platform.

 

 

 

4:30pm to 5:00pm

Collaborative Curriculum: Using .LRN to Coordinate Data Collection and Analysis Between Classrooms Featuring Microscopic Image Collections

With an NSF SBIR grant (National Science Foundation Small Business Innovative Research), Prime Entertainment has partnered with the Concord Consortium (CC), and Solution Grove (SG), to develop cutting edge collaborative curriculum centered around projects using a digital microscope. Prime Entertainment makes the QX5 hardware, CC is developing the Java application for collecting data, and SG is implementing the .LRN back end and website where teachers and students can share data and work together. Get a preview of how these systems integrate with each other and the structure of the online community.

 

5:00PM to 6:00PM: Informal demos and discussions
 

8:00PM: New England Seafood Dinner at the Summer Shack

Jasper White's Summer Shack

Telephone 617-867-9955
50 Dalton Street in the Back Bay,
across from the Sheraton Hotel entrance and the Hynes Auditorium. Upstairs from Kings Bowling Alley.
Closest Subway T Station: Green Line - Hynes Auditorium.

Day 2 (Nov. 2) - General Web Applications Focus - OpenACS

Free-form and technology focused with opportunities to demo

8:15AM - 8:50AM Breakfast

9:00AM - Start

Location:  Harvard Conference Center Rooms 214/216/217/Lounge

 

The architecture of Phigita.net

Neophytos Demetriou

An XOTcl based architecture of an OpenACS-like system, scalability through database partitioning, providing google like services.

Zip Car

Roy Russell - Founding CTO
Roy advises the company on a broad range of subjects. He has been an integral part of the Zipcar team since inception. Since the early days of Zipcar, Roy has been instrumental in developing and deploying the unique technology that has given the company its leading position in user experience. 

xoTcl for OpenACS Developers (Introduction)

Neophytos Demetriou and Gustaf Neuman

This will be a short introduction of what will be presented in more detail on Day 3 (during the hacking/training sessions at the Museum of Science).

Solution Grove

Demo of AJAX usage - Hamilton Chua remotely with Caroline Meeks and Dave Bauer live.

Porting Sloan from Oracle to Postgres - Please let us know if there is anyone with a oracle installation interested in moving to Postgres, we will only do this if there is interest. Deds Castillo remotely with Caroline Meeks and Dave Bauer live.

Two Approaches to Virtualization and OpenACS/.LRN

Two Approaches to Virtualization and OpenACS/.LRN

The two main approaches to virtualization, "total OS encapsulation" as done by VMWare Server, and the "shared-kernel" approach as taken by Solaris 10 with its Zones technology, will be discussed. A live demonstration of installing a working OS under each approach will be given.

Patrick Giagnocavo

Patrick Giagnocavo is the CEO of Zill.Net. Zill.Net offers hosting and colocation with a focus on OpenACS and .LRN setup and ongoing system administration.

Remote queries with SOAP:
We have designed and created a simple way to run queries on a remote server, using SOAP to send queries and receive results that are similar to those that the db_* API returns. This method may be used by other applications such as the <multiple> tag and list-builder.

xoORB: An XOTcl based Object Request Broker for OpenACS (SOAP-based web-services, client, and server framework)

Stefan Sobernig

 

Conformance Testing of the .LRN platform

 

Gerardo Morales - Groupe des Ecoles des Télécommunications/ Institut National des Télécommunications (GET/INT) France

For big and complex applications such as .LRN, it is mandatory to execute in a scheduled way a set of test cases to assure its stability and the conformance to its original model, along with the continuous development of such application. This presentation highlights the importance of conformance testing and the types of tests needed for the .LRN platform. It also presents a new method to automatically generate test cases from a .LRN model described in UML.

Selenium Unit Tests in OpenACS

Tracy Adams (ACSPropel) 

1. Creating Selenium Unit Tests
2. Hosted Selenium Unit Test management

1:00 PM to 1:50 PM: Lunch 

 

Marketspace Advisory

Sam Stearns

Marketspace Advisory is a strategy consulting firm focused on improving its clients' customer-facing interface systems and associated channel migration challenges. Clients include large organizations in the media, financial services, and consumer products sectors. We use an OpenACS /.LRN - based extranet during our engagements to share knowledge with our clients (especially via social bookmarking) and help raise their digital literacy.

Load balancing using a cluster with .LRN

This talk describes a widely-distributed and integrated functionality to increase performance and service. The installation includes multiple servers specialized for both static and dynamic information. Also some specific synchronization scripts will be described that replicate high traffic pages that do not change often and are the same for most users. The following will also be discussed:
- cache sharing
- node sharing
- reload of procs
- Content Repository (CR) file system sharing

.LRN Windows installer

We present an easy way to run and test .LRN and OpenACS in your windows installation. This method is based on the original design by Rocael Hernandex, initial development by Vlassis and then ProjectOpen in Barcelona, and has been fully-refactored and now maintained by Byron Linares.

OpenACS OCT/.LRN Leadership Team/EU4ALL Meeting 

The European project "EU4ALL" just started (EU4ALL stands for "European Unified Approach for Accessible Lifelong Learning") and the Scientific Coordinators of the project (aDeNu Research Group at UNED represented by Emma, Olga, and Jesús) want to meet with OpenACS/.LRN leadership to align common objectives and define a framework to reach them Audio  OpenACS_Meeting_Nov_2006.ogg (OGG)  OpenACS_Meeting_Nov_2006.mp3 (MP3)

Demos

Caroline Meeks and Dave Bauer 

1. AJAX UI examples
2. Extending List Builder with filters and graphs
3. Moving SloanSpace from Oracle to Postgres
4. Dynamic Types (Dave and Lee together we hope)

UG-Surveys

A package that administers multiple surveys that are being sent to users. It administers the assessment package. At Galileo has been used widely to used to pass out surveys to students across the different programs. So far more than 65,000 surveys has been answered.
- Create survey templates
- Deploy templates
- Close surveys and results

 

Day 3 and 4 - Training and Hacking Days at the Boston Museum of Science

November_3rd_and_November_4th_Training_and_Hacking_Days

.LRN Accessibility

Created by Olga C. Santos, last modified by Gustaf Neumann 25 Oct 2017, at 08:34 AM

From quite a long time .LRN community has been moving towards producing both accessible interfaces and services for all. Accessibility analysis on previous releases have been done such as Tristan Kalnins-Cole's under Dorian Peter's (dotLRN Director of Visual Design) supervision. This lead to the unofficial conclusion that version 2.1.3 was level A compliant.

Selva theme was designed to make easier the customization of the look and feel of .LRN, improving navigation and usability. Moreover, unlike other .LRN templates, it is strongly based on CSS. Therefore, it can be easily seen that Selva theme was a step forward in considering accessibility issues.

During the development of version 2.2.0 we have been working to assure that .LRN 2.2.0 with Selva theme is compliant at least with W3C WAI WCAG 1.0 level A. In this sense, three new categories of bugs have been created in the Bug Tracker and are being used to report problems regarding accessibility. So far, within the framework of several R&D projects in which aDeNu Research Group at UNED is involved, we have compiled several accessibility analysis performed by some of our partners (Soluziona) and research groups within UNED to translate the problems found at different development stages to .LRN/OpenACS bugs and discuss them in the .LRN IRC Tuesday meetings. "This work has led to the release of .LRN 2.2.0 as W3C WAI WCAG 1.0 level A compliant, except for LORS package (there is a strong incompatibility between the SCORM RTE and WCAG 1.0, which is to be solved with WCAG 2.0). Moreover, there may be some minor level A bugs reported found here, which are to be solved."

The planning for next version is to achieve WC3 WAI WCAG level AA and take into account, when available, specific guidelines from national regulations such as the American Section 508, UK SENDA, Australian DDA, German BITV or Italian Stanca. Our plans are to consider WCAG 2.0 as soon as they are officially released as well as other WAI documents (e.g. ATAG and UAAG).

In order to improve the accessibility quality of dotLRN, we ask you to use W3C Web Content Accessibility bug types to report any problems encountered so they are taking into account when developing.

Update for dotLRN 2.3

See Zen project and external evaluations on Educational packages [1], [2].

Information on the progress is also done in periodic dotLRN/OpenACS conferences:

  • Fall 2006
  • Spring 2007
    • Improving Accessibility, Usability, and Code Quality of .LRN and OpenACS: The .LRN Zen Project [3]
    • Workshop on Experiences on Accessible eLearning Platforms

 

Last modified: 2017-10-25 08:34:57.234495+02

How to contribute code that passes accessibility tests

Created by Rocael Hernández Rizzardini, last modified by Benjamin Brink 30 Jun 2017, at 06:10 AM

About this document

  • Status: DRAFT
  • Updated: 11-jun-2009

Accessibility Policy

The policy for .LRN is published at .LRN website: Accessibility Policy

Corresponding policy for OpenACS is currently being written and will be published soon.

The conformance level to be satisfied is explained in the "Accessibility Conformance Level" section of the .LRN Accessibility Policy.

The "Accessibility page" refered by the .LRN Accessibility Policy states the conformance level and its domain of aplication for each version of the software.

Web Content Accessibility Guidelines

Note: Although automatic tools, such as TAW and "Cynthia says", may be useful to help the developer/author in addressing accessibility issues by providing informative reports, they can not certify the accessibility level of a page since many things need a manual review. Also, those tools won't be able to check a page protected by user and password (they would report on the login page, the one they can actually reach).

WCAG version 2.0

WCAG version 1.0

  • The guidelines: explain how to make Web content accessible to people with disabilities.
  • Checklist of checkpoints to satify for each level of conformance. Each checkpoint is followed by one or more links to techniques in the following documents:
    • "Core Techniques for Web Content Accessibility Guidelines 1.0" ([WCAG10-CORE-TECHNIQUES]), which discusses the accessibility themes and general techniques that apply across technologies.
    • "HTML Techniques for Web Content Accessibility Guidelines 1.0" ([WCAG10-HTML-TECHNIQUES]), which provides examples and strategies for authoring accessible Hypertext Markup Language (HTML) content.
    • "CSS Techniques for Web Content Accessibility Guidelines 1.0" ([WCAG10-CSS-TECHNIQUES]), which provides examples and strategies to help authors write Cascading Style Sheets (CSS) as part of accessible content design.
  • Techniques: gateway to the aforementioned specific ones.

Contributing Code

Once the requirements are met, to contribute your code follow these instructions (one of the two):

  1. How to contribute to OpenACS
  2. Contributing code for .LRN: submit your proposal to the .LRN leadership team by:
    • posting at the .LRN Q&A forum
    • joining the weekly meeting on IRC (tuesday at 18:00 CET/CEST)

Resources

on-site resources

External resources

If you need more information on how to address accessibility, post your questions at the forums

SCORM support

Created by Olga C. Santos, last modified by Gustaf Neumann 22 Jun 2017, at 09:22 AM

Overview

Current SCORM support is provided by the LORS package: .LRN to incorporate IMS Metadata (IMS-MD 1.2.1) and IMS Content Packaging (IMS-CP 1.1.4) specifications as well as ADL SCORM extensions (SCORM 1.2). See Educational_Standards.

Standards Support.

Contributors:

  • It was initially developed by Ernie Ghiglione
  • E-LANE project
  • Adam Ullman added the SCORM applet for the run time interface from Concurrent Technologies
  • SITT (Michelle y Giancarlo) added delivery-scorm to collect the scores in the database
  • Dave Bauer

Extensions:

LORS Central: version handling, live version management, single item add/edit, others. Uses Content Repository directly, instead of file-storage

Status:

  • Incompatibilities between the java server and client environments
  • LORSM: Emma and Don are doing bug-fixing
  • LORS central: Galileo is doing bug-fixing. It clones LORSM, so improvemnts in LORSM have to be integrated 

Community members interests:

  • Matthew Coupe: Requires SCORM support to run SCORM courses. LORS central will be a nice to have feature as will integration with assessments, forums and chat.
  • aDeNu Group (UNED) requires SCORM support to run accessible SCORM based courses for ALPE project
  • Innova Group (UNED) is migrating LORS to Oracle to provide SCORM support in aLF (UNED customization of dotLRN)
  • Galileo wants to deploy LORS Central
  • Don Baccus needs basic course sequencing for a current client project

TO DO:

See SCORM Roadmap presented at the Workshop on Educational Standards and Methodologies support in dotLRN at OpenACS and .LRN Spring Conference, Vienna 2007.

Short term:

  • Fix bugs both in LORSM and LORS Central
  • Assure that SCORM sessions are recorded
  • Dynamic integration of Forums and File storage (as Assessment is done)

Medium term:

  • Combine LORSM and LORS Central to include version handling, live version management, single item add/edit, content repository instead of file-storage, but keeping their different scopes: LORS central handles very well centralized management, although it could do in a per course basis as LORSM does, which is for course level management
  • Maintain both probably is not a good approach, LORS Central provides what LORSM does, but Central has features such as: 1) item online add/edit, 2) single place to deploy one course and its versioning among different class instances, 3) native content-repository support (not using file-storage). Note that 1) & 2) are needs for real world deployment of courses.
  • Improve implementation: recompile Java applet vs. rewrite in JavaScript
  • Integrate LORS inside platform space (instead of in full page display)
  • Integrate portlets (forums, assessment, file storage) instead of the whole page
  • Improve accessibility
  • Implement SCORM 2004 v3

Competitors:

  • SCORM 1.2: ATutor, ANGEL, Kewl, OLAT, Docebo, WebCT
  • SCORM 1.3: Blackboard, Claroline, Desire2Learn, TeleTop, Moodle

See eduTools for a comparative comparison.

An appropriate SCORM support is a MUST for dotLRN to be competitive.

 

Last modified: 2017-06-22 09:22:57.800008+02 

Simple Content Creator / Editor

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 20 Jun 2017, at 10:34 AM

Description

The Content Package aims to be a simple tool for content creation in the educational context. 

  • Provides a simple interface to create web pages (a no-brainer 1 click), and easily include and manipulate web assets such as flash, videos, images, etc.
  • Provides a web template, easy to manage, similar to a PPT template but with built in navigation (sequential navigation, tab based organization, sub tabs supported and per unit / module navigation).
  • Folder, subfolders, pages ordering.
  • Free of "standards" approaches, so professors with basic word knowledge can use it.
  • Auto scroll (focus navigation on the content area).
  • It provides portlets for .LRN

The Content Package is based in XOWiki, since it is a very well maintained tool, and have many of the desired features such as: easy content tool (plus the advantage that a wiki tools is becoming more and more common), directories, versioning, flexible built-in features to handle content more easily (including positioning and segmentation), basic template management, variables, multi-language support.

The Content Package is a configuration package with a set of scripts, xowiki is left unmodified for Content to work. 

Check Galileo University promotional video (in Spanish).

Application architecture design by Byron & Rocael, development by Byron for Galileo University

Try it at:

http://www.galileo.edu/dotlrn/classes/departamentoparapruebas/departamentoparapruebas.actualizacintributaria/lamegaprueba2/xowiki/


user & pass: usertest

Check the manuals (in Spanish).

To-Do 

  • Provide collaborative content creation tools while being able to set up roles easily.
  • Integrate to SCORM / LORS

How to install

 

Works on:

postgresql 8.2.4

xowiki 0.47 +

xotcl 0.47 +
 

Requirements: 

ltree module for PostgreSQL.

Installation Process:

 

  1. Install ltree module for postgres.
  2. Obtain packages:  content-portlet, dotlrn-content, xowiki,xotcl-core
  3. Move the files of content-portlet/misc/www/*  to xowiki/www/
  4. Move the files of content-portlet/misc/admin/*  to xowiki/www/admin
  5. Move the files of content-portlet/misc/portlets/*   to xowiki/www/portlets/
  6. Go to acs-admin/apm
  7. Choose "install-packages"
  8. Install xotcl-core,  xowiki , content-portlet, dotlrn-content
  9. If xowiki is already installed, reload xowiki
  10. Restart the server.
  11. Activate the applet in one course.


 

Technical Specs

 Install the content applet in dotlrn will:    

  1. Place the xowiki (INSTANCIA) that will be used with the following personalized characteristics.
  • Parameters:  
  • extra_css : /resources/content-portlet/template/Gestheme.css
  • security_policy: ::xowiki::policyb
  • template_file: ges-view

 

  • Kind of created pages.
  • ::xowiki::Page : Index for welcoming to the main application: content-portlet/www/prototypes/gestemplate/GesTemplateIndex.page
  • ::xowiki::Object : 
  • Default object whit the name folder_id in which the use of Xhina editor is configured.
  • es:o_index : Object which manages the presentation of the index page depending on the kind of user.
Source: content-portlet/www/prototypes/gestemplate/GesTemplateIndexe.page
  • ::xowiki::PageTemplate:
  • es:Template_de_ges Web template that manages the presentation and navegation of the future content pages that will be created.
Source: content-portlet/www/prototypes/gestemplate/GesTemplatebody.page
  • es:Template_de_header: Template which manages the edition of the content titles.
source: content-portlet/www/prototypes/gestemplate/GesTemplateheader.page
  • ::xowiki::PageInstance :
  • es:header_page : used to entry the heading of the future content pages.
Source    : content-portlet/www/prototypes/gestemplate/GesTemplateheaderpage.page
  1. Creation of the content index that will be used:  this content index is composed of the following categories:
  • Unit or chapter
  • Introduction
  • Content
  • Activities
  • Glossary
  • Appendix

Content-Portlet Description:
The template es:Template_de_ges  manages the final presentation of the created content pages.
The web template used, is based in three navigation levels.
 

  • Unit or module
  • Section
  • Subsection

This template is built with a series of scripts, which are responsible of the navigation of every section, is divided in:  header, module navigation, section navigation, subsections navigation, navigation between pages and content.
The navigation is controlled by their respectives scripts located in content-portlet/www/

And they are:

unit-navbar: Checks the navigation between units or modules.
Navbar and complete-navbar:  Checks the navigation between sections in the web template.
complete-titlebar, next, home: These are the elements that conform and check the horizontal navigation bar between content pages for one section or subsection.
Subnavbar and complete-subnavbar: These elements check the navigation between subsections.
Each one of these are part of the web template and provides us a graphic simple way to navigate between content pages.

content-portlet/www/prototypes/gestemplate :  Provides the content of the diferents pages of xowiki created automatically by adding the applet in a course.

content-portlet/www/resources : It contains the graphic part of the web template that is being used.  (images, estiles, etc.)

Updates

There is an improved version of this package called Learning Content.

Plataforma Elearning

Created by Geovanni Hernandez, last modified by Gustaf Neumann 18 Jun 2017, at 12:32 PM

  • Plataformas Elearning

Se denominador  Aprendizaje electrónico (Also Conocido Como e-learning ) a la Educación a Distancia virtualizada A Traves de canales Electrónicos (Las Nuevas Redes de Comunicación, en especial Internet ), utilizando párr Ello Herramientas o Aplicaciones de hipertexto ( Correo electrónico , paginas web , Foros de Discusión , Mensajería Instantánea , Plataformas de Formación, Entre Otras) Como Soporte de los Procesos de Enseñanza-Aprendizaje. En un Concepto Más relacionado con lo semipresencial, tambien es Llamado b-learning ( blended learning ). 1

El b-learning Es Una modalidad Que Combina la Educación a Distancia y la Educación presencial, Retomando las Ventajas de Ambas Modalidades Y complementando EL APRENDIZAJE de los aprendices.

Also Florerias definirse Como un Sistema BASADO en la Comunicación Masiva y bidireccional Que sustituye la interaction personal en el aula del profesor y alumno, Como medio preferente de Enseñanza, Por La Acción Sistemática y Conjunta de Recursos Didácticos DIVERSOS y El Apoyo De Una organization tutorial, Que PROMUEVE EL APRENDIZAJE AUTONOMO de los Estudiantes, ademas de Reforzar La de habilidad de la Comunicación Efectiva Con Los Participantes A Traves De Las Plataformas implementadas.

  del consiste en la Educación y Capacitación through Internet. Este tipo de Enseñanza en línea permite la         interaction del usuario con el material el Mediante la utilizacion de Diversas Herramientas informáticas.

Este nuevo Concepto educativo Es Una revolucionaria modalidad de Capacitación Que posibilitó Internet, Y Que hoy se posiciona de Como La forma predominante de Capacitación En El Futuro. Este Sistema ha transformado la Educación, Abriendo Puertas al Aprendizaje individuo y organizacional. Es por Ello Que hoy en día this ocupando ONU Lugar Cada Vez Más destacado y reconocido Dentro de las Organizaciones Empresariales y Educativas.

Sigue un "Geovanni Hernández"


English Translation

E-learning is denominator (Also known as e-learning) to Distance Education virtualized through electronic channels (The new communication networks, especially the Internet) using para This Tools or Applications hypertext (E-mail, web pages, Discussion forums, Instant Messaging, Platforms Training, among others) and support the teaching and learning processes. In a concept more related to what blended learning, also called b-learning (blended learning). 1

The b-learning is a modality that combines distance education and classroom education, taking up the advantages of both modalities and complementing LEARNING apprentices.

Also Florist defined as a system based on the Mass and two-way communication system that replaces personal interaction in the classroom of teacher and student, as preferred means of education, the systematic and Joint DIFFERENT Resource Action and support of a tutorial organization, that promotes learning AUTONOMO of Students, in addition to strengthening skill of effective communication with participants through platforms implemented.

  It consists of the Education and Training through Internet. This type of online education allows user interaction with the material By using various tools.

This new educational concept is a revolutionary form of training enabled Internet, and today is positioned as the predominant form of future training. This system has transformed Education, Abriendo Puertas to individual and organizational learning. That is why today esta un Lugar occupying increasingly prominent and recognized within business and educational organizations.

.LRN Educational standards support

Created by Olga C. Santos, last modified by Gustaf Neumann 06 Jun 2017, at 11:53 PM

.LRN supports several educational standards in the following packages:

  • LORS: expands .LRN to incorporate IMS Metadata (IMS-MD 1.2.1) and IMS Content Packaging (IMS-CP 1.1.4) specifications as well as ADL SCORM extensions (SCORM 1.2).
  • Assessment: import IMS-QTI 1.2.1 zip files to create an assessment or export an assessment into IMS-QTI 1.2.1.
  • IMS-LD: plays IMS-LD units of learning (UoLs), and is integrated with ADL SCORM, IMS QTI and the .LRN forums. Information about the last stable release can be read in this link. The release was announced here.
  • IMS Enterprise: handle any IMS Enterprise v.1.1 XML document and reflect all the respective data into .LRN.

Both Assessment and LORS are part of dotLRN 2.2.0 and IMS-LD and IMS-Enterprise can be downloaded via the APM package manager.

Last modified: 2017-06-06 23:53:48.516768+02

.LRN Leadership Team 2008

Created by Carl Robert Blesius, last modified by Gustaf Neumann 01 May 2017, at 09:55 AM

This is the appointed Leadership Team for the year 2008. The Leadership Team is self elected from .LRN consortium and community members as outlined in the .LRN Governance Document.

.LRN Governance

Created by Caroline Meeks, last modified by Gustaf Neumann 07 Nov 2016, at 07:52 PM

Definitions

 

.LRN Consortium  – A nonprofit corporation incorporated in Massachusetts

.LRN Organizational Member  – An organization that has paid its yearly membership fee of $250 (or more).

.LRN Voting Member  – The individual designated by a .LRN Organizational Member to vote on its behalf.

.LRN Board  – A member of the 7 person board of directors that is elected by the .LRN Voting Members.

.LRN Chairman  – The chairman is a member of the .LRN board elected to chair the board by the .LRN board.

.LRN Leadership Team  – A group of people decided on by the .LRN Board and Leadership Team. .LRN Leadership Team members do not have to be voting .LRN members. 

.LRN Decision  – A decision that has gone through the decision making process described below

 

*******DRAFT**********DRAFT**********DRAFT***********DRAFT********

Please note that the decision making process is being modified as of July 8, 2007  

The Decision Making Process

Goals

  • Make it easy for motivated people to make decisions and implement them with minimal overhead.
  • Give the elected .LRN Board oversight over .LRN decisions without requiring too much of the Board's time. 
  • Give the appointed (in the future - elected?) Leadership Team (authority || permission) to move forward on technical decisions if the Board can not give input.

 

Informal description of the process

 

If you have an idea you'd like to implement, discuss it with people who care, post in OpenACS and/or talk about it in a .LRN meeting as appropriate. After you have listened, post your suggestion to the .LRN Decision board. Then implement it.  Mostly we all want the same things and we need action.  The .LRN Board vote is available as an oversight and in those hopefully infrequent times when there is significant dissent.
 

Formal Process

  1. All members of the .LRN Board and Leadership Team subscribe to the .LRN Decision Forum.
  2. The Leadership Team is the governing body primarily responsible for technical decisions with respect to .LRN. The Leadership Team has been appointed carefully by the Board hence there is implied trust by the Board in the Leadership Team. (NOTE: I am not sure how this would change if the Leadership Team changes to be elected.) 
  3. There is no formal process for small technical decisions. The Leadership Team will keep discussions as open as possible via open meetings where anyone is free to attend. Ideally, most technical decisions will be made at the weekly Leadership Team Meetings (currently Tuesdays at 16GMT on #openacs at irc.freenode.net), but some informal discussions may take place via the Leadership Team mailing list (honchos at dotlrn.org) in order to be more efficient.
  4. Members of the .LRN Board and Leadership Team are jointly responsible for making large technical and non-technical decisions with respect to .LRN.
  5. There is a formal process for large technical and non-technical decisions. What constitutes a large technical decision is determined by the Board and the Leadership Team.  (NOTE1: Though most decisions for .LRN may be technical, I feel .LRN is much more than just a technical framework and will encounter non-technical issues/decisions; NOTE2: I consider a large technical decision to be something along the lines of: "Are we going to do the Zen Project?")
  6. For all large decisions and all non-technical decisions, a new thread is started in the .LRN Decision Forum.  The first posting will contain the issue up for decision and the possible solutions on which the Board and Leadership Team members can vote. Once the thread is posted, voters have  (48 hours || 72 hours || 7 days) to vote.  A simple majority (51%) based on the members attending the vote will decide the decision up for vote. The Board and the Leadership Team members receive 1 vote each. In case of a tie, the present Board Members + (1 || 2) member(s) of the Leadership Team (which members are to be decided by the Leadership Team) will have a revote. Again a simple majority, will decide the vote. (NOTE: I don't know wtf to do if there is a tie after the revote.) (DAVEB: What is the motivation to make the votes scheduled and held in IRC, as opposed to a longer voting period on the forums. I think it would be easier to get participation from more members of the board and leadership team with a voting period on the forums. Since these are "large" decisions a few days of voting should not cause a signifigant delay.)(AVNI: Dave - that makes sense. Changed 17 july 07. :-) )
  7. If a member of the Board or the Leadership Team disagrees strongly with a small or large technical or non-technical decision made, s/he may post his disagreement (the reason for the disagreement must be made clear in the forum posting) on the .LRN Decision Forum. If (2 || 3 || 4) other Board or Leadership Team members in distinct locations (distinct university, company, country, etc) agree with the dissenting member and post as such with their own reasons for dissenting in the same thread, the decision is overturned.  Other Leadership Team and Board Members along with community members may post on this thread also to inform the Team and the  Board about their views.

---- Have cut the six below out for now. Feel free to add back in: ----------------------------------------------

  1. Members of the .LRN Board and Leadership Team are jointly responsible for making decisions. All people are expected to discuss and reach an appropriate level of consensus on issues. 
  2. When an individual believes he has done an appropriate level of communication and consensus building on a decision he posts it to the .LRN Decision Forum 
  3. If no one objects or calls for a vote the decision is confirmed in 2 weeks.
  4. If people agree they need take no action; however if there is disagreement or concern, any member of the Board or Leadership Team may “Call for a Vote” on any decision posted to the decision forum within 2 weeks of the post.
  5. If a decision is called for a vote only the .LRN Board members vote. .LRN Leadership Team members are encouraged to post their views to help inform the board.
  6. A decision is upheld with 2 Yes and 0 No’s or a 2/3 majority of all members (usually 5 people).

---- End cut ----------------------------------------------------------------------------------------------------------------

*****END DRAFT********END DRAFT********END DRAFT*****

 

The .LRN Board

  • Board members typically serve 3 year terms. (See Start Up procedure for exceptions)
  • Board members must be .LRN Voting Members from a .LRN Organization
  • Elections are held once per year for all vacant posts.
  • Board terms are staggered so that each year at least 2 or 3 posts are up for election.
  • If a Board member resigns or is no longer a .LRN Voting member prior to the end of his 3-year term then that post is filled during the yearly vote.  All candiates are voted on together. The people with the highest number of votes are given the longest terms.

Start Up Procedure

For this year's elections all 7 positions will be available.  Because we are still in startup mode all terms will be for 1 year.  Next year all 7 seats will be up for election again, at that point we will transition to 3 year terms.  The 3 people who receive the top 3 votes will get 3 year terms, the next two, 2-year terms and the next two, one-year terms.This will set up up to have 1/3 of the positions available every year in the future.

The current board will immediately begin to designate the Leadership Team. We will not wait for the election.

The .LRN Decision forum will be put into place in the next 2 weeks after the server is moved.

The current Board will have oversight, but anything that has a “Call for Vote” will be delayed until the new board is in place. That is, noncontroversial decisions can be implemented immediately, but controversial decisions will be postponed until we have a duly elected Board to vote.

Discussion

 

This proposal was created by Carl Blesius, Rocael Hernandez, Carlos Kloos and Caroline Meeks over lunch at the Argentina E-Lane meeting. It was written up by Caroline Meeks.  Our goal was to create the simplest possible start up plan and leave complex or controversial decisions to an elected board.

This is not meant to be the final plan. Specifically we discussed but did not reach conclusions about how large organizations vs. small should be represented, individual vs. organizational power or how parties that contribute more money should be rewarded. We also discussed but did not decide on issues around official/certified vendors and vendors contributing back to .LRN. We will work on these issues with the newly elected board.

We ask that the community look over this proposal and see if you agree that it will work for startup purposes. We also ask that you think about what you would like to see as part of permanent governance and policy; however, the appropriate time to fully engage in decisions around long term issues is after we have an elected board.  At that point all parts of this initial governance plan can be modified via the decision policy laid out above.

I would especially ask those familiar with our nonprofit incorporation if there are any legal requirements we need to meet as part of governance.

.LRN Installation

Created by yesten dan, last modified by Gustaf Neumann 06 Nov 2016, at 09:55 AM

Before OpenACS 5.8.1, DotLRN installations required a different installer than its base system OpenACS. There was no way for an end-user to upgrade from an existing OpenACS installation to DotLRN without loosing data, or to make hybrid installations (maybe in the future to use e.g. as well components from Project Open, etc.).

Starting with OpenACS 5.8.1 (and DotLRN 2.8.0) one can upgrade from OpenACS to DotLRN via the standard OpenACS package manager. Therefore, one easy approach to install DotLRN 2.8.0 is to install first a minimal OpenACS system and upgrade in a second step:

  1. Install OpenACS 5.8.1. For details, check out openacs-system-install.

  2. On the running OpenACS system
    • browse to YOUR_SYSTEM/acs-admin/
    • Click on "Install Software" 
    • Click on "Install from Repository"
    • select "dotLRN" and click on the button "Install..."

This will install dotLRN with the required core components. More packages can be installed a some later times if desired.

Install instructions for .LRN 2.5.0.

Packaged installations

For platforms like Linux/Ubuntu, Linux/Debian, FreeBSD or Windows, one can use the packaged solutions installing separate databases for DotLRN and OpenACS:

 

 

Next Page
previous April 2024
Sun Mon Tue Wed Thu Fri Sat
31 1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 1 2 3 4

Popular tags

17 , 5.10 , 5.10.0 , 5.9.0 , 5.9.1 , ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bootstrap , bugtracker , CentOS , COMET , compatibility , CSP , CSRF , cvs , debian , docker , docker-compose , emacs , engineering-standards , exec , fedora , FreeBSD , guidelines , host-node-map , hstore
No registered users in community xowiki
in last 30 minutes
Contributors

OpenACS.org