Home
The Toolkit for Online Communities
17332 Community Members, 1 member online, 2245 visitors today
Log In Register
OpenACS Home : xowiki : Weblog
Search · Index
Previous Month September 2014
Sun Mon Tue Wed Thu Fri Sat
31 (2) 1 2 3 (2) 4 5 6
7 8 9 10 11 12 13
14 15 (1) 16 17 18 19 20
21 22 (1) 23 24 25 26 27
28 29 30 1 2 3 4

Popular tags

ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bugtracker , COMET , cvs , debian , emacs , fedora , FreeBSD , hstore , includelets , install , installation , installers , javascript , libthread , linux , monitoring , naviserver , nginx , nx , OmniOS , oracle , osx , patches , performance

No registered users in community xowiki
in last 30 minutes

Contributors

OpenACS.org

Weblog

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

.LRN

Created by Emmanuelle Raffenne, last modified by Gustaf Neumann 05 Oct 2013, at 01:10 PM

.LRN Project

.LRN Home Page - The Official .LRN Home Page

.LRN bug tracker - Use the Open ACS bug tracker to report and check status on bugs for all sections of .LRN. If you need to report a bug and you are not sure what code is causing it, use the "2-dotLRN General" category. Otherwise select the package. Note that all the dotLRN packages are at the bottom of the list.

Get Involved! - how to participate in the community

.LRN Versions

Last stable release: 2.5.0

Next release: see .LRN 2.5 Release Management 

Download from .LRN download page

.LRN Installation

To install .LRN follow the instructions at .LRN_Installation

.LRN Governance

This .LRN Governance page is a proposal based on a meeting by Carl Blesius, Carlos Kloos, Roceal Hernandez and Caroline Meeks.  

Useful Resources

Site Specific Documentation

Official test servers

Page Information

  • Last modified: 2013-10-05 13:10:30.274062+02

Learning Content Tool

Created by Alvaro Rodriguez, last modified by josue ruiz 21 Dec 2012, at 12:22 AM

Learning-Content Tool

Description


User specs
The Learning-Content Package is a simple content creation tool based on xowiki. This package lets you easily create, edit and organize content for a course, taking advantage of xowiki's easy inline edition and revision history.  The package provides a generic template generated automatically with the pages and the categories.
During the edition of the pages there is an interface that allows the addition of terms and definitions to a glossary, linking the words from the content. It comes with an interface that allows linking of certain resources from the course, such as linking evaluations, assessments and forums to the content pages.
There is a new admin section for the content which includes a page to manage the categories in the content tree, an option to show/hide a specific title for the course on every page, user tracking by page or user, and one-click automatic copy of the content to other classes/communities.

Development History


2007

The Content package was first developed by Byron Linares (Galileo University) as a portlet using xowiki as the main package, adding all the files and modifications needed in xowiki. The automatic template included was specific for the Galileo's theme.

Works on:
postgresql 8.2.x
xowiki 0.47
xotcl 0.47

Required:
ltree module for postgresql

2008-2009
The package was improved by Alvaro Rodriguez and Viaro Networks team to make it a real package as an extension of xowiki, it was updated to work with the latest version of xotcl-core, xowiki from the oacs-5-4 branch. It was completely ported to Oracle and it no longer requires the ltree module for postgresql.

How to Install


Works on:
Postgresql 8.2.x +
Oracle 9i +

Requires:
xowiki 0.106.1
xotcl-core 0.100
views 0.1d3
ajaxhelper 0.87d (needs upgrade to YUI 2.5.2+)

Installation process:
  1. Get the following packages from branch oacs-5-4: dotlrn-all, xowiki, xotcl-core, views
  2. Get the following packages from HEAD: learning-content, learning-content-portlet, dotlrn-learning-content, ajaxhelper
  3. Move to the content package folder and run the script.sh, this will patch all the files from other packages to integrate them with content new features
    1. To run the script:
      • /$path_to_content_patch/$  sh script.sh
  4. Install dotlrn, then install xowiki, xotcl-core, learn-content, learn-content-portlet, dotlrn-learn-content, ajaxhelper and views
  5. Restart the server
  6. Activate the applet in a course

