Filtered by category .LRN, 1 - 10 of 23 Postings (all
Created by Caroline Meeks, last modified by Gustaf Neumann 07 Nov 2016, at 07:52 PM
.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
Please note that the decision making process is being modified as of July 8, 2007
The Decision Making Process
- 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.
- All members of the .LRN Board and Leadership Team subscribe to the .LRN Decision Forum.
- 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.)
- 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.
- Members of the .LRN Board and Leadership Team are jointly responsible for making large technical and non-technical decisions with respect to .LRN.
- 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?")
- 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. :-) )
- 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: ----------------------------------------------
- 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.
- 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
- If no one objects or calls for a vote the decision is confirmed in 2 weeks.
- 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.
- 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.
- 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.
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.
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:
- Install OpenACS 5.8.1. For details, check out openacs-system-install.
- 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.
For platforms like Linux/Ubuntu, Linux/Debian, FreeBSD or Windows, one can use the packaged solutions installing separate databases for DotLRN and OpenACS:
Created by Carl Robert Blesius, last modified by Gustaf Neumann 06 Nov 2016, at 09:54 AM
Installing .LRN: Using the VMWare Virtual Machine
Installing .LRN: Using the Tarball
Installing .LRN: Using CVS
Installing .LRN: Using Debian/Ubuntu Packages
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
tar zxf dotlrn-2.4.1.tgz
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.
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):
cvs -d email@example.com:/cvsroot login
cvs -d firstname.lastname@example.org:/cvsroot -r oacs-5-4 co openacs-4
mv openacs-4/packages/dotlrn/install.xml openacs-4
You can then proceed with the normal OpenACS installation instructions.
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".
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
Created by Geovanni Hernandez, last modified by Kenneth Wyrick 31 Oct 2016, at 07:11 PM
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.
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.
Created by Carl Robert Blesius, last modified by Gustaf Neumann 29 Oct 2016, at 12:00 PM
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.
Created by Olga C. Santos, last modified by Gustaf Neumann 08 Apr 2016, at 09:14 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 SCROM RTE and WCAG 1.0, which is to be solved with WCAG 2.0). Morevore, there may be some minor leval 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 , .
Information on the progress is also done in periodic dotLRN/OpenACS conferences:
Last modified: 2016-04-08 09:14:33.112388+02
Created by Emmanuelle Raffenne, last modified by Gustaf Neumann 19 Oct 2015, at 08:48 AM
.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
Last stable release: 2.5.0
Next release: see .LRN 2.5 Release Management
Download from .LRN download page
To install .LRN follow the instructions at .LRN_Installation
This .LRN Governance page is a proposal based on a meeting by Carl Blesius, Carlos Kloos, Roceal Hernandez and Caroline Meeks.
Site Specific Documentation
Official test servers
- Last modified: 2015-10-19 08:48:56.668188+02
Created by Alvaro Rodriguez, last modified by josue ruiz 21 Dec 2012, at 12:22 AM
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.
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.
Required:ltree module for postgresql2008-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
Postgresql 8.2.x +
Oracle 9i +
ajaxhelper 0.87d (needs upgrade to YUI 2.5.2+)Installation process:
- Get the following packages from branch oacs-5-4: dotlrn-all, xowiki, xotcl-core, views
- Get the following packages from HEAD: learning-content, learning-content-portlet, dotlrn-learning-content, ajaxhelper
- 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
- To run the script:
- /$path_to_content_patch/$ sh script.sh
- Install dotlrn, then install xowiki, xotcl-core, learn-content, learn-content-portlet, dotlrn-learn-content, ajaxhelper and views
- Restart the server
- Activate the applet in a course
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
- 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)
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.
- A new parameter called page_instance_id needs to be added to the ad_page_contract
- 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
- 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
- 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.
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
- September 23, 2009
- September 15, 2009
- July 14, 2009
- July 07, 2009
- June 30, 2009
- June 23, 2009
- June 16, 2009
- June 09, 2009
- June 02, 2009
- May 26, 2009
- May 19, 2009
- May 12, 2009
- May 05, 2009
- April 28, 2009
- April 21, 2009
- April 14, 2009
- April, 07, 2009
- March 31, 2009
- March 24, 2009
- March 17, 2009
- March 10, 2009
- March 03, 2009
- February 24, 2009
- February 17, 2009
- February 10, 2009
- February 03, 2009
- January 27, 2009
- January 20, 2009
- January 13, 2009
- January 06, 2009
- December 30, 2008
- December 23, 2008
- December 16, 2008
- December 09, 2008
- December 02, 2008
- November 25, 2008
- November 18, 2008
- November 11, 2008
- November 04, 2008
- October 28, 2008
- October 21, 2008
- October 14, 2008
- October 7, 2008
- September 30, 2008
- September 23, 2008
- September 16, 2008
- September 09, 2008
- September 02, 2008
- August 26, 2008
- August 19, 2008
- August 12, 2008
- August 05, 2008
- July 29, 2008
- July 22, 2008
- July 15, 2008
- July 08, 2008
Created by Hector Amado, last modified by Hector Amado 07 Oct 2009, at 11:34 PM
Educational Wiki (Eduwiki)
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+
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
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
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.
Start and end date editing functionality
Integration with evaluation package