MoodleDocs - User contributions [en]

Cron

2010-12-10T06:58:26Z

Odoardo: /* Starting cron */

Cron is the name of a Unix program that runs predefined tasks on a computer at regular intervals. It assists some of Moodle's modules to perform tasks on a scheduled basis. For example, the cron process might tell Moodle to check all discussion forums so it can mail out copies of new posts to people who have subscribed to that forum.

The primary Moodle script that does all this is located in the admin directory, and is called cron.php. However, it can not tell itself to run, so you need to set up a mechanism where this script is run regularly (eg every five or ten minutes). This provides a "heartbeat" so that the script can perform functions at periods defined by each module. This kind of regular mechanism is known as a '''cron service'''. The service can be part of a webhost or can be something run from a different server or computer.

==Overview of cron==
===Script overview===

The cron.php script looks through the mdl_modules table (assuming the default table prefix is mdl_) in the Moodle database for modules scheduled to have their cron functions run; it then looks in each such module directory for a function called module-name_cron in the lib.php file and runs it. It also looks through the mdl_block table for blocks scheduled for their cron methods (object functions) to be run; it then, for each such block, runs the cron method for a new object associated with that block (I'm omitting details for the benefit of non-programmers; programmers can read admin/cron.php for themselves). These files (the lib.php files and the files where the block classes are defined) can contain cleanup functions, email functions or anything that needs to be run on a regular basis. For example, cron will trigger the system to create the backups of courses at the time specified in the administration settings. It also triggers any messaging module or forum email notifications, but not all functions are called each time the cron runs. Some functions, such as unenrolling students who have not logged in or deleting old copies of log files, are only run occasionally. The cron.php file has a section which will randomly call these core tasks approximately 1 in 5 times the cron runs.

===Starting cron===
In Moodle 1.9 there are a number of way to invoke cron.php. Cron can be started from the address bar in a browser (URL usually ending in admin/cron.php), via a [[Daemon]], or wq1et, curl or some other code.

The cron process can be protected by a password.

The cronclionly Security > Site Policies setting with stop the browser URL trigger. This sets Moodle so that cron.php cannot be invoked by the Moodle URL. See the illustration below.

'''Menu: Security > Site policies'''

[[Image:Moodelcronadmin.png]]

:''TIP:'' While this is identified as CLI (command line interface) this is a bit misleading in that it does not mean that you have to be sitting at a shell account entering the command. If you enable this switch you can invoke cron.php through any set of batch or script files you wish, but it must be invoked via its correct location in the operating systems file structure. This can be especially frustrating for those not used to scripting in that environment is not typically provided.

===Cron service location and timing===
Note that the machine performing the cron '''does not need to be the same machine that is running Moodle'''. For example, if you have a limited web hosting service that does not have a cron service, then you might choose to run cron on another server or on your home computer. All that matters is that the cron.php file is called regularly.

The load of this script is not very high, so 5 minutes is usually reasonable, but if you're worried about it you can reduce the time period to something like 15 minutes or even 30 minutes. It's best not to make the time period too long, as delaying mail-outs can slow down activity within the course. Remember that mail-outs also wait for the editing time to expire before being queued for sending.

===Testing cron and manual trigger===

First, test that the script works by running it directly from your browser: ''<nowiki>http://example.com/moodle/admin/cron.php</nowiki>''

If cron is called from the command line by any user logged in to your Moodle it will create a temporary admin environment in order to run and then log the user out. You can disable command line running of cron by disabling the appropriate section in the cron.php file.

Now, you need to set up some of way of running the script automatically and regularly.

==Managing Cron on Windows systems==

There are two different ways for setting-up Moodle cron.php on Windows systems:

*Use the '''Moodle Cron package'''. The simplest way is to use this little package [http://download.moodle.org/download.php/windows/MoodleCron-Setup.exe MoodleCron-Setup.exe], which makes this whole thing very easy by installing a small Windows service. Run it and forget about it! :-)
*Use a '''Scheduled Task'''. If you prefer to use the built-in Windows Scheduler or are having trouble with moodle-cron-for-windows package, you can use wget for windows or php from the command line and setup a scheduled task. Just follow these steps:
** Choose either the '''php.exe/php-win.exe (command line binary)''' or '''wget'''
::The php.exe or php-win.exe binary (for PHP version 5 or later) is installed in your php folder (e.g. c:\php) will give you better performance when running the cron script.
::If you want to use wget, download a compiled version of wget for windows from the native GNU Win32 ports (http://unxutils.sourceforge.net/), from Heiko Herold's wget for windows page (http://xoomer.virgilio.it/hherold/) or Bart Puype's wget for windows page (http://users.ugent.be/~bpuype/wget/). If you use Heiko Herold's package, copy all of the .DLL files to your C:\Windows\system32 directory. Copy the wget.exe file to c:\windows (this makes sure wget is always in the search path).
:* Setup a '''Scheduled Task'''.
:: - Go to Start >> Control Panel >> Scheduled Tasks >> Add Scheduled Task.
:: - Click "Next" to start the wizard:
:: - Click in the "Browse..." button and browse to c:\php\php.exe or c:\windows\wget.exe and click "Open"
:: - Type "Moodle Cron" as the name of the task and select "Daily" as the schedule. Click "Next".
:: - Select "12:00 AM" as the start time, perform the task "Every Day" and choose today's date as the starting date. Click "Next".
:: - Enter the username and password of the user the task will run under (it doesn't have to be a priviledged account at all). Make sure you type the password correctly. Click "Next".
:: - Mark the checkbox titled "Open advanced properties for this task when I click Finish" and click "Finish".
:: - In the new dialog box, type the following in the "Run:" text box: <pre>c:\windows\wget.exe -q -O NUL http://my.moodle.site/moodle/admin/cron.php</pre> or <pre>c:\php\php-win.exe -f c:\moodle\admin\cron.php</pre> Replace "c:\moodle" with the path to your moodle directory or "my.moode.site" with the name of your site.<br><br>
:: - Click on the "Schedule" tab and there in the "Advanced..." button.
:: - Mark the "Repeat task" checkbox and set "Every:" to 5 minutes, and set "Until:" to "Duration" and type "23" hours and "59" minutes.
:: - Click "OK" and you are done.
* '''Test your scheduled task'''. You can test that your scheduled task can run successfully by clicking it with the right button and chosing "Run". If everything is correctly setup, you will briefly see a DOS command window while wget/php executes and fetches the cron page and then it disappears. If you refresh the scheduled tasks folder, you will see the ''Last Run Time column'' (in detailed folder view) reflects the current time, and that the Last Result column displays "0x0" (everything went OK). If either of these is different, then you should recheck your setup.
* '''Logging cron output'''. You may want to log the output of the cron script as it executes, in case you see the job is producing errors, backups are not being completed or users are experiencing delays in receiving forum emails. To do this, adjust the command so that it uses the php.exe and stores the output in a file called (for example c:\moodle\admin\cron.log). Here is an example of the php.exe command:
<pre>c:\php\php.exe -f c:\moodle\admin\cron.php > c:\moodle\admin\cron.log</pre>
If you experience problems logging the output of cron.php to a text file using the above command then read [http://moodle.org/mod/forum/discuss.php?d=139263#p609060 this] message by Iñaki Arenaza for an alternative way to log the output of Cron.

==Managing the cron job on Mac OS X with launchd==

It's really important to start the cron job every 5 minutes. The cron job assists most of Moodle's modules to perform tasks on a scheduled basis. For example, the discussion forums can only mail out copies of new posts to all subscribers if the cron job tells Moodle to do this.

In Mac OS X 10.5 you will find the system daemon ''launchd'' for this service. This daemon offers a standardized interface to any user and all programs started automatically by the system. Please look at http://developer.apple.com/macosx/launchd.html for more informations about the configurations and all parameters.

In our case the service should get the web page http://your-server-address/moodle19/admin/cron.php every 5 minutes. The configuration will be done by the file named ''moodle4mac.cron.plist'' which must be placed in the system folder ''/Library/LaunchDaemons/'' ... surely you can use any other file name but it should say something about the function of the service. The extension must be ''.plist''. After any reboot of your Mac server the cron service will start automaticly because the file is placed in the correct system folder.

===Use the graphical way===
You can use Lingon to add a new daemon plist or to edit one. It produces the same text as you can write in your text editor. http://sourceforge.net/projects/lingon/files/

[[Image:macosx-lingon.png]]

===Use a text editor===
Please use a text editor to write the needed file. You can open the Terminal and use the system editors vi or pico. But you can also write the text file with any GUI text editor ... I mostly use TextWrangler ... but do NOT take an editor for formatted texts like Microsoft Word or OpenOffice Writer. You must get pure text!

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key><false/>
<key>Label</key><string>moodle4mac.cron</string>
<key>ProgramArguments</key>
<array>
<string>curl</string>
<string>-s</string>
<string>http://your-server-address/moodle19/admin/cron.php</string>
</array>
<key>RunAtLoad</key><true />
<key>StartInterval</key><integer>300</integer>
<key>StandardErrorPath</key><string>/dev/null</string>
<key>StandardOutPath</key><string>/dev/null</string>
</dict>
</plist>

The label string must be the same as the file name is but without the extension ''.plist''. Save the text file ''/Library/LaunchDaemons/moodle4mac.cron.plist''. The owner of the file must be set to the system user ''root''. If you use a site with SSL (ie: it has an http'''s''':// protocol) you either need to have your SSL certificates listed for use by the CURL utility ([http://curl.haxx.se/docs/sslcerts.html see these docs] for more details) OR you must use the '-k' switch in addition to the '-s' switch used above; your arguments line would then read: `<string>-s -k</string>`.

That's all, really!

===How to start and stop the cron service===
You can start the new cron service in the Terminal.

sudo launchctl load /Library/LaunchDaemons/moodle4mac.cron.plist

The following command would stop the service. If you want to activate changes in the cron service you need to ''unload'' and then to ''load'' the daemon again.

sudo launchctl unload /Library/LaunchDaemons/moodle4mac.cron.plist

===Only one service for two servers?===
For my server I needed to have a cron service for to instances ''moodle19'' and ''moodle20'' ... no problem ... with the typo ''moodle[19-20]'' I will get a cron service for both.

<nowiki>curl -s http://your-server-address/moodle[19-20]/admin/cron.php</nowiki>

To see if the cron service works correctly you should look at the ''access.log'' of your web server. The cron.php should be accessed every 5 minutes ... on my server for both Moodle instances ''moodle19'' and ''moodle20'' ... oh yes, it works!!

192.168.0.220 - - [30/Jul/2009:22:10:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:10:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1403
192.168.0.220 - - [30/Jul/2009:22:11:18 +0200] "OPTIONS * HTTP/1.0" 200 -
192.168.0.220 - - [30/Jul/2009:22:15:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 735
192.168.0.220 - - [30/Jul/2009:22:15:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 964
192.168.0.220 - - [30/Jul/2009:22:20:56 +0200] "GET /moodle19/admin/cron.php HTTP/1.1" 200 1136
192.168.0.220 - - [30/Jul/2009:22:20:57 +0200] "GET /moodle20/admin/cron.php HTTP/1.1" 200 1365

==Managing cron on web hosting services==

Your web-based control panel may have a web page that allows you to set up a cron service process.

===CPanel cron service===
If you are using CPanel, login then look for "Advanced" category towards the bottom of the page. Click on Cron Jobs -> Advanced (Unix style). Enter the following for the cron to run every 30 minutes.

Email address for output: emailaddress@mydomain.con
Minute:*/30
Hour:*
Day:*
Month:*
Weekday:*
<nowiki>Command: wget -q -O /dev/null http://www.mydomain.com/moodle/admin/cron.php</nowiki>

Click Commit Changes. Check your email for the output.

[[Image:Cpanel-cron-setup.JPG]]

===Other systems cron service===
For other systems, look for a button called "Cron jobs". In there you can put the same sort of Unix commands as listed below.

If you don't have permissions to run the 'wget' command on the server, you can use this php command:

/usr/local/bin/php -q /real/path/to/script/admin/cron.php

For example:

/usr/local/bin/php -q /home/username/public_html/moodle/admin/cron.php

If you don't know what is the real path of your Moodle folder you can use the PHP command realpath.

Another alternative, if you do not have permission to run the 'wget' command, may be to use a curl command.

For example:

curl --silent --compressed http://mydomain.com/moodle/admin/cron.php

==Using a cron command line in Unix==

There are different command line programs you can use to call the page from the command line. Not all of them may be available on a given server.

'''Note:''' The examples with wget, lynx, and similar are '''not''' the same as the "CLI only" cron checkbox, mentioned above (the configuration variable "cronclionly"). wget, lynx, and other similar utilities are Unix command-line HTTP clients, and thus running cron.php in this way is the same as running it in a browser, from Moodle's point of view.

For example, you can use a Unix utility like 'wget':

wget -q -O /dev/null <nowiki>http://example.com/moodle/admin/cron.php</nowiki>

Note in this example that the output is thrown away (to /dev/null).

A number of users of Moodle have found that 'wget' sometimes fails. Especially if you have trouble with email digests not being sent on a daily basis to all users, an alternative command that solves the problem is:

php <nowiki>http://example.com/moodle/admin/cron.php</nowiki>

The same thing using lynx:

lynx -dump <nowiki>http://example.com/moodle/admin/cron.php</nowiki> > /dev/null

Note in this example that the output is thrown away (to /dev/null).

Alternatively, you can use a standalone version of PHP, compiled to be run on the command line. The disadvantage is that you need to have access to a command-line version of php. The advantage is that your web server logs aren't filled with constant requests to cron.php and you can run at a lower I/O and CPU priority.

/opt/bin/php /web/moodle/admin/cron.php

Example command to run at lower priority:

ionice -c3 -p$$;nice -n 10 /usr/bin/php /moodle/admin/cron.php > /dev/null

===Using the crontab program on Unix===

All that Cpanel does is provide a web interface to a Unix utility known as crontab. If you have a command line, you can set up crontab yourself using the command:

crontab -e

and then adding one of the above commands like:

*/30 * * * * wget -q -O /dev/null <nowiki>http://example.com/moodle/admin/cron.php</nowiki>

The first five entries are the times to run values, followed by the command to run. The asterisk is a wildcard, indicating any time. The above example means run the command ''wget -q -O /dev/null...'' every 30 minutes (*/30), every hour (*), every day of the month (*), every month (*), every day of the week (*).

The "O" of "-O" is the capital letter not zero, and refers the output file destination, in this case "/dev/null" which is a black hole and discards the output. If you want to see the output of your cron.php then enter its url in your browser.

* [http://linuxweblog.com/node/24 A basic crontab tutorial]
* [http://www.freebsd.org/cgi/man.cgi?query=crontab&apropos=0&sektion=5&manpath=FreeBSD+6.0-RELEASE+and+Ports&format=html Online version of the man page]

For '''beginners''', "EDITOR=nano crontab -e" will allow you to edit the crontab using the [http://www.nano-editor.org/dist/v1.2/faq.html nano] editor. Ubuntu defaults to using the nano editor.

Usually, the "crontab -e" command will put you into the 'vi' editor. You enter "insert mode" by pressing "i", then type in the line as above, then exit insert mode by pressing ESC. You save and exit by typing ":wq", or quit without saving using ":q!" (without the quotes). Here is an [http://www.unix-manuals.com/tutorials/vi/vi-in-10-1.html intro] to the 'vi' editor.

==See also==

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=41827 Cron - can someone give me a quick confirmation of function?]
*[http://moodle.org/mod/forum/discuss.php?d=97684 Cronjob Question]
*[http://moodle.org/mod/forum/discuss.php?d=97457 Slow cron : avoiding simultaneous cron]
*[http://moodle.org/mod/forum/discuss.php?d=117168 Visibility of cron.php]
*[http://moodle.org/mod/forum/discuss.php?d=139263#p609060 How to log the output of a Scheduled Task on Windows] - this discussion explains a nice trick that can be very useful when you are experiencing problems with your Windows Scheduled Task and you need to log the output of the Scheduled Task to a log file.

[[Category:Installation]]

[[es:Cron]]
[[fr:Cron]]
[[nl:Cron]]
[[sk:Cron]]
[[pl:Cron]]
[[ja:Cron]]

Repositories FAQ

2010-12-09T07:28:00Z

Odoardo: /* How can I enable repositories in Moodle? */

{{stub}}

==How can I enable repositories in Moodle?==

Repositories can be enabled by an administrator in ''Site administration > Plugins > Repositories > Manage repositories''.

All enabled and visible repositories will appear in the file picker.

==How can I delete an embedded file previously added using the file picker?==

There is no need to do anything, as any unused files are detected and then deleted automatically after a period of time. Users cannot delete files manually, since they may be used elsewhere.

==See also==

* [[Repositories]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=1807 Repositories forum]

[[Category:Repositories]]
[[Category:FAQ]]

[[de:Repositories FAQ]]

Development:Repository API

2010-11-03T10:48:27Z

Odoardo: /* Repository plugins */

{{Moodle_2.0}}

The page is open for everyone so everyone can help correct mistakes and help with the evolution of this document. However, if you have questions to ask, problems to report or major changes to suggest, please add them to the [[Development_talk:Repository_API|page comments]], or start a discussion in the [http://moodle.org/mod/forum/view.php?id=1807 Repositories forum]. We'll endeavour to merge all such suggestions into the further development and fix all kinds of problems.

Note that parts of this document have been now split off into a separate [[Development:File_API]]

==Objectives==

# Allow all Moodle users to easily bring content into Moodle from external repositories
# Provide a consistent interface to any external repository, for any Moodle module

==Use cases==

===Teacher adding an external file as a new resource===

# Teacher wants to add a new resource to a course
# Teacher clicks the "Choose a resource" button
# Teacher is presented with a simple file picker to choose a file (with a menu to switch between multiple configured repositories)
# Teacher chooses a file in an external repository
# File is COPIED into Moodle and stored by the resource module
# File is marked as owned by that user
# Whenever someone wants to view that file, the resource module controls access (see [[Development:File API]] )

===Teacher linking to an external file as a new resource (think video repository) ===

# Teacher wants to display a file in the repository
# Teacher clicks the "Choose a resource" button
# Teacher is presented with a simple file picker to choose a file (with a menu to switch between multiple configured repositories)
# Teacher chooses a file in an external repository
# Link to the file is COPIED into Moodle and stored by the resource module
# Link is marked as owned by that user
# Whenever someone wants to follow that link, the resource module controls access (see [[Development:File API]] )

===Student submitting an assignment===
# Student needs to submit an assignment and presses the "Choose files" button
# Student sees a "file picker" where they can see files listed on any of several configured repositories ([https://docs.moodle.org/en/Image:Filepicker_login.jpg file picker login], [https://docs.moodle.org/en/Image:Filepicker_browser.jpg file picker browser], [https://docs.moodle.org/en/Image:Filepicker_search.jpg file picker search])
# Student chooses MySpace from the list
# Student is prompted to enter MySpace username/password (if admin allows it, a checkbox could be there to "remember this for next time" but remember security)
# Student sees their files in MySpace and chooses one or more
# Files are copied from MySpace to Moodle
# Assignment module controls the permissions so that only the Student and assignment graders can see the file (other students would not have permission).

===Student attaching an image to a forum===
# Student needs to attach an image and presses the "Choose files" button in the posting screen
# Student sees a "file picker" where they can see files listed on any of several configured repositories
# Student chooses Mahara from the list
# Student is prompted to enter Mahara username/password
# Student sees their files in Mahara and chooses one image
# Image is copied to Moodle
# Image file is attached to forum post by Forum module (by reference)
# Forum module controls permissions so that anyone who can read that forum can see that file

===Student attaching the same image in another forum===

# Student needs to submit an assignment and presses the "Choose files" button
# Student sees a "file picker" where they can see files listed on any of several configured repositories
# Student chooses "Local files" from the list and sees all the files they've permission to use
# A COPY of the image file is attached to forum post by Forum module
# Forum module controls access to this file.

Please add more use cases in this same format

==Mock screenshots==
When you first call up the file picker and choose a repository, you might be asked to log in (if saving of passwords is not allowed):

[[Image:Filepicker_login.jpg]]

Browsing files could look something like this:

[[Image:Filepicker_browser.jpg]]

And you can also search:

[[Image:Filepicker_search.jpg]]

==General architecture==

Each repository plugin (a standard Moodle plugin stored under /repository/xxx) will subclass the standard API and override methods specific to that repository.

As is usual in Moodle, there will be admin settings to disable/enable certain repository plugins as standard, as well as user settings so that users can add their own personal repositories to the standard list (eg [http://briefcase.yahoo.com Yahoo Briefcase] or [http://docs.google.com Google Docs]) and to select their default repository.

Once a repository has been used the file will usually be copied into Moodle there and then. However there will also be options to:
* only return the URL to the file if it's desired to keep it external (but this does present security and integrity risks), or
* refresh the local file copy regularly and automatically
* refresh the file manually if desired

Once in Moodle, it is subject to the [[Development:File API]] for access control like any other file.

==Repository requirements==

From the Moodle point of view, each repository is just a hierarchy of nodes.

The repository MUST provide:
# A URI to download each node (eg file).
# A list of the nodes (eg files and directories) under a given node (eg directory). This allows Moodle to construct a standard browse interface (much like a standard OS file picker).

The repository can OPTIONALLY:
# Require some authentication credentials
# Provide more metadata about each node (mime type, size, dates, related files, dublin core stuff, etc)
# Describe a search facility (so that Moodle can construct a search form)
# Provide copyright and usage rules (or just information about the rules)

==Repository plugins==

Some plugins I'd like to see developed for the first version are:
* box - an interface to [http://box.net box.net]
* mahara - an interface to a Mahara installation
* Server Files - very similar to the current course-based file manager, except user-based
* Remote Moodle - an interface to another Moodle site, accessed over a secure mnet connection
* googledocs - an interface to [http://docs.google.com Google Docs]
* s3 - an interface to [http://www.amazon.com/gp/browse.html?node=16427261 Amazon S3]
* flickr - an interface to [http://flickr.com flickr]
* WebDAV - to access arbitrary external WebDAV servers
* merlot - an interface to the learning materials in [http://www.merlot.org/merlot/materials.htm Merlot.org]
* File System - a plugin to list files on local file system, of course, you can mount remote files to this local directory
* youtube - an interface to [http://youtube.com YouTube]
* jsr170 - an interface that can talk to anything that supports jsr170 (eg [http://www.alfresco.com/ Alfresco])
* oki - an OKI emulator allowing us to access things with OKI interfaces,like [http://www.fedora.info/ Fedora]
* briefcase - an interface to [http://briefcase.yahoo.com/ Yahoo Briefcase]
* myspace - an interface to MySpace files (perhaps via [http://www.programmableweb.com/api/myspace this MySpace API])
* skydrive - an interface to Microsoft's [http://skydrive.live.com/ SkyDrive] files
* Dropbox - an interface to Dropbox files [http://www.dropbox.com]
* facebook - an interface to Facebook files
* [http://www.dspace.org/ Dspace] - a repository from MIT
* DOOR - another popular open source repository
* SMB shares - An interface for windows shares e.g. personal folders on network drives. Would need to link with LDAP as usernames will often be wholly/partially the same as network folder names. This could be done using SAMBA, but would also need to work on windows machines natively. See [http://moodle.org/mod/data/view.php?d=13&rid=991 this block] for a linux implementation.

==Tables==

=== repository ===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|autoincrementing

|-
|'''type'''
|varchar(255)
|
|The type of the repository

|-
|'''visible'''
|tinyint(1)
|
|

|-
|sortorder
|int(10)
|
|
|}

=== repository_instances ===

This table contains one entry for every configured external repository instance.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|autoincrementing

|-
|name
|varchar 255
|
|A custom name for this repository (non-unique)

|-
|'''typeid'''
|int(10)
|
|The id of repository type

|-
|'''userid'''
|int(10)
|
|The person who created this repository instance

|-
|'''contextid'''
|int(10)
|
|The context that this repository is available to ( = system context for site-wide ones)

|-
|username
|varchar(255)
|
|username to log in with, if required (almost never!)

|-
|password
|varchar(255)
|
|password to log in with, if required (almost never!)

|-
|timecreated
|int(10)
|
|The time this repository was created

|-
|timemodified
|int(10)
|
|The last time the repository was modified
|}

=== repository_instance_config ===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|autoincrementing

|-
|'''instanceid'''
|int(int)
|
|

|-
|'''name'''
|varchar(255)
|
|

|-
|value
|Text
|
|
|}

===File types===

The context at which someone is inserting a file may require certain file types (eg uploading a new user profile image is only looking for images).

To support this, the calling code needs to be able to specify the required mimetypes, and the listing code should be able to filter the results based on these mimetypes. Ideally the repository itself can do the filtering for ultimate speed (though not all repositories will support this).

We will have to develop special new mimetypes for Moodle files like backups (application/vnd.moodle.backup) and IMS learning design (application/vnd.moodle.imsld) etc

==Technical walkthrough==

(See also the functional spec for the [[Development:Repository_File_Picker]] )

There are two main cases where the repository API will be used: as part of a Moodleform to add a file and as part of the HTML editor to add a media element into some HTML). We also have to cater for the using Moodleforms without Javascript.

In all of these cases the files will be uploaded to Moodle while using the file picker dialog and stored in a temporary file area owned by the currently active user. It is only AFTER the submission of the entire Moodleform that we will know the full context, itemids to store the file properly, so at this time the file will be copied into the correct filearea.

===Case 1: As part of a Moodleform with Javascript===

1. Moodle module code calls a "filepicker" moodleform item whenever a file is required, which includes the following information to pass to the File API:

eg $mform->addElement('filepicker', 'uniqueelementid', $fullname, $data)

2. When rendering the form, Moodle will display a read-only filename field with an '''"Add file"''' button next to it. There will also be a hidden field to store a file reference later (this is what actually gets used, the filename field is just for users to see something).

3. When the add file button is pressed, the form will be "replaced" in the page by a larger resizeable area containing an AJAX file picker. (After picking the display can be closed). (There could be a user option to make this a popup window instead, if required)

4. The AJAX file picker interface will list all the active repositories as a menu, and list files in one of several formats (like Windows/Mac/Linux): Details, Names, Icons.

5. For each plugin, the AJAX interface will prompt the user to login first (if required) asking the plugin to log in behind the scenes. It'll also ask the plugin to return listing data in response to clicks and searches.

6. Finally, when the user selects a file and clicks the "Select" button, the AJAX interface will trigger a method in the plugin that will fetch the file and call the File Storage API to '''store''' the file using the '''uniqueelementid''' and the current user info. While this is happening, the interface should show some sort of progress bar (ideally) or at least a "loading file" image/sign/message.

7. After a file has finally been selected we will have a file ID which we can pass back to the original Moodle form (to the hidden field named '''uniqueelementid_formid'''). The picker can then rename the read-only filename field before it hides itself.

8. Submitting the form will trigger the mform processing for this field, which will check fields, create things in the module etc. Once this has been finally successful the developer must call an mform function to "fix" the info for each file and "move" it into the module file area:

eg $mform->store_local_file('uniqueelementid', $context, $filearename, $itemid, $filepath);

9. Cron jobs in File Storage api should automatically delete any files in the user's tempfile area that are older than 7 days or move them into a trash can in the user's file area (perhaps).

===Case 2: As part of a Moodleform without Javascript===

Steps 1-2 are the same as for the case with Javascript.

3. The add file button is a submit button for the form with a different value. When the add file button is pressed,
* the whole form will be ''submitted'' to the original location (but with a different submit button value)
* moodleforms get_data() will detect this is a "repository save" and can save the full POST info in the current session tagged with the id of the openfile element, together with the URL to return to
* moodleforms get_data() then redirects the user to a new page showing the main picker interface

4. The file picker interface will have to be a completely new and separate interface from the AJAX one. It could be a long hierarchy listing, or reload a lot.

5. Finally, when the user selects a file and submits using the "Select" button to picker.php, it will trigger a method in the plugin that will fetch the file and call the [[Development:File_API|File API]] to store the file using the filearea and context information we already had. While this is happening, the interface can show some sort of progress bar (ideally) or at least a "loading file" image/sign/message.

6. After this, picker.php will redirect/continue back to the original form page. The form can be constructed as usual, however, when the form is rendered using display() method moodleforms should now look for relevant saved content in the session and use that to override any content in the form (and then delete the saved info in the session).

Steps 8-9 are the same as for the case with Javascript.

===Case 3: As part of a HTML editor===

The key thing here is a move away from storing any absolute URLs to files in our HTML texts. Instead we'll store relative names.

1. The moodleform for a textarea (HTML editor) will require a path to the filearea associated with this HTML. eg '''wwwroot/pluginfile.php/13/content/0/'''. This would have to be the user_draft area if the filearea doesn't exist yet eg '''wwwroot/draftfile.php/userid/tempfile/uniquelementid'''

2. All textarea content will also need to have str_replace done on it to replace @@pluginfile@@/somefilenames.jpg in the content to use this path so that it comes up right in the editor. (Note this also needs to be done on every format_text command too when showing this text.)

3. The path parameter also needs to be added to the editor configuration in the current page.

4. Editor plugins can be modified to look for these variables in the editor configuration.

5. When adding an image or other media element, the same AJAX repository picker will show up as a popup div to allow people to pick from any repository and choose files to download. The repository picker is responsible for downloading the file in real-time, storing it as a user temporary file if the filearea doesn't already exist, prefixing the supplied path to the filename and returning a URL back to the dialog text input before closing.

6. On submission, and after the HTML is stored, we might now have a new permanent filearea, so we'll need to update any associated temporary files to make sure they have the proper file area information.

==Repository plugins==

Each repository plugin is required to contain the following elements:

===class repository()===

This class implements the interface to a particular repository, for browsing, selecting and updating files. The base class (repository) is defined in /repository/lib.php, while each repository defines an inherited class (eg repository_alfresco) in /repository/repositoryname/repository.class.php

Repositories can redefine any of these methods as required (and in some instances, MUST redefine them):

====__construct($repositoryid, $contextid, $options=array(), $readonly)====

'''MUST''' redefine

Accept necessary parameters, and do initialization of repository.

====get_file($url, $file = '')====

Given a URL, download a file from there, save the file in a temporary directory.

====get_link($info)====
Get the url of external resource

====get_listing($path='/', $page='''''''')====

Given a path, and perhaps a search, get a listing of files. In the case of AJAX file picker, this function should return json format Javascript array.

====search($keyword)====
Search repository by given keyword, it will return an array of the same format of get_listing

====print_login()====

Show the login screen, if required. In the case of AJAX file picker, this function should return json format array which defined the login form.

====print_search====

Print the search form, it will return a json string

====get_meta()====
Return information for creating ajax request, it is private function, you don't need to rewrite it.

====create()====
Create an instance

====delete()====
Delete this instance from `repository` table

====hide()====
Hide a repository instance from file picker list

====set_option()====
set options in data1-data5 fields, can be overrided

====get_option()====
get option list or a specific option from database

====get_type_option_names()====
If this plugin needs admin settings, please refine this function to return option names.

====type_config_form()====
If get_type_option_names return non empty array, this function '''MUST''' redefine, it will help to build the setting form.

====get_instance_option_names()====
If plugin instance needs settings, this function will return instance option names.

====instance_config_form()====
If get_instance_option_names return non empty array, this function '''MUST''' redefine, it will help to build the instance setting form.

====supported_filetypes()====
What file types are supported by this repository plugin, it will return an array, the file type name is defined in a [http://freemind.sourceforge.net/wiki/index.php/Main_Page freemind] file in lib/file/file_types.mm

====supported_returntypes()====
The repository plugin could support external link or copying files to moodle. If the plugin support file link only, developer should override this function to return FILE_EXTERNAL, if plugin support copying file only, it should return FILE_INTERNAL, by default, plugin supports both.

====filter()====
Filter file listing to exclude specific file types

===icon.png===

A logo that represents the repository. Ideally square but we should handle all sizes.

==See also==

* [[Development:Repository Administration Specification]]
* [[Development:Repository Interface for Moodle/Course/User]]
* [[Development:Repository plugins]]
* [[Development:Repository File Picker]]
* [[Development:File API]]
* [[Development:Portfolio API]]
* MDL-13766 and MDL-16543 Repository API Meta issues

[[Category:Repositories]]

[[ja:開発:リポジトリAPI]]

Book module

2010-09-16T01:38:00Z

Odoardo: /* Installation */

{{Book}}

The '''Book module''' makes it easy to create multi-page resources with a book-like format. It is contributed by [http://moodle.org/user/view.php?id=12863&course=5 Petr Škoda]. This module can be used to build complete book-like websites inside of your Moodle course.

Previously created websites can be imported directly into the Book module. Books can be printed entirely or by chapter.

The book module allows you to have main chapters and sub chapters, but it goes no deeper. In other words, sub chapters cannot have their own sub chapters. This was an intentional decision by the creator of the book module. He intended this to be a simple resource for teachers and students.

The book module is not interactive. You can, however, link to [[Choice module|choices]], [[Forum module|forums]] etc., from within a book. And you can include multimedia objects like [[Flash]] movies in your book.

==Installation==
* Select the correct version of the "book.zip" module for your Moodle installation
* Unpack the zip file into the mod folder of your Moodle site
* Login to the Moodle site as administrator and
* In site administration block click on notifications
* Moodle will install the Book module.
* [[Creating_a_book|Add a book as an activity]]

==See also==
*[http://moodle.org/mod/data/view.php?d=13&rid=319 Book Module] is a Modules and plugins database page for downloads and more information.
*Discussions: please create or find a discussion topic in the [http://moodle.org/mod/forum/view.php?id=2633 Book module forum]
*Examples: The manuals at [http://moodle.tokem.fi tokem.fi] are a series of book modules. Each book is designed for a different level of Moodle user.
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=76092 Using a Lesson to simulate a Book] forum discussion

[[Category:Contributed code]]

[[es:Book]]
[[eu:Liburua]]

Messaging

2010-09-11T11:09:06Z

Odoardo: Changed 'People bock' to 'People block'

{{Messaging}}The Messaging system default is not limited to a specific course or role. Logged in users (students, teachers or administrators) may send messages to each other regardless of whether they are enrolled on the same course. This is unlike [[Forums]] and [[Chats]] that can be course, role or group specific.

Messages are sent via a popup Message window. This can be found via:
*[[Participants]] link in a course's [[People block]] (Send message button on each user's page),
*[[Online Users block]] (if turned on) has a message icon [[Image:Message.gif]] next to each user's name
*Browse list of users in the [[Course administration block]] (send message button on each user's page)

Site-wide messaging may be disabled/enabled by the Administrator in the permissions section of ''Administration > Configuration > Variables'' in Moodle 1.6, in ''Administration > Security > Site policies'' in 1.7 to 1.9, or in ''Administration > Advanced features'' in 2.0.

Alternatively, to encourage the use of messaging in a course, you may wish to add a [[Messages block]] and/or an [[Online Users block]] to the course page.

==Sending messages==

To send a message to an individual:
#In the Messages window click on the Search tab to search for the person, if appropriate checking the box "Only in my courses", then click on their name. (Alternatively, if the person is listed in the Online Users block, simply click on the "Add/send message" envelope opposite their name.)
#Type the message in the pop-up box then click on the "Send message" button.

To send a message to selected course participants (for teachers only):
#Click on the Participants link in the People block on the course page.
#Select participants from the list or use the "Select all" button at the bottom of the list.
#Choose "Add/send message" from the "With selected users..." drop-down menu.
#Type the message then click the "Preview" button.
#Assuming you are satisfied with the message, click the "Send" button.

==Reading and replying to messages==

When you are sent a message, the Messages window will pop-up. Also, the Messages block will display the name of the person sending the message with a link to read the message. If you have set the email option (see Message Settings below), then you will get a copy of the message in your email after the time you have specified if you are not logged in.

After reading a message, you may type a reply then click on the "Send message" button.

==Searching messages==
[[Image:MsgSearch.jpg|thumb|Message window Search tab]]
In addition to searching for people, the Search tab in the Messages window provides the option to search for keywords, only messages to or from you, and to include in the search people you have previously blocked from contacting you.

==Managing contacts==
[[Image:MsgContacts.jpg|thumb|Message window Contacts tab]]
People may be added to your list of contacts (or blocked from contacting you) by clicking the "Add contact" (or "Block contact") icon opposite their name in the Messages window.

By default the contact list is empty. In order to send a message or to create a shortcut to the person you are sending, go to the Search tab.

==Message history==

A record of messages sent to/from a person may be obtained by clicking the "History" icon opposite their name in the Messages window.

==Message settings==
[[Image:MsgSettings.jpg|thumb|Message window Settings tab]]
Message settings may be changed via the Settings tab in the Messages window.

Here you can decide on having a popup Message window whenever you get a new message, blocking messages from people who are not on your Contacts list, having an audio signal for a new message, using a HTML editor, or getting email messages when you are offline.

Note: It's possible to set a different email address for receiving copies of messages to the email address in your profile.

==See also==
*[[Messaging FAQ]]
*[[Using Moodle book]] Chapter 5: Forums, Chats, and Messaging
*[[Messaging enhancements]] (contributed code)
*[[Development:Messaging 2.0]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=27559 What facilities are there for seeing other users' messages?]
*[http://moodle.org/mod/forum/discuss.php?d=58977 How can I see student messages?]
*[http://moodle.org/mod/forum/discuss.php?d=34972 Viewing old messages?]
*[http://moodle.org/mod/forum/discuss.php?d=63401 Restrict Messaging to Course Participants/Teachers]

[[es:Mensajería]]
[[eu:Mezularitza]]
[[de:Mitteilungen]]
[[fr:Messagerie]]
[[ja:メッセージング]]

Messaging

2010-09-11T11:06:55Z

Odoardo: Changed 'person may obtained' to 'person may be obtained' in the "Message history" section

{{Messaging}}The Messaging system default is not limited to a specific course or role. Logged in users (students, teachers or administrators) may send messages to each other regardless of whether they are enrolled on the same course. This is unlike [[Forums]] and [[Chats]] that can be course, role or group specific.

Messages are sent via a popup Message window. This can be found via:
*[[Participants]] link in a course's [[People block]] (Send message button on each user's page),
*[[Online Users block]] (if turned on) has a message icon [[Image:Message.gif]] next to each user's name
*Browse list of users in the [[Course administration block]] (send message button on each user's page)

Site-wide messaging may be disabled/enabled by the Administrator in the permissions section of ''Administration > Configuration > Variables'' in Moodle 1.6, in ''Administration > Security > Site policies'' in 1.7 to 1.9, or in ''Administration > Advanced features'' in 2.0.

Alternatively, to encourage the use of messaging in a course, you may wish to add a [[Messages block]] and/or an [[Online Users block]] to the course page.

==Sending messages==

To send a message to an individual:
#In the Messages window click on the Search tab to search for the person, if appropriate checking the box "Only in my courses", then click on their name. (Alternatively, if the person is listed in the Online Users block, simply click on the "Add/send message" envelope opposite their name.)
#Type the message in the pop-up box then click on the "Send message" button.

To send a message to selected course participants (for teachers only):
#Click on the Participants link in the People bock on the course page.
#Select participants from the list or use the "Select all" button at the bottom of the list.
#Choose "Add/send message" from the "With selected users..." drop-down menu.
#Type the message then click the "Preview" button.
#Assuming you are satisfied with the message, click the "Send" button.

==Reading and replying to messages==

When you are sent a message, the Messages window will pop-up. Also, the Messages block will display the name of the person sending the message with a link to read the message. If you have set the email option (see Message Settings below), then you will get a copy of the message in your email after the time you have specified if you are not logged in.

After reading a message, you may type a reply then click on the "Send message" button.

==Searching messages==
[[Image:MsgSearch.jpg|thumb|Message window Search tab]]
In addition to searching for people, the Search tab in the Messages window provides the option to search for keywords, only messages to or from you, and to include in the search people you have previously blocked from contacting you.

==Managing contacts==
[[Image:MsgContacts.jpg|thumb|Message window Contacts tab]]
People may be added to your list of contacts (or blocked from contacting you) by clicking the "Add contact" (or "Block contact") icon opposite their name in the Messages window.

By default the contact list is empty. In order to send a message or to create a shortcut to the person you are sending, go to the Search tab.

==Message history==

A record of messages sent to/from a person may be obtained by clicking the "History" icon opposite their name in the Messages window.

==Message settings==
[[Image:MsgSettings.jpg|thumb|Message window Settings tab]]
Message settings may be changed via the Settings tab in the Messages window.

Here you can decide on having a popup Message window whenever you get a new message, blocking messages from people who are not on your Contacts list, having an audio signal for a new message, using a HTML editor, or getting email messages when you are offline.

Note: It's possible to set a different email address for receiving copies of messages to the email address in your profile.

==See also==
*[[Messaging FAQ]]
*[[Using Moodle book]] Chapter 5: Forums, Chats, and Messaging
*[[Messaging enhancements]] (contributed code)
*[[Development:Messaging 2.0]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=27559 What facilities are there for seeing other users' messages?]
*[http://moodle.org/mod/forum/discuss.php?d=58977 How can I see student messages?]
*[http://moodle.org/mod/forum/discuss.php?d=34972 Viewing old messages?]
*[http://moodle.org/mod/forum/discuss.php?d=63401 Restrict Messaging to Course Participants/Teachers]

[[es:Mensajería]]
[[eu:Mezularitza]]
[[de:Mitteilungen]]
[[fr:Messagerie]]
[[ja:メッセージング]]

Installation guide - Moodle for Windows on a USB Memory Stick

2010-09-02T11:20:30Z

Odoardo: /* Poodle - live Moodle on USB storage */

[http://www.chsoftware.net/en/useware/wos/wos.htm CH Software's WOS - Webserver on a Stick] packages a complete Apache/PHP/MySQL webserver with a wrapper that automatically configures and starts the servers; the Small Edition takes only 20 Mb. It is published under the GNU GPL.

The complete package with a vanilla Moodle 1.5.3, WOS Portable SE 1.1.1, Apache 2.0.5, PHP 5.1.2 (and 4.4.1), and MySQL 4.1.18-nt - all free, open source software - occupies less than 100Mb.

==Installation==

For best results you should always install and run WOS from the root directory of a drive. The first time it's run, WOS configures the paths for the servers based on the current directory.

<big>Note: Make sure you stop IIS service which may already be running on your PC.</big>

1. Start by downloading the latest versions of [http://www.chsoftware.net/en/useware/wos/wos.htm?action=download WOS Portable or WOS Portable Small Edition.]

1a. Thanks to [http://moodle.org/mod/forum/discuss.php?d=45618#211677 Matt Campbell], you can also get the complete Moodle on a Stick (MOS) package as a single zip download from this
URL:http://instructor.metrotech.org/~mcampbell/USBMoodle.zip
(Includes Moodle 1.5.3 and 1.6.0, from 2006, as well as the WOS package) Simply unzip the file onto a USB stick, check the readme
file to make sure your setup is correct, and run

start.exe

if using this method.

2. Unzip the file and copy to your USB Stick.
Switch to the stick and double click start.exe to begin the WOS installation.

3. Choose your language, then click through the Terms of Use. WOS starts up and displays the WOS Status dialog box and opens your web browser to the WOS start page

* You should now see the follow on the WOS startup page.
Apache 2.0.55 is running
PHP 5.1.2 works (or PHP4 if you configured it that way)
MySql 4.1.18-nt is running
Document Root is: F:/www

4. Setup your Database
Click on the PHPMyAdmin link on the Start page.
In PHPMyAdmin, type a name for your database. ie: 'moodle' and click Enter.

5. Now Download your preferred version of Moodle from [http://download.moodle.org/ the Moodle Download page] and unzip the file to your www directory on the USB stick.

6. Run Moodle Installation.
Using the directory and settings above, the URL is http://localhost/moodle/install.php.

Now you simply work through the normal Moodle installation procedures.
NOTE: During the databases setup, use root as the database user and leave the password field blank (warning: security risk if opening to your LAN/WAN)It should work just like it does on the web or on your hard drive windows installation.

==Troubleshooting==

Moodle requires a number of PHP settings to be active for it to work. On most servers these will already be the default settings. However, I noticed the WOS package required register_globals needed to be turned off and magic_quotes gpc turned On. These are defined in PHP's configuration file (usually called php.ini):

WOS Portable is freeware, and there is no official support.

If you have a problem after running through the above, try the troubleshooting hints on the [http://www.woswiki.chsoftware.net/index.php/General_troubleshooting WOS Wiki].

==See also==
*Another way to do it (in French) [http://agir.transfer-tic.org/moodleauf/mod/resource/view.php?id=727 Guide de clonage d'un site Moodle]
*[[sk:Moodle Windows Inštalácia na USB kľúči]]
*Another way to do it (with SQLite database)- [https://docs.moodle.org/en/Student_projects/SQLite#Moodle.2FSQLite_on_a_stick Moodle/SQLite on a stick]

==Poodle - live Moodle on USB storage==
Poodle (short for Portable Moodle) is a software tool designed to allow for the delivery of Moodle content offline.

Moodle is designed to offer an online environment for learning and collaboration between teachers and students. Many different education institutions have created content for classes and instruction in the Moodle platform. The Poodle is a way to bring some of that content to those who are in low-bandwidth and no-bandwidth areas.

[http://www.maflt.org/products/poodle website and download]

[[Category:Installation]]
[[hr:Upute za instalaciju - Moodle za Windows na USB memoriji]]

Teacher role

2009-04-08T11:50:46Z

Odoardo: /* Teacher overview */

==Teacher overview==
'''Teacher''' is one of the core user [[Assign roles|roles]] in Moodle. The others include [[Administrator]], [[Student]] and [[Guest access|Guest]]. These roles have privileges and control what you can and can't do within particular areas of a Moodle. In short, an ''Administrator'' can do almost anything and go anywhere, a ''Teacher'' has control over a specific course within a Moodle and the experience of their learners, and a ''Student'' participates in a course.

The term 'Teacher' can be changed to something else in the course settings or in the site settings. For example 'Tutor', 'Facilitator', 'Professor' or 'Instructor' might be more appropriate. The default term is Teacher and is generally used throughout Moodle documentation.

A participant/user is assigned the 'Teacher' role in a specific [[Course| course]]. Being a 'Teacher' in one course does not give you any special privileges in another. For example, you must be specifically added to a course as a 'Teacher', or a 'Student', or be allowed in as a guest to have any access at all.

==Course creator==
In later versions of Moodle, the role of teacher has been further defined. There is now a role called "[[Course creator]]". This role can create a course, assign Teachers, plus have all the privileges of a Teacher.

==Non-editing teacher==
There is "non editing teacher" role that would be suitable for a student mentor or course adjuncts.

== See also ==
* [http://moodle.org/mod/forum/discuss.php?d=43024 Why "teacher" discussion]

[[Category: Roles]]

[[eu:Irakaslea]]
[[fr:Enseignant]]
[[it:Docente]]
[[ja:教師]]
[[zh:教师]]
[[de:Trainer-Rolle]]

learning objects

2008-10-12T08:27:22Z

Odoardo: /* What are learning objects? */

== What are learning objects? ==

The broadest definition of learning objects seems to be, "any digital resource that can be reused to support learning."

http://www.uwm.edu/Dept/CIE/AOP/LO_what.html

According to LOAZ, "There are many characteristics of learning objects, the common ones are: accessibility, interoperability, adaptability, reusability, durability, and granularity."

http://www.loaz.com/learning-objects/learning-object-characteristics.html

What role do learning objects play in Moodle? If we accept that any reusable, digital resource can be a learning object, almost any resource or activity we use in Moodle qualifies. After all, you can import and export resources and activities between courses pretty easily.

=== Creating Learning Objects with Moodle ===

Consider the book module. Perhaps you have created a Moodle book about the fall of the Berlin Wall for a history course you are teaching. If you permit a German instructor at your school to import that book into one of his or her courses, then your book has met the criteria of a learning object. It is digital, portable and reusable.

The same can be said of resources created with a glossary, a wiki, and other modules.

=== Uploading Learning Objects to Moodle ===

Is a PowerPoint presentation a learning object that we can upload and use in Moodle? It would seem so. The same can be said of a text document, an image, a self-contained web site, and any other digital teaching resource that you create. If it is reusable, it is probably a learning object. This would include the simplest annotated image and the most sophisticated interactive multimedia resource.

If you can upload a resource to your Moodle site and use it in more than one course, it is a learning object. Of course, if the learning object is already on the Web, you may choose to link to it. Think of a YouTube movie or a SlideShare presentation.

=== Additonal Learning Object Considerations ===

But what about metadata and SCORM? What about tracing student learning? And don't learning objects have to be housed in a searchable repository? These and other considerations are discussed by experts, but do not yet seem to have been resolved.

== See also ==

http://en.wikipedia.org/wiki/Learning_Objects

learning objects

2008-10-12T08:26:07Z

Odoardo: /* Uploading Learning Objects to Moodle */

== What are learning objects? ==

The broadest definition of learning objects seems to be, "any digital resource that can be reused to support learning."

http://www.uwm.edu/Dept/CIE/AOP/LO_what.html

Accoring to LOAZ, "There are many characteristics of learning objects, the common ones are: accessibility, interoperability, adaptability, reusability, durability, and granularity."

http://www.loaz.com/learning-objects/learning-object-characteristics.html

What role do learning objects play in Moodle? If we accept that any reusable, digital resource can be a learning object, almost any resource or activity we use in Moodle qualifies. After all, you can import and export resources and activities between courses pretty easily.

=== Creating Learning Objects with Moodle ===

Consider the book module. Perhaps you have created a Moodle book about the fall of the Berlin Wall for a history course you are teaching. If you permit a German instructor at your school to import that book into one of his or her courses, then your book has met the criteria of a learning object. It is digital, portable and reusable.

The same can be said of resources created with a glossary, a wiki, and other modules.

=== Uploading Learning Objects to Moodle ===

Is a PowerPoint presentation a learning object that we can upload and use in Moodle? It would seem so. The same can be said of a text document, an image, a self-contained web site, and any other digital teaching resource that you create. If it is reusable, it is probably a learning object. This would include the simplest annotated image and the most sophisticated interactive multimedia resource.

If you can upload a resource to your Moodle site and use it in more than one course, it is a learning object. Of course, if the learning object is already on the Web, you may choose to link to it. Think of a YouTube movie or a SlideShare presentation.

=== Additonal Learning Object Considerations ===

But what about metadata and SCORM? What about tracing student learning? And don't learning objects have to be housed in a searchable repository? These and other considerations are discussed by experts, but do not yet seem to have been resolved.

== See also ==

http://en.wikipedia.org/wiki/Learning_Objects