Release Notes


Name: Content
Version: 0.1d  (October 2007)
Developed by: Byron Linares (Galileo University)
  • Provides a simple interface to create web pages 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

Name: Learn Content (Renamed because Content was a very generic name)
Version: 1.0b (January 2009)
Developed by: Alvaro Rodriguez (Viaro Networks)
  • The package is an OO extension of xowiki, leaves xowiki package unmodified
  • Glossary tool, a plugin for xinha to add words to the glossary during the content edition, an admin page to manage all words and definitions, dynamic popup with the word definition inside the content
  • Integration with other dotlrn resources, a new interface to link resources from the course to the content pages, this allows the content tool to be the reference of a course like SCORM
  • User tracking, reports about all the content pages and all the users views, visits by page and visits by user
  • Header for the content, show/hide a specific title for the course on top of each page of the content
  • An admin section of the content for teachers, the xowiki's inherited admin section is only for swa
  • Automatic copy of the content to other classes/communities inside dotlrn
  • Split up the automatic template in sections to be easily changed (by developers/designers)

Technical specs


The Learn-Content Package is an OO extension of xowiki. The package generic template was split into sections so that it can be easily modified (by a developer/designer).  A new plug-in for the Xinha richtext editor allows it to interact with the new glossary feature. To use this plug-in a parameter in the Xinha configuration must be set (which is automatically added in content).

Every page instantiated along with the package (index, glossary admin, templates, etc) is now in the prototypes section of content. If a site-wide administrator deletes a page it will be loaded again when requested. There is a new admin section that is independent of xowiki's admin section, this section is in a different directory so that different permissions can be set.

Calls to content callbacks have been added to other packages in the add forms to be able to link the resources from those packages to the content pages. The callbacks extend the form of a new object to receive the page_id to be linked to, and inserts the objects into the page once it has been created in the submit section of the form.

A new proc was created that automatically copies content to other classes/comunities using the export and import options of xowiki, complete with all the categories, the mapped objects, and the activities linked to the content.

Each callback is defined and implemented in the learn-content-callback-procs, in the following way:
ad_proc -public -callback "callback_name" -impl content
if a package needs a different implementation of a callback it should be done in the package callbacks procs in the following way:
ad_proc -public -callback "callback_name" -impl $package_key
This callbacks are used inside the page that has the form for creating/editing new in the following way:
callback -catch -impl content "callback_name" -params...

To add a new package to the activities available in content, the callbacks should be added to the file(s) where the objects are created, i.e. forum-new, task-add-edit, etc.
  1. A new parameter called page_instance_id needs to be added to the ad_page_contract
  2. The following callback should be added in a place where the form can be extended
    • callback -catch -impl content learning_content::extend_form -name $form_name -page_instance_id $page_instance_id
  3. The following callback should be added in the submit section of the form after the object has been created
    • callback -catch -impl content learning_content::insert_object -name $object_name -item_id $page_instance_id -activity_id $object_id
  4. The activity should be added to the activity-new and get-activities pages in the learning-content package, check out the existing activities sections to figure out the right way to include

The script added to the package to patch the rest of the packages was generated with diff between the packages from clean oacs-5-4 and modified oacs-5-4:
diff -crNB ~/oacs-5-4/packages/$package_name ~/custom-oacs-5-4/packages/$package_name


This work was done in collaboration with Innova - UNED.

.LRN Meetings

Created by Alvaro Rodriguez, last modified by Alvaro Rodriguez 10 Mar 2010, at 04:41 AM

Next Meeting: 2010-03-10 18:00 CET/CEST Convert to your local time 

Agenda

  • .LRN 2.6 Release

Previous Meetings


2008

Educational Wiki (Eduwiki) Tool

Created by Hector Amado, last modified by Hector Amado 07 Oct 2009, at 11:34 PM

Educational Wiki  (Eduwiki)

Description


The Educational Wiki (Eduwiki) Package is a Wiki tool based on xowiki, Eduwiki aims to be a simple tool for Wiki pages creation in the educational context.
This package lets the teacher to easily define Eduwiki Activities,  there are three Eduwiki Types activities:  Teacher Wiki,  Group Wiki and Student Wiki.
Teacher Wiki activity is a single Wiki Activity managed by the Teacher,  Teacher may set permissions to the students to read and write Wiki pages.
Group Wiki activity creates a Wiki per Group, Teacher may set permissions to read and write Wiki pages by other groups members.
Student Wiki type creates individual Wiki pages per student,  each student can edit an create Wiki pages, teacher may set permissions to the rest of students to view and edit student Wiki pages.


How to Install


Eduwiki package works on: Postgresql 8.2.x+

Requires:
dotlrn 2.4.1
xowiki 0.116
xotcl-core 0.106
ajaxhelper 0.87d


Installation process:


1. Get the following packages from HEAD:  eduwiki,  eduwiki-portlet,  dotlrn-eduwiki
2. Save packages to packages dir in your .LRN installation
3. Browse to Package Manager to install new packages (eduwiki,  eduwiki-portlet,  dotlrn-eduwiki)
4. Restart the server
5. Activate the applet in a course


Release Notes


Name: Educational Wiki (eduwiki)
Version:  0.1d3 (July 2009)
Developed by:  Hector Amado (Galileo University)
Designed by: Rocael Hernández, Byron Linares (Galileo University)
Requirements by: Daniel Contreras, Rocael Hernández (Galileo University)

Provides a simple interface to create Wiki Activities,  Teacher may set permissions to read, write and create Wiki Pages.
Provides a simple interface to create Wiki Pages (a no-brainer 1 click), and easily include and manipulate web assets such as flash, videos, images, etc.

The package is an OO extension of xowiki,  leaves xowiki package unmodified, 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, basic template management, variables, multi-language support.
It provides portlets for .LRN


Technical specs


The Educational Wiki (eduwiki) Package is an OO extension of xowiki.  It's based on Policy ::xowiki::policy3, to set permissions per pages.

A new proc was created to manage Eduwiki Activities, eduwiki::set_eduwiki_permissions,  this proc set permissions to new pages based
on the activity definition.


To-Do


Start and end date editing functionality
Integration with evaluation package

.LRN 2.5 Release Management

Created by Rocael Hernández Rizzardini, last modified by Emmanuelle Raffenne 16 Sep 2009, at 06:44 PM

About

  • Next stable release: 2.5.0
  • Las stable release: 2.4.1
  • Tentavive deadlines:
    • may 31, 2009: code freeze and branch
    • june 1, 2009: alpha release process starts
    • june 15, 2009: beta release
    • july 15, 2009: final release

.LRN 2.5 will contain the packages included in the following cvs modules:

  • acs-core
  • dotlrn-all
  • dotlrn-extras
See Aliases at CVS for a detailed list of the packages included in those modules.

Releases are coordinated by the .LRN Leadership Team.

Weekly technical meetings in IRC at openacs channel:

  • Summer: Wednesdays, following the OCT one at 16:00 GMT
  • Winter: Wednesdays, following the OCT one at 17:00 GMT.

To-do List

  • Databases support:
    • Postgresql 8.2 and 8.3
    • Oracle 10 and 11
  • Replace "html_p" by "mime/type" and richtext widget for input (news, bulk-mail, others?)
  • calendar: localize notifications
  • forums:
    • DONE: localize notifications
    • removed the SC implementation of search to avoid confusion (search now implemented with callbacks)
  • assessment:
    • review daveb changes
    • added "views" support (explicit dependency)

Wish List

NOTE: xowiki was NOT part of .LRN 2.4 or earlier. Since noone from the accessibility group has checked, whether xowiki is compliant with WCAG 1.0 double-A, the DotLRN consortium board meeting decided in Valencia to include xowiki and maybe some other packages in a dotlrn-extras distribution in 2.5. This extra-distribution should not have the strong accessibility requirement as dotlrn-all, where every package must be manually checked in detail by some "accessibility expert".

Note by Don Baccus:  Honchos, not an ad hoc group of .LRN consortium members, decides what goes into .LRN.  Honchos proposed, and the board agreed, that a MINIMUM requirement for inclusion is accessibility compliance.  If xowiki hasn't been checked, by default it DOES NOT go in, not vice-versa.

New features

  • Removal of .LRN applets:  see the Removal of Applet thread
  • Wiki (xowiki with special policy set designed for .LRN, i.e. avoid professors writing their own tcl scripts or access the DB (DONE), probably a simplified UI?) Galileo will work on this and a few additions to have a wiki for .LRN, in late may / early june 2008.
  • Content package: tools for creating content online for .LRN
  • xo-S5: online presentation tool (and get rid of wimpy-point)
  • Replacement of static portlets by xowiki portlet pages (need to figure out if we use the same xowiki instance for "portlet pages" and for the wiki)
  • Blogger replacement with xowiki blogger? (have to review funtionality list, upgrade from actual blogger, others)
Having the idea of a macro-tool (xowiki) that can be easily customized for specific use with prototypes and others will help us to the reduce the code to maintain.

To do

  • xowiki (What's missing?)
  • content: produce an standard release that work atop .LRN (oracle & PG).
  • s5
  • xo static portlet (supported via xowiki-portlet and dotrln-xowiki; what else?)
  • blogger

Packages that could be xoified?

There are packages that could be replaced with xowiki/xotcl.
xowiki might need a finer granularity (object level) for permissions (parties), categories, comments.

  • news (if we manage to tell xowiki to use dates to display and archive a news item
  • edit-this-page
  • bulkmail (like news but with email being sent out and ui for selecting role/users)

I would even to that far to say that we can replace forums (using page_order) and calendar (similar to news/bulkmail but special UI).

Time/Topics Planner for dotLRN Courses

Created by Alvaro Rodriguez, last modified by Alvaro Rodriguez 01 Sep 2009, at 04:12 PM

Introduction

.LRN Blocks View is an additional View to .LRN Communities or Classes.

The Blocks View works by integrating all kinds of activities or resources of a community to a simple interface where everything is treated by the object id no matter what the object type is, and creating a new behavior to the activities according to the object type.

The new interface becomes the Community Home and is organized by blocks, there are currently 2 formats for the blocks:
  • Weekly Format
    • Each block represents a week, the weeks start to count the day the community starts, this value is set in the Course Settings of the Blocks View.
    • The current weeks is highlighted.
  • Topics Format
    • Each block represents a topic, all the activities and resources in this block are related to the topic, in this format the start date of the community is not relevant.
    • This format lets the teacher selects the current topic and highlights that topic automatically until it is deselected or another topic is selected, only one topic can be selected at a time.

This option is available for all communities inside the dotlrn-admin-portlet, there's a link to enable/disable this view, when the view is enabled a default empty block is created inside the community (this initial block it is always shown on top with no format) and it automatically mounts the packages needed (evaluation, assessment, forums, content, xowiki, chat) on the community.

Course Settings


In the Course Settings of the Blocks View we can set:
  • the number of blocks, if the number of blocks selected is greater than the current blocks, the extra blocks needed are created, if the number of blocks selected is lower than the current blocks the rest of the blocks are simply not displayed but never deleted.
  • the start date, this is used to set the start day for the weekly format.
  • the format, weekly or topics.

Blocks Basics


To add objects to a block there is a section inside each block where we can select the type of activity/resource we want to add and it lead us to the specific interface of that object type to create a new object or we can go to choose an existing activity from an interface showing all the available activities.

Each block has the following options:
  • Add a summary, this is a small text that we can add to be shown on top of the block to describe the block's content.
  • Show/Hide, we can choose which blocks we want to make available for students.
  • Move, the blocks can be ordered by using a drag n drop option to move them or doing a manual move by moving the block one position at a time.

Blocks Objects Basics


Each object inside a block has the following options:
  • Show/Hide, we can choose which object we want to make available for students.
  • Move, the objects can be ordered inside the same block or moved to a different block by using the drag n drop option.
  • Indent, the objects can be indent right or left, this is just for visual purposes and it has no side effect on the behavior of the objects.
  • Edit, this link lead us to the specific edit interface depending on the object type.
  • Delete, this link deletes the reference of the object with the block and if the object is not referenced by another block it deletes the object as well.

Technical Specs


The relations between all the packages integrated with blocks are handled by using callbacks, this callbacks are declared in the blocks context and the implemented in each package context.

The callbacks used are:
Specific callbacks: These callbacks need to be implemented for each package  because it must return the url for different actions on an specific object type.
  1. search::url
  2. planner::edit_url
  3. planner::delete_url
Standard callbacks: These callbacks are implemented once because there's no difference in the code needed for all packages.*
  1. planner::extend_form
  2. planner::insert_object

* The only package with a different implementation for the standard callbacks is the file-storage, the objects of the file-storage cannot be treated only with the object_id because there are different types of objects (url, file or folder) and to be able to choose a file we might need to navigate inside some folders, so in this case the value for the block id is passed in the cookies and the cookies are validated by the parameter return_url.

A New Package


A new package was created based on xowiki called "pages" to accomplish the integration of xowiki with the blocks view, xowiki is not a usual package so it was not possible to add the callbacks in the same way as the rest of the packages, a lot of procs needed to be changed and to avoid adding too much code to xowiki we created an independent package.  This package requires xowiki as it uses all the xowiki classes and procs.

This package works just like xowiki but using a different policy to let the users only work with ::xowiki::Page and ::xowiki::PlainPage, adding new pages can be handled only from the blocks interface because it needs a block to associate the page with. The package has a callback "after-mount" to set the permissions to not inherit from parent and only swa can admin that package.

Navigation Bar


The blocks view provides a navigation bar in the master section (only inside of the community), this bar show all the objects inside the blocks on that community and you can go to any object on any block. If you're inside an object page, the navigation focuses on that object (this is done by sending a parameter to the master with the object_id) and enables the navigation to the next and previous object (if possible).

Scalability


This .LRN Planner went through scalability tests because it has it's own data model which links objects from all the other resources tables, if this is used as every single course home organizer it could become slow know that needs to get specific information from different tables for every object. 

The solution for this matter was to group all the activities of a course for a specific type, get the information by groups and leave it in aolserver's cache, this involves a lot of extra code to keep the cache up-to-date, this is completely handled to make the planner a powerful solution for every course in .LRN.

Project Documentation

This paper was presented in the 7th OpenACS/.LRN Conference, you can check out the conference paper.

How to Install

Works on:
Postgresql 8.2.x +
Oracle 9i +

Requires:
dotlrn 2.4.1
xowiki 0.106.1
xotcl-core 0.100
ajaxhelper 0.87d

Installation process:

  1. Get the following packages from branch oacs-5-4: dotlrn-all, xowiki, xotcl-core
  2. Get the following packages from HEAD: planner, pages, ajaxhelper
  3. Move to the planner-patch folder in the planner package folder and run the script.sh, this will patch all the files from other packages to integrate them with the planner new features
    1. To run the script:
      • /$path_to_planner_patch/$  sh script.sh
  4. Install dotlrn, then install xowiki, xotcl-core, planner, pages and ajaxhelper
  5. Restart the server
  6. Activate the Planner View in a course admin portlet

Release Notes

Name: .LRN Planner
Version: 1.0b (July 2009)
Developed by: Alvaro Rodriguez (Viaro Networks)

  • Full integration with dotlrn resources: evaluation, assessment, forums, file-storage, HTML and Text Pages (using the Pages package)
  • Use of aolserver cache to assure scalability
  • Weeks and topics formats available
  • Provides a completely independent course home
This is how the Planner View looks.

Technical Specs

The planner works by linking activities by calling the callbacks that have been added to other packages in the add forms to be able to link the resources from those packages to the planner blocks. The callbacks extend the form of a new object to receive the page_id to be linked to and inserts the objects to the page once it has been created in the submit section of the form.

Each callback is defined and implemented in the planner-procs, in the following way:
ad_proc -public -callback "callback_name" -impl planner
if a package needs a different implementation of a callback it should be done in the package callbacks procs in the following way:
ad_proc -public -callback "callback_name" -impl $package_key
This callbacks are used inside the page that has the form for creating/editing new in the following way:
callback -catch -impl planner "callback_name" -params...

To add a new package to the activities available in the planner, the callbacks should be added to the file(s) where the objects are created, i.e. forum-new, task-add-edit, etc.
  1. A new parameter called block_id needs to be added to the ad_page_contract
  2. The following callback should be added in a place where the form can be extended
    • callback -catch -impl planner planner::extend_form -name $form_name -block_id $block_id
  3. The following callback should be added in the submit section of the form after the object has been created
    • callback -catch -impl planner planner::insert_object -name $object_name -block_id $block_id -object_id $object_id
  4. The activity should be added to the index, select-activity and get-activities pages in the planner package, check out the existing activities sections to figure out the right way to include 
  5. Depending on the activity, other lines of code need to be added to keep the consistency with the use of aolserver's cache, to keep it up-to-date with objects add/edit/delete actions.

The script added to the package to patch the rest of the packages was generated with diff between the packages from clean oacs-5-4 and modified oacs-5-4:
diff -crNB ~/oacs-5-4/packages/$package_name ~/custom-oacs-5-4/packages/$package_name

This work was done in collaboration with Innova - UNED.

How to contribute code that meets accessibility requirement

Created by Rocael Hernández Rizzardini, last modified by Emmanuelle Raffenne 11 Jun 2009, at 07:24 PM

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

.LRN Installation

Created by Carl Robert Blesius, last modified by Alvaro Rodriguez 11 Jun 2009, at 04:12 PM

Index

Introduction 

Installing .LRN: Using the VMWare Virtual Machine 

Installing .LRN: Using the Tarball

Installing .LRN: Using CVS

Installing .LRN: Using Debian/Ubuntu Packages

Introduction

VMWare virtual machine: simple (for a testing and evalution). Tarball: medium to hard (for a production install without source control). CVS: hard but flexible (e.g. makes it easier to update your installation from the code repository between official releases). Debian/Ubuntu: simple to medium (fast and easy install for novices, easy infrastructure deployment for professional users).

Installing .LRN: Using the VMWare Virtual Machine

to be announced. 

Installing .LRN: Using the Tarball

Before you start

Quickly read the OpenACS Installation Overview and if you still feel like you can progress start with the first part of the next section: Install a Unix-like system and supporting software

(skip the obvious portions if you are already running some unix like OS). Download the latest .LRN distribution from the .LRN repository (currently 2.4.1).

Move the tarball into your /tmp directory (replace dotlrn-2.4.1.tgz with the name of the tarball you downloaded, if you downloaded another version):

mv dotlrn-2.4.1.tgz /tmp/

untar it in that directory

cd /tmp
tar zxf dotlrn-2.4.1.tgz

Installation Process

Continue with the other sections of the installation document, but instead of downloading the OpenACS tarball mentioned in the docs (section "Unpack the OpenACS tarball" in the Install Linux and supporting software document), use the .LRN tarball you just downloaded above. This .LRN distribution includes all OpenACS packages needed to install and run .LRN. Throughout the documentation, use your unpacked .LRN tarball under /tmp/dotlrn-2.4.1 (or name of the directory you unpacked it to) instead of instead of the OpenACS tarball referred to in the documentation.

.LRN is automatically installed and configured as part of the installation process if you install using a standard .LRN distribution.

When installation is complete, restart AOLserver as described in the OpenACS installation instructions.  You'll need to wait a few minutes while dotLRN configures itself.  Reload your browser page.  If installation was successful, you'll see a login page. Use the user name and password you entered for the system administrator.  A page will come up that includes a link to sitewide administration.  Visit the link, then click on the "users" link and then approve the system administrator's .LRN membership.

Explore .LRN

Go to .LRN Administration at http://yourserver/dotlrn/admin.  Create a .LRN Community and a couple of users.

Here are some suggestions for things to check out in dotlrn:

Goto /dotlrn your "workspace". Click the "My Account" link at the top and try the "Customize this portal" link there.  Goto the admin pages for a class or community and try the "Manage Membership" link. Create a new sugroup for a class or community. Edit or create new "Custom Portlets".

Installing .LRN: Using CVS

Setting up the Required Infrastructure

The OpenACS documentation page has extensive installation instructions describing how to install needed database and webserver. Follow the instructions up until the point where you are told to download OpenACS and then continue with this document instead.

Notes on using CVS

CVS commandlines are given in terms of anonymous users, if you have an account on openacs.org, use your login where appropriate. Don't forget to set the CVS_RSH variable in your shell envrioment to "ssh".

Checking out the code

Go to /var/lib/aolserver (create the directory if it is not already present). Checkout the code (this is a complete code checkout and might take a while):
cd /var/lib/aolserver
cvs -d anonymous@cvs.openacs.org:/cvsroot login
cvs -d anonymous@cvs.openacs.org:/cvsroot -r oacs-5-4 co openacs-4
mv openacs-4/packages/dotlrn/install.xml openacs-4

Proceed

You can then proceed with the normal OpenACS installation instructions.

Explore dotLRN

Go to dotLRN Administration at http://yourserver/dotlrn/admin. Make some dotLRN users, terms, departments, classes.

Here are some suggestions for things to check out in dotlrn:

Goto /dotlrn your "workspace". Click the "Control Panel" link at the top and try the "Customize this portal" link there. Goto the admin pages for a class or community and try the "Manage Membership" link. Create a new sugroup for a class or community. Edit or create new "Custom Portlets".

Enjoy!

Automated Installation

As an alternative to the manual CVS checkout and installation described here there are scripts that will automate the install for you. See the OpenACS installation documentation for more details.

Installing .LRN: Using Debian/Ubuntu Packages

Debian

Ubuntu

Simple Content Creator / Editor

Created by Rocael Hernández Rizzardini, last modified by Alvaro Rodriguez 06 Mar 2009, at 12:06 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) and public announcement. 

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.

Release Notes .LRN 2.3.1

Created by Alvaro Rodriguez, last modified by Alvaro Rodriguez 11 Nov 2008, at 02:40 AM

Release Notes .LRN 2.3.1

Note: This release notes were created based on the change log from tag dotlrn-2-3-0-final to dotlrn-2-3-1-final on the branch oacs-5-3. (view full change log

ASSESSMENT

Add form for naming an answer set

Fix upgrade to work with correct constraint names

CALENDAR

Add attachment icon if an event has attachments

Upgrade that fixes permissions and removes requests for personal calendars

FAQ

Added triggers to index faq contents for search

NEW-PORTAL

Fix bug where database does not magically return portal pages in sorted order, causing user confusion when the pages end up out of order. No upgrade for existing pages since I don't want to stomp all over portals that may have been customized.

changes to portal layout page design

THEME-ZEN

First shot at integration of Zen. Everything except DIV-based column layout is in other than some details ...

And more necessary things ... would've been nice to have received the tar file in the first place, as was asked for!

Zen round 2.  Added 1, 2 and 3 column div-based layout and a horrible, horrible hack in the new-portal package to make them work.

Use site blank-master. Initialize header stuff

1. Fixed some catalog stuff.  Made a simple update script, not ready for Prime Time.

Zen: file for onkeypress goto function; needs to be reviewed by donb

Changed update code to set portlet themes to zen

1. Localized styleswitcher links
 

This work has been done for the .LRN Consortium

Next Page