MoodleDocs - User contributions [en]

Admin presets block

2014-07-21T08:05:12Z

Davmon:

Allow users with the site configuration capability to export the site settings to .xml presets, import other sites .xml presets, load (totally or partially) presets settings and rollback the applied changes if necessary.

==Features==
* Export system settings to XML files
* Import presets files
* Preset preview and partial load
* Rollback applied changes
* Option to auto-exclude the sensitive data (like passwords) when exporting settings
* Editable sensitive setting list
* Third parties plugins supported (as long as they use the moodle core admin_setting classes)

==Installation==
* Download the latest version from the [https://moodle.org/plugins/view.php?plugin=block_admin_presets Modules and Plugins entry]
* Unzip and rename the folder from dmonllao-moodle-block_admin_presets-xxxxxxx to admin_presets
* Copy the admin_presets folder inside blocks/
* Login as an admin user and install as usual through the 'Notifications' like of the frontpage administration block
* Reconfigure the sensible settings if it's necessary

==See also==
* [https://moodle.org/plugins/view.php?plugin=block_admin_presets Modules and Plugins entry], where you can find more info about it
* [http://moodle.org/mod/forum/discuss.php?d=171536 Forum discussion]
* [http://tracker.moodle.org/browse/CONTRIB/component/10914 Tracker component], for bugs and other issues

[[Category:Contributed_code]]

Using Assignment

2014-03-13T02:40:57Z

Davmon: /* Annotating PDF files */

{{Assignment}}
<p class="note">'''Note''': This page is about using the new Assignment module in Moodle 2.3 onwards. For documentation on using Assignments (2.2), see [https://docs.moodle.org/22/en/Using_Assignment Using Assignment] in the 2.2 docs.</p>

==Different Submission options==

The standard assignment submission options available are:
* File submissions (students submit a file for assessment)
* Online text (students can type their responses directly in Moodle)
* Submission comments

''Note: It is also possible to use the assignment module for grading an "offline assignment", ie, one where work is done outside of Moodle. This is done by simply unchecking the above three options.''

==Which submission type suits you best?==

===You want students to type shorter or longer responses directly online===

*Set ''Online text'' to Yes. This works well for younger children who will only manage a sentence or two and works just as well for higher education students who write more.
**Advantage - quick for the student to get started; no need to use a word-processing program and upload the file.
**Disadvantage - potential worries that if the internet goes down, the work students have typed in and not yet saved might be lost. If the word count is expected to be large, setting ''Online text'' to No and ''File submission'' to Yes might be a better option.

===You want students to submit work you can download in a specified program===

*Set ''File submission'' to Yes, set the number of files you will allow using the ''Maximum number of uploaded files'' setting and the file sizes by using the '' Maximum submission size'' setting.
**Advantage - better than students emailing work as the whole class's work is collated in one space on your course. Markers can provide comments directly on the student work.
**Advantage - with "Attempts reopened" enabled, teachers can see the progression through various drafts of a student's work.
**Disadvantage - assignments must downloaded to be viewed (but they can be [[Assignment_FAQ| downloaded in bulk]]) and the teacher needs the appropriate program to open them.

===You want students to submit files at different times for a project===

*Set ''File submission'' to Yes, and use ''Maximum number of uploaded files'' to set the maximum number of separate files they can upload
**Advantage - all project files are in one assignment area for grading so they get a single grade.
**Disadvantage - all project files are in one assignment area for grading - so they can only have a single grade!

===You want students to write a response to a video/sound file/image===

*Set up an assignment allowing ''online text'' submission and get students to use the Moodle media icon to add video/sound/image files.

===You want students to answer a series of questions on a video/sound file/image===
*Investigate the [[Quiz]] module. Assignments are really just for a single question.

===You want to grade work students have done offline===
*Uncheck the submission types when setting up the assignment. Students won't be required to do anything but you can use the assignment to grade them for work done outside of Moodle.

===You want to view, comment on and send back students' assignments===

*Set up an assignment allowing ''file submissions''.
**Advantage: useful for teachers who like using the "comment" options in word-processing programs for example. If you have Ghostscript enabled on your server and the students upload PDF files, you can annotate them inline. See the section [[Using Assignment#Annotating PDF files| Annotating PDF files]] below.
**Disadvantage: if students upload other file types, you have to download them, comment and then re-upload them.

===You want students to send you a comment or note along with their uploaded work===

*In the settings, set ''Submission comments'' to Yes.

===You want to allow students to redraft and decide when to submit the work===

*In the settings set ''Require students click submit button'' to Yes. Students can then control when their draft work is submitted to the teacher.

===You want students to keep an ongoing journal or do an iterative assignment===

*In the settings set ''Require students click submit button'' to No. Students can continue to make changes to their assignment and at no point do they 'submit'. If the work will be graded at some point it is recommended that either ''Prevent late submissions'' is set to Yes to ensure that no changes can be made after the due date, or [[Using_Assignment#Submission_status| all submissions are locked]] when grading commences to ensure that the work is not altered during grading.
**Advantage: the work remains in one place and is constantly improved, graded (if needed) and improved again.
**Disadvantage: there is no record/history of previous attempts (such as with the [[Wiki]]). The online text assignment does not replicate the display of a journal or blog where each new entry is additional to the previous ones.

===You want students to submit work in groups===

*In the settings, set "Students submit in groups" to Yes. If you just do this, then once one student has submitted, the assignment will be flagged as submitted even if the others haven't contributed. If you want to ensure everyone has an input, set "Require students click submit button" to Yes and then change "Require all group members to submit" to Yes. The assignment will only be classed as submitted when each member has contributed, and once one student has submitted, the remaining members's names will be displayed for the group to see who still needs to add their input.

===You want to grade students' work anonymously===
*In the settings, choose "Blind marking". When students submit assignments, their names will be replaced by radomly generated participant numbers so you will not know who is who. Note that this is not '''totally'''''Italic text''
blind marking because you can reveal their identities in the assignment settings and you can work out identities from the logs - so this might not be suitable if your establishment has very precise privacy requirements.

===You want to read and grade student assignments offline===
*In the settings, choose "Offline grading worksheet". When students have submitted, click "View/grade all submissions" and you can download their assignments from the link "Download all submission" and download the grading sheet from the link "Download grading worksheet". You can then edit grades and re-upload the grading worksheet. You can also upload multiple feedback files in a zip from this drop down menu. See [[Assignment settings]] for an explanation of how to use the "upload multiple feedback files as zip" feature.
===You want to hide students' grades until a time of your choosing.===
Use 'marking workflow' as explained in [[Assignment settings]]

===You want to moderate other colleagues' marking or allocate certain teachers to certain students===
Use 'marking allocation' as explained in [[Assignment settings]]
==How do students submit their assignments?==
The first page students will see when they click on the assignment activity link from the course page will display the assignment name, description and the submission status. The first time a student views the assignment it will look like this:
{|
|[[Image:statuses.jpg|thumb|Student view of assignment]]
|}
The submission status section includes:
*'''Submission status'''
*'''Grading status'''
*Due date
*Time remaining
*Last modified
*Submission details

As they progress through the assignment the Submission status and Grading status will update and the Last modified date will appear.
{|
|[[Image:submission statuses graded.jpg|thumb|Example of submitted and graded assignment]]
|}

If the student uploaded a pdf file which the teacher has annotated, this will be made available in the feedback section. The student can search through the document and filter specific comments.
{|
|[[File:26pdfstudentgraded.png|thumb|Student view of graded pdf file]]
|[[File:26searchcomments.png|thumb|Searching and filtering comments in annotated pdf]]
|}
Submission statuses include:

*Nothing submitted for this assignment
*Draft (not submitted)
*Submitted for grading

Grading statuses include:

*Not graded
*Graded

===File submission===
To submit a file submission, students complete the following steps:
*Click the ‘Add submission’ button to bring up the file upload page.

*Upload the relevant file into the submission. They are able to ‘drag and drop’ the file into the submission box.
*Click ‘Save Changes’.
*There should now be a Last modified date and the file(s) uploaded will also be displayed.

*Depending on how the assignment is setup the status will either read ‘Submitted for grading’ - in which case no further action is need, or ‘Draft (not submitted)’.
*If changes are required, click on ‘Edit my submission’.
*Once ready to submit, click ‘Submit assignment’. Note that once the assignment is 'submitted’ no further changes are allowed.

{|
|[[File:file upload.jpg|thumb|Student view when adding a submission]]
|[[File:file uploaded.jpg|thumb|Student view once file is uploaded]]
|[[File:submit button.jpg|thumb|Student view when submitting assignment]]
|}
Note: Depending on how the assignment is setup students may see '''both''' a file submission page and an online text editor.

===Online text===
To submit online text, students complete the following steps:
*Click the ‘Add submission’ button to bring up the online text editor page

*Type the relevant text into the [[Text_editor|text editor]], or paste from a previously written file.
*Click ‘Save Changes’.
*There should now be a Last modified date and the first 100 characters entered will also be displayed.

*Depending on how the assignment is setup the status will either read ‘Submitted for grading’ - in which case no further action is need, or ‘Draft (not submitted)’
*If changes are required, click on ‘Edit my submission’.
*Once ready to submit, click ‘Submit assignment’. Note that once the assignment is 'submitted’ no further changes are allowed.

{|
|[[File:online text entered.jpg|thumb|Online text entered]]
|[[File:submit button online text.jpg|thumb|Sumbitting assignment]]
|}

===Submission comments===
Depending on how the assignment has been setup, there may be a section where students can leave submission comments.
{|
|[[Image:student comments.jpg|thumb|Student comments]]
|}

==Submission notifications==
Moodle allows the sending of a notification to the student when a student submits an assignment. This feature provides reassurance to the students that they have correctly submitted their assignments, especially when using features like draft submissions and file uploads. Moodle also allows notifications to teachers either when students submit assignments, or when students submit assignments late, or both. This feature notifies markers of the presence of assignments, or provides a reminder to access assignments submitted after the due date.

'''Why is this useful?'''
*Provides a receipt for student that the assignment has been successfully submitted
*Provides notification to marker that assignment are submitted
*Notifies of any changes to submission - for student’s record and to notify marker
*Provides notification to student that assignment feedback is available

'''When is it sent?'''

If ‘Require students to hit submit button’ is enabled within the assignment (formerly ‘enable send for marking button’ in 2.2), which requires students to click a final submit button and prevents further changes, only one notification will be sent upon hitting the submit button.

If ‘Require students to hit submit button’ is not enabled, and students are allowed to make alterations or add/remove files from their submission, this receipt will be sent every time the file is altered - ie once on adding the file, once on adding a second file, once on removal of file, once on uploading a new file.

'''Where are these settings?'''

Submission Notification for Grader - ''Assignment > Edit Settings''
The grader is given two options:
*Notify Graders about Submissions - YES/NO
*Notify Graders about Late Submissions - YES/NO

The first option will notify the grader on any/all submissions made. The second will only send a notification for assignments submitted after the ‘Due Date’.

The Late Submissions option will be greyed out unless ‘Notify Graders about Submissions’ is selected as NO because ‘Notify Graders about Submissions’ will also send receipts for assignments submitted after the due date. To fully disable the grader receiving notifications, change both options to NO.

Submission Notification for Students - ''My Profile Settings > Messaging''
Tickboxes on the messaging page can be set by the student depending on their preference. A student can opt to receive notification via email, popup message or both.

{|
|[[File:grader notifications.jpg|thumb|Grader notifications]]
|[[File:messaging settings.jpg|thumb|Student notifications]]
|}

Assignment notification - On submission of an assignment, the student will receive a notification that their assignment has been successfully received.

Essay graded notification - Once a grader has provided a mark/feedback for assignments, students will be notified (within the hour) that this feedback is available.

==Viewing and grading submitted assignments==
When students have submitted their assignments, they can be accessed by clicking on the assignment activity. This will bring up the Grading Summary page.

The Grading Summary page displays a summary of the assignment, including; number of participants, number of drafts, number of submitted assignments, due date and time remaining.

Clicking on the the ‘View/grade all submissions’ link will bring up the Grading Table.

The Grading Table contains columns of information about the student, the status of their submission, a link to grade their submission, a link to each submission and feedback comments and files (if enabled).

===Submission status===
If you will be assigning grades to student work, you may want to take note of the submission status before you begin the marking process. If you have required students click the Submit button, you may find that some submissions are still marked as Draft (not submitted), meaning the student has either uploaded a file(s) or entered some text, but has not clicked ‘Submit assignment’.

If it's after the due date and you are about to commencing marking that you use ‘Prevent submission changes’ to stop students from making changes to their assignment. You can do this one by one by using the icon in the Edit column.

Or you can select two or more students by putting a tick in the select column and going to 'Lock submissions’ from the ''With selected'' menu under the grading table.

Likewise you can also revert a student's submission to draft if they have uploaded the incorrect file. Instead of selecting ‘Prevent submission changes’ select ‘Revert the submission to draft’, or place ticks against selected students and choose 'Revert the submission to draft status' from the ''With selected'' menu under the grading table.

{|
|[[File:submission statuses.jpg|thumb|Submission statuses]]
|[[File:prevent submission changes dropdown.jpg|thumb|Prevent submission changes dropdown]]
|[[File:lock submissions.jpg|thumb|Lock submissions]]
|[[File:revert to draft.jpg|thumb|Revert to draft]]
|[[File:revert submission to draft status.jpg|thumb|Revert to draft status]]
|}

===Quick grading===
Under Options (scroll to bottom of the page) you can determine your preferences for the number of assignments you wish to display per page. You can also filter assignments either to show all (no filter), submitted, or requires grading. This is also where you can turn on '''quick grading'''.

'''Quick grading''' allows you to enter grades and a feedback comment (if enabled in [[Assignment settings]]) directly into the grading table. '''Quick grading''' is not compatible with advanced grading and is not recommended when there are multiple markers.

#You can enter grades and feedback comments using quick grading. '''It is now possible to enter grades in decimal format.''' You will not be able to return a feedback file to your students (if enabled in the [[Assignment settings]]).
#Enter the grades
#Scroll to the bottom of the grading table and click 'Save all quick grading changes'
#A confirmation screen will appear.

===Student grading page===
If you have enabled File Feedback in the [[Assignment settings]] and wish to upload either the marked student assignment, a completed text based feedback document or audio feedback, click on the green tick in the Grade column (or use the icon in the Edit column and select Grade).

Here you can enter grades, feedback comments and feedback files (if enabled in the [[Assignment settings]]). You can use drag and drop to upload feedback files.

{|
|[[File:green tick.jpg|thumb|Green tick]]
|[[File:grade.jpg|thumb|Grading]]
|[[File:feedbackfiles.png|thumb|Feedback files]]
|}

====Annotating PDF files====
{{New features}}
If the student has uploaded a PDF file you will see a link to Launch the PDF editor on the students' individual grading screen. This will display the PDF inline, allowing you to annotate it, using a variety of tools, stamps (if uploaded by the admin) and comments which may be saved to a comments bank. When the annotations are complete, clicking to save the changes will result in it being displayed to the student as part of their feedback. ''(Note that simply clicking on the file itself will not display it inline for annotating.)
''
{|
|[[File:26launchpdf.png|thumb|Teacher view when grading a pdf]]
|[[File:26annotatepdf.png|thumb|Annotating a pdf]]
|[[File:26pdfsavechanges.png|thumb|Make sure you save the changes]]
|}
Comments may be added and then saved in a quick list for future use. When adding a new comment, click the icon top right to access previously saved comments:
{|
|[[File:26commentquicklist.png|thumb|Saving and re-using comments]]
|}

Note: The annotate PDF feature requires Ghostscript to be installed on the server. https://docs.moodle.org/405/en/Upgrading#Ghostscript

===Downloading student submissions===
You can download a zip file containing all of the assignment submissions by selecting the ‘Download all submissions’ options from the ''Choose'' menu at the top of the grading table, or in the settings menu.

File submissions will be downloaded in the format uploaded by the student. Online text submissions will be downloaded as html files. '''Each file in the zip will include the student first and lastname at the beginning of the filename for identification purposes.'''

==Keeping records (archiving, exporting, backing up)==
When students unenrol from a Moodle area, their records become invisible through the Gradebook interface. In order to have the information to hand, departments or course teaching teams may need systems in place to keep their own records for the data retention period required in their particular context. There are two separate procedures for exporting student submissions and marks.

To export marks (with or without feedback):
#Go to your course area
#From its front page Settings block, select Grades; the Grader Report loads.
#From the Grader Report Settings block, select Export; a menu displays.
#From the menu, if you need easy viewing and running calculations you probably want to select one of the spreadsheet formats; a page of export settings loads
#Use the Visible Groups pulldown menu to limit the export to specific groups, as required
#In Options, you indicate whether feedback comments are included
#In Grade Items To Be Included lists you can, if required, omit particular Activities from the report
#When you've finished with the settings, click on Submit; a preview of your export displays
#Click on Download to export to the format you chose, and save the file.

To download the original student submissions:
#In your course area, click the link to the Assignment whose submissions you want to download.
#Click on the link to View/Grade all submissions; the Grading Table will load.
#Click the link to 'Download all submissions' (either from the ''Choose'' menu or from the Settings block), and save the file.

==Tips and Tricks==
* Want to use an Assignment activity again in another Moodle site? Use the [[Activity_backup| backup and restore]] options.
*Want to use an Assignment activity in another course you teach? Use the [[Import_course_data| Import function]] in the course administration block.
*Moodle will sometimes appear not to be uploading a resubmitted assignment - you seem to be downloading the original assignment. This is a cache issue, in short, go to ''"Tools > Clear Recent History"'' in Firefox or ''"Tools > Delete Browsing History > Delete Temporary Files"'' in Windows Explorer. The newer file will then appear.

==See also==

===Screencasts===
*[http://www.youtube.com/watch?v=2dcnTTp_W7c&feature=share&list=SPxcO_MFWQBDe8RRnGjoUDqbcm9PSlIoWn&index=3 Marking workflow and allocated markers.]
*[http://www.youtube.com/watch?v=MgsA-9qMBdY&feature=share&list=SPxcO_MFWQBDe8RRnGjoUDqbcm9PSlIoWn&index=1 Annotate PDFs]

===Examples from [http://school.demo.net School demo site]===

* [http://school.demo.moodle.net/mod/assign/view.php?id=1532&rownum=2&action=grade Teacher view of a PDF assignment which can be annotated inline.]Log in with username 'teacher' and password 'moodle'
* [http://school.demo.moodle.net/mod/assign/view.php?id=1532&action=grading Teacher view of allocated markers and marking workflow status.] Log in with username 'teacher' and password 'moodle'
* [http://school.demo.moodle.net/mod/assign/view.php?id=1456 Student view of an assignment.] Log in with username 'student' and password 'moodle'. Scroll down to see the rubric and feedback.
* [http://school.demo.moodle.net/mod/assign/view.php?id=1457&action=editsubmission Student view of a student submission statement] Log in with username 'student' and password 'moodle'
* [http://school.demo.moodle.net/mod/assign/view.php?id=1501 Student view of group assignment grading screen] Log in with username 'student' and password 'moodle'
* [http://schoolmaster.demo.moodle.net/mod/assign/view.php?id=1501 Teacher view of a group assignment grading screen] Log in with username 'teacher' and password 'moodle'.
* [http://school.demo.moodle.net/mod/assign/view.php?id=1500&action=grading Teacher view of blind marking grading screen] Log in with username 'teacher' and password 'moodle'

===Other===
* [http://www.somerandomthoughts.com/blog/2013/07/07/one-approach-for-group-project-grading/ One approach to group project grading] Blog post by Gavin Henrick.
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=201307Advantages of using Assignment upload over emailing a document] forum discussion

[[de:Aufgabe nutzen]]
[[fr:Afficher un devoir]]
[[ja:課題を表示する]]
[[es:Usando Tarea]]

Test course generator

2013-10-14T04:41:42Z

Davmon: /* CLI version */

(This in only available from 2.5.2+ (Build: 20131004) onwards)

If you want a large course for testing performance or reliability of a feature (where its behaviour might depend on the size of a course), you can generate standard-sized test courses using the generator tool.

== Requirements ==

This tool is for developer use only and should not be used on a live site. It is disabled unless you set the debugging option to DEVELOPER.

== Finding the generator tool ==

The tool is in the administration menu under Development / Make test course.

== Using the tool ==

To use the tool, select a size and type a shortname. The shortname should be one that is not in use. (If you type one that's in use, it will tell you.)

The tool shows an estimate of how large the created course will be and how long it will take to create. These are rough estimates.

* The 'M' course size (100 sections) is similar to a typical course at a large institution. This is useful for testing performance under normal conditions.
* The 'XL' course is very large and is suitable for testing reliability under extreme conditions.

=== Options ===
* Shortname: The course shortname (required)
* Size: The size of the generated site. Accepted values: XS, S, M, L, XL, or XXL (required)

== CLI version ==

You can run the tool from the command-line using:

php admin/tool/generator/cli/maketestcourse.php

This will show command-line options.

=== Options ===
Adding to the options mentioned above the CLI command has a few more.

* Use a fixed dataset: Use a fixed data set instead of randomly generated data, useful for generating a standard data set
* Specify a file size limit: Limits the size of the generated files to the specified number of bytes, you may find this setting useful because depending on the size you select the courses can use too much disk space
* By pass check: Bypasses the developer-mode check
* Quiet: Do not show any output

Test course generator

2013-10-14T04:40:58Z

Davmon: /* Using the tool */

JMeter test plan generator

2013-10-02T01:19:30Z

Davmon:

(This in only available from 2.5.2+ (Build: 20131004) onwards)

The JMeter test plan generator allows you to run performance tests over a Moodle course, it works along with https://github.com/moodlehq/moodle-performance-comparison, you can find more info about how to use it in https://github.com/moodlehq/moodle-performance-comparison/blob/master/README.md

== Requirements ==

This tool is for developer use only and should not be used on a live site. It is disabled unless you set the debugging option to DEVELOPER.

== Finding the generator tool ==

The tool can be found in:
* Web interface
** The Site Administration block -> Development -> Make JMeter test plan
* CLI
** admin/tool/generator/cli/maketestplan.php

== Usage ==

cd /moodle/dirroot
php admin/tool/generator/cli/maketestplan.php --size=S --shortname="course_short_name"

=== Options ===
* Course shortname: Shortname of the test plan's target course (required)
* Size: Size of the test plan to create XS, S, M, L, XL, or XXL options (required)
* By pass check: Bypasses the developer-mode check (be careful!)
* Update users password: Updates the target course users password

For more help:
php admin/tool/generator/cli/maketestplan.php --help

Test site generator

2013-10-02T01:19:23Z

Davmon:

(This in only available from 2.5.2+ (Build: 20131004) onwards)

The test site generator adds a set of courses, users and enrolments between them, in fact is using the [[Test course generator]] to generate the courses. It does not install a moodle site nor changes it's settings, only populates it. It's execution is not restricted to one, every time you run it new courses will be added.

__TOC__

== Requirements ==

This tool is for developer use only and should not be used on a live site. It is disabled unless you set the debugging option to DEVELOPER.

== Finding the generator tool ==

This tool is only available through CLI (command line interface)

== Usage ==

cd /moodle/dirroot
php admin/tool/generator/cli/maketestsite.php --size=S

=== Options ===
* Size: Size of the generated site, this value affects the number of courses and their size. Accepted values: XS, S, M, L, XL, or XXL (required)
* Use a fixed dataset: Use a fixed data set instead of randomly generated data, useful for generating a standard data set
* Specify a file size limit: Limits the size of the generated files to the specified number of bytes, you may find this setting useful because depending on the size you select the courses can use too much disk space
* By pass check: Bypasses the developer-mode check
* Quiet: Do not show any output

For more help:
php admin/tool/generator/cli/maketestsite.php --help

Development data generator

2013-10-02T01:18:05Z

Davmon:

The development data generator tool replaces the previous tool_generator (admin/tool/generator) in Moodle 2.6. It has also been backported (without removing the old one) to Moodle 2.5 as the current Moodle 2.5 tool_generator is not usable; it is available from 2.5.2+ (Build: 20131004) onwards.

It contains multiple features to help generate data for development or testing purposes.

# [[Test course generator]]
# [[Test site generator]]
# [[JMeter test plan generator]]

Test course generator

2013-10-02T01:17:10Z

Davmon:

JMeter test plan generator

2013-10-01T10:32:36Z

Davmon: Created page with "{{Work in progress}} The JMeter test plan generator allows you to run performance tests over a Moodle course, it works along with https://github.com/moodlehq/moodle-performan..."

{{Work in progress}}

The JMeter test plan generator allows you to run performance tests over a Moodle course, it works along with https://github.com/moodlehq/moodle-performance-comparison, you can find more info about how to use it in https://github.com/moodlehq/moodle-performance-comparison/blob/master/README.md

== Requirements ==

This tool is for developer use only and should not be used on a live site. It is disabled unless you set the debugging option to DEVELOPER.

== Finding the generator tool ==

The tool can be found in:
* Web interface
** The Site Administration block -> Development -> Make JMeter test plan
* CLI
** admin/tool/generator/cli/maketestplan.php

== Usage ==

cd /moodle/dirroot
php admin/tool/generator/cli/maketestplan.php --size=S --shortname="course_short_name"

=== Options ===
* Course shortname: Shortname of the test plan's target course (required)
* Size: Size of the test plan to create XS, S, M, L, XL, or XXL options (required)
* By pass check: Bypasses the developer-mode check (be careful!)
* Update users password: Updates the target course users password

For more help:
php admin/tool/generator/cli/maketestplan.php --help

Test site generator

2013-10-01T10:32:29Z

Davmon: Created page with "{{Work in progress}} The test site generator adds a set of courses, users and enrolments between them, in fact is using the Test course generator to generate the courses...."

{{Work in progress}}

The test site generator adds a set of courses, users and enrolments between them, in fact is using the [[Test course generator]] to generate the courses. It does not install a moodle site nor changes it's settings, only populates it. It's execution is not restricted to one, every time you run it new courses will be added.

__TOC__

== Requirements ==

This tool is for developer use only and should not be used on a live site. It is disabled unless you set the debugging option to DEVELOPER.

== Finding the generator tool ==

This tool is only available through CLI (command line interface)

== Usage ==

cd /moodle/dirroot
php admin/tool/generator/cli/maketestsite.php --size=S

=== Options ===
* Size: Size of the generated site, this value affects the number of courses and their size. Accepted values: XS, S, M, L, XL, or XXL (required)
* Use a fixed dataset: Use a fixed data set instead of randomly generated data, useful for generating a standard data set
* Specify a file size limit: Limits the size of the generated files to the specified number of bytes, you may find this setting useful because depending on the size you select the courses can use too much disk space
* By pass check: Bypasses the developer-mode check
* Quiet: Do not show any output

For more help:
php admin/tool/generator/cli/maketestsite.php --help

Test course generator

2013-10-01T10:32:17Z

Davmon: Created page with "{{Work in progress}} If you want a large course for testing performance or reliability of a feature (where its behaviour might depend on the size of a course), you can genera..."

{{Work in progress}}

If you want a large course for testing performance or reliability of a feature (where its behaviour might depend on the size of a course), you can generate standard-sized test courses using the generator tool.

== Requirements ==

This tool is for developer use only and should not be used on a live site. It is disabled unless you set the debugging option to DEVELOPER.

== Finding the generator tool ==

The tool is in the administration menu under Development / Make test course.

== Using the tool ==

To use the tool, select a size and type a shortname. The shortname should be one that is not in use. (If you type one that's in use, it will tell you.)

The tool shows an estimate of how large the created course will be and how long it will take to create. These are rough estimates.

* The 'M' course size (100 sections) is similar to a typical course at a large institution. This is useful for testing performance under normal conditions.
* The 'XL' course is very large and is suitable for testing reliability under extreme conditions.

== CLI version ==

You can run the tool from the command-line using:

php admin/tool/generator/cli/maketestcourse.php

This will show command-line options.

Development data generator

2013-10-01T10:31:23Z

Davmon: Created page with "The development data generator tool replaces the previous tool_generator (admin/tool/generator) in Moodle 2.6. It has also been backported (without removing the old one) to Mo..."

The development data generator tool replaces the previous tool_generator (admin/tool/generator) in Moodle 2.6. It has also been backported (without removing the old one) to Moodle 2.5 as the current Moodle 2.5 tool_generator is not usable.

It contains multiple features to help generate data for development or testing purposes.

# [[Test course generator]]
# [[Test site generator]]
# [[JMeter test plan generator]]

IMS Enterprise

2013-05-27T05:53:44Z

Davmon: /* Basic guide to IMS Enterprise file format */

{{Enrolment}}
Location: IMS Enterprise file edit settings link in ''Site administration > Plugins > Enrolments > Manage enrol plugins''

'''IMS Enterprise''' is an international standard XML file format which may be used to specify enrolments/unenrolments in courses, as well as course information and user information.

==Format overview==

Below is a simple guide to the basic structure of a typical IMS Enterprise data file. Much more information is available on the [http://www.imsglobal.org/enterprise/ IMS Enterprise official website].

You may like to read the [https://github.com/moodle/moodle/blob/master/enrol/imsenterprise/entv1p1_conformance_summary.html conformance summary] which describes which IMS data elements this plugin can process.

==Basic guide to IMS Enterprise file format==

For any IMS-style enrolment you need a <group> tag which specifies the course, a <person> tag which specifies the user account, and a <membership> tag containing <member> tags which specify a person's role within a given course.

Remember that the numeric keys used in the Moodle databases are not the interoperable data - a student data system is never going to know in advance that Joe is the 20th user added to the Moodle database - so those aren't the keys exchanged in this type of data.

Typically a course would have a reference code as well as a name, so let's assume its code is MOODLE101. If you require a new course to be placed in a category other than the default, you can specify that using the <orgunit> tag. To define your course you could use

<group>
<sourcedid>
<source>MyDataSystem</source>
<id>MOODLE101</id>
</sourcedid>
<description>
<short>Moodle 101</short>
<long>Moodle 101: Course Name</long>
</description>
<org>
<orgunit>CATEGORY</orgunit>
</org>
</group>

The enrolment script will look for a course with code MOODLE101, and (optionally) create it if it doesn't exist, the plugin also allows you to map between group tags and the course shortname, fullname and summary fields. Similarly for the person - let's assume it's "jmoodle":

<person>
<sourcedid>
<source>MyDataSystem</source>
<id>jmoodle</id>
</sourcedid>
<userid>jmoodle</userid>
<name>
<fn>Joe Moodle</fn>
<n>
<family>MOODLE</family>
<given>JOE</given>
</n>
</name>
</person>

If Joe doesn't already have an account, the script can (optionally) create an account for him.

Let's now look at the membership, adding the person to the course:

<membership>
<sourcedid>
<source>MyDataSystem</source>
<id>MOODLE101</id>
</sourcedid>
<member>
<sourcedid>
<source>MyDataSystem</source>
<id>jmoodle</id>
</sourcedid>
<role roletype="01">
<status>1</status>
<extension><cohort>unit 2</cohort></extension>
</role>
</member>
</membership>

The IMS Enterprise specification does offer a facility for specifying start/end dates for enrolments, so those can be included using the <timeframe> tag if needed.

If a person is already added to a group within the course, the script won't actually modify that. If they are not grouped, however, then the specified grouping will be applied.

==Automatic creation of new courses==

If required, the IMS Enterprise enrolment plugin can create new courses for any it finds in the IMS data but not in Moodle's database.

Courses are first queried by their "idnumber" - an alphanumeric field in Moodle's course table, which can specify the code used to identify the course in the Student Information System (for example). If that is not found, the course table is searched for the "short description", which in Moodle is the short course identifier as displayed in the breadcrumbs etc. (In some systems these two fields may well be identical.) Only when that search has failed can the plugin optionally create new courses.

Any newly-generated courses are HIDDEN when created. This is to prevent the possibility of students wandering into completely empty courses that the teacher may be unaware of.

==Unenrolling students/teachers==

If required, the Enterprise data can add as well as remove course enrolments - for students and for teachers. If this setting is turned on, then Moodle will carry out unenrolments when specified in the data. Note, as of Moodle 2, you must use IMSEnterprise to remove members that have been added by the plugin. You cannot manually delete a member.

There are three ways of unenrolling students within the IMS data:

* A <member> element which specifies the given student and course, and with the "recstatus" attribute of the <role> element set to 3 (which means "delete"). THIS IS NOT YET IMPLEMENTED IN THE MOODLE PLUGIN.
* A <member> element which specifies the given student and course, and with the <status> element set to 0 (which means "inactive").

The third method is slightly different. It does not require this config setting to be activated, and can be specified well in advance of the unenrolment date:

* A <member> element which specifies a <timeframe> for the enrolment can specify the begin and/or end dates for enrolment of this particular student. These dates are loaded into Moodle's enrolment data table if present, and so after the end-date, a student will no longer be able to access that particular course.

==See also==

* [http://www.imsglobal.org/enterprise/ IMS Enterprise specification] - the official site
* [http://cvs.moodle.org/contrib/plugins/enrol/imsenterprise/entv1p1_conformance_summary.html?view=co Conformance summary] - summarises the parts of the specification which Moodle makes use of
* [https://studydirect.sussex.ac.uk/downloads/imsenterprise.php Minted IMS Enterprise enrolment plugin] - An extension of the ims enterprise enrolment plugin developed in the [http://www.sussex.ac.uk/minted minted project]

[[fr:Fichier IMS Enterprise]]
[[de:Einschreibung über IMS Enterprise Datei]]

IMS Enterprise

2012-07-18T09:14:43Z

Davmon: /* Basic guide to IMS Enterprise file format */

{{Enrolment}}
Location: IMS Enterprise file edit settings link in ''Site administration > Plugins > Enrolments > Manage enrol plugins''

'''IMS Enterprise''' is an international standard XML file format which may be used to specify enrolments/unenrolments in courses, as well as course information and user information.

==Format overview==

Below is a simple guide to the basic structure of a typical IMS Enterprise data file. Much more information is available on the [http://www.imsglobal.org/enterprise/ IMS Enterprise official website].

You may like to read the [http://cvs.moodle.org/contrib/plugins/enrol/imsenterprise/entv1p1_conformance_summary.html?view=co conformance summary] which describes which IMS data elements this plugin can process.

==Basic guide to IMS Enterprise file format==

For any IMS-style enrolment you need a <group> tag which specifies the course, a <person> tag which specifies the user account, and a <membership> tag containing <member> tags which specify a person's role within a given course.

Remember that the numeric keys used in the Moodle databases are not the interoperable data - a student data system is never going to know in advance that Joe is the 20th user added to the Moodle database - so those aren't the keys exchanged in this type of data.

Typically a course would have a reference code as well as a name, so let's assume its code is MOODLE101. If you require a new course to be placed in a category other than the default, you can specify that using the <orgunit> tag. To define your course you could use

<group>
<sourcedid>
<source>MyDataSystem</source>
<id>MOODLE101</id>
</sourcedid>
<description>
<short>Moodle 101</short>
<long>Moodle 101: Course Name</long>
</description>
<org>
<orgunit>CATEGORY</orgunit>
</org>
</group>

The enrolment script will look for a course with code MOODLE101, and (optionally) create it if it doesn't exist. Similarly for the person - let's assume it's "jmoodle":

<person>
<sourcedid>
<source>MyDataSystem</source>
<id>jmoodle</id>
</sourcedid>
<userid>jmoodle</userid>
<name>
<fn>Joe Moodle</fn>
<n>
<family>MOODLE</family>
<given>JOE</given>
</n>
</name>
</person>

If Joe doesn't already have an account, the script can (optionally) create an account for him.

Let's now look at the membership, adding the person to the course:

<membership>
<sourcedid>
<source>MyDataSystem</source>
<id>MOODLE101</id>
</sourcedid>
<member>
<sourcedid>
<source>MyDataSystem</source>
<id>jmoodle</id>
</sourcedid>
<role roletype="01">
<status>1</status>
<extension><cohort>unit 2</cohort></extension>
</role>
</member>
</membership>

The IMS Enterprise specification does offer a facility for specifying start/end dates for enrolments, so those can be included using the <timeframe> tag if needed.

If a person is already added to a group within the course, the script won't actually modify that. If they are not grouped, however, then the specified grouping will be applied.

==Automatic creation of new courses==

If required, the IMS Enterprise enrolment plugin can create new courses for any it finds in the IMS data but not in Moodle's database.

Courses are first queried by their "idnumber" - an alphanumeric field in Moodle's course table, which can specify the code used to identify the course in the Student Information System (for example). If that is not found, the course table is searched for the "short description", which in Moodle is the short course identifier as displayed in the breadcrumbs etc. (In some systems these two fields may well be identical.) Only when that search has failed can the plugin optionally create new courses.

Any newly-generated courses are HIDDEN when created. This is to prevent the possibility of students wandering into completely empty courses that the teacher may be unaware of.

==Unenrolling students/teachers==

If required, the Enterprise data can add as well as remove course enrolments - for students and for teachers. If this setting is turned on, then Moodle will carry out unenrolments when specified in the data. Note, as of Moodle 2, you must use IMSEnterprise to remove members that have been added by the plugin. You cannot manually delete a member.

There are three ways of unenrolling students within the IMS data:

* A <member> element which specifies the given student and course, and with the "recstatus" attribute of the <role> element set to 3 (which means "delete"). THIS IS NOT YET IMPLEMENTED IN THE MOODLE PLUGIN.
* A <member> element which specifies the given student and course, and with the <status> element set to 0 (which means "inactive").

The third method is slightly different. It does not require this config setting to be activated, and can be specified well in advance of the unenrolment date:

* A <member> element which specifies a <timeframe> for the enrolment can specify the begin and/or end dates for enrolment of this particular student. These dates are loaded into Moodle's enrolment data table if present, and so after the end-date, a student will no longer be able to access that particular course.

==See also==

* [http://www.imsglobal.org/enterprise/ IMS Enterprise specification] - the official site
* [http://cvs.moodle.org/contrib/plugins/enrol/imsenterprise/entv1p1_conformance_summary.html?view=co Conformance summary] - summarises the parts of the specification which Moodle makes use of
* [https://studydirect.sussex.ac.uk/downloads/imsenterprise.php Minted IMS Enterprise enrolment plugin] - An extension of the ims enterprise enrolment plugin developed in the [http://www.sussex.ac.uk/minted minted project]

[[fr:Fichier IMS Enterprise]]
[[de:Einschreibung über IMS Enterprise Datei]]

Journal module

2012-04-19T15:05:31Z

Davmon:

The Journal Module has been disabled during install by default since Moodle 1.5 (when all Journals were converted to Online Assignments)

NOTE: From Moodle 2.0 you will no longer find the Journal module installed by default as part of your CVS version of Moodle. You'll need to install it separately from contrib.
see [http://moodle.org/mod/forum/discuss.php?d=96337]
and [http://moodle.org/mod/forum/discuss.php?d=96334]

In order to avoid data loss, the installation of the journal plugin on a Moodle 2.0 should follow the [https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0#A_word_about_optional_plugins_and_themes Upgrading to Moodle 2.0 guidelines]. [http://moodle.org/mod/forum/discuss.php?d=154910 That discussion] about the best way to upgrade contrib plugins to Moodle 2.0 could also be useful.

==See also==
*[http://moodle.org/plugins/view.php?plugin=mod_journal Journal module for download]
*Using Moodle [http://moodle.org/mod/forum/view.php?id=736 Journal module forum]

[[Category:Contributed code]]

Journal module

2012-03-15T09:16:48Z

Davmon:

The Journal Module has been disabled during install by default since Moodle 1.5 (when all Journals were converted to Online Assignments)

NOTE: From Moodle 2.0 you will no longer find the Journal module installed by default as part of your CVS version of Moodle. You'll need to install it separately from contrib.
see [http://moodle.org/mod/forum/discuss.php?d=96337]
and [http://moodle.org/mod/forum/discuss.php?d=96334]

In order to avoid data loss, the installation of the journal plugin on a Moodle 2.0 should follow the [https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0#A_word_about_optional_plugins_and_themes Upgrading to Moodle 2.0 guidelines]. [http://moodle.org/mod/forum/discuss.php?d=154910 That discussion] about the best way to upgrade contrib plugins to Moodle 2.0 could also be useful.

==See also==
*[http://moodle.org/mod/data/view.php?d=13&rid=325 Journal module for download]
*Using Moodle [http://moodle.org/mod/forum/view.php?id=736 Journal module forum]

[[Category:Contributed code]]

Development:Moodle flavours

2011-05-09T07:26:30Z

Davmon:

{{Infobox Project
|name = Moodle flavours
|state = Planning
|tracker =
|discussion = http://moodle.org/mod/forum/discuss.php?d=174755
|assignee = David Monllaó
}}

''Project specification coming soon...''

==Introduction==

A ''flavour'' is a packaged set of Moodle site settings, plugins and language packs. Moodle Administrators will be able to create a flavour from their installation, selecting which settings, plugins and language packs will be packaged into a compressed file. They can then, share the package with the Moodle community, store it as a backup or use it to replicate the flavour to other installations they manages. It could also be useful for administrators with little Moodle experienced, allowing them to explore the Moodle settings and setup recommended by others.

==Examples==
* Flavours for universities with common language packs, videoconferencing plugins and the secure quiz settings
* Flavours for schools with plugins more oriented towards children
* Sets of audio plugins for music teaching
* Local language customisations for Italian (for example) and Romanic language packs, for languages teaching
* Packs of admin monitoring / reporting plugins

==GSOC Original Proposal==

===Short description===
This project will bring flavours to Moodle, allowing Administrators to choose and load a flavour from a public repository. Flavours can contain administration settings, Moodle plugins, sub-plugins, language packs and local language strings. The repository management could be done with a database module instance on moodle.org or through the Modules and Plugins databse, although, this project will focus on the development of the flavour packaging and deployment system.

===Long description===
There are a lot of Moodle settings, plugins and integrations with other applications. It's fun to explore Moodle options, but not everyone has time to achieve this.

Based on [http://en.wikipedia.org/wiki/AppFuse Appfuse] nomenclature, a flavour will be a Moodle package of administration settings, installed plugins, languages and the local customisations. Flavours will be distributed using a database (like the M&P or themes dbs) on moodle.org where flavour contributors can share, describe, comment or rate the submitted flavours.

Flavours will be distributed as compressed files, with a .xml file to structure the flavour contents. The packaging system should respect the moodle and moodledata directory structure.

To ''deploy'' a flavour, the user interface will be similar to the courses backup and restore interface, which should be familiar to Administrators. During deployment, administrators will be able to selectively nominate the flavour contents that will be used.

Another consideration will be versioning; there will need to be control over configuration, plugin and language pack versions to avoid incompatibilities between releases.

Development:Moodle flavours

2011-05-01T09:39:25Z

Davmon:

{{Infobox Project
|name = Moodle flavours
|state = Planning
|tracker =
|discussion =
|assignee = David Monllaó
}}

''Project specification coming soon...''

==Introduction==

A flavour it's a set of moodle site settings, plugins and language packs. Moodle admins could create flavours from his installation, selecting which settings, plugins and language packs should be packaged into a compressed file and then, share the package with the Moodle community, store it as a backup or use it to replicate the same to other installations he/she manages. It could also be useful for administrators not very experienced with Moodle which don't have enough time to explore all the Moodle settings: they can install the latest Moodle release, look for a flavour which matches his needs and import it.

==Examples==
* Flavours for universities with the most "common" language packs, videoconferencing plugins and the quiz settings with "secure" values
* Flavours for schools with plugins more oriented to children
* Sets of audio plugins for music teaching
* Local language customizations for Italian (for example) and Romanic language packs, for languages teaching
* Packs of admin monitoring / reporting plugins

==GSOC Original Proposal==

===Short description===
This project purpose is to bring Moodle different flavours, allowing administrators to choose and load a flavour from a public repository. Every flavour could contain administration settings, Moodle plugins, sub-plugins, language packs and local language strings. The repository management could be done with a database module instance, that's not the project, the development to do is the flavour packaging and deployment system.

===Long description===
There are a lot of Moodle settings, plugins and integrations with other applications, it's fun to explore all that options, but not everybody has enough time to do it.

To complete the short description and leaving apart the appfuse nomenclature, it is a Moodle packaging/deployment system for administration settings, installed plugins, languages and the local customizations (the recent subplugins and the local language strings) That project will not be useful without a database (like the M&P or themes dbs) on moodle.org to share, describe, comment or rate the submitted flavours.

The flavours should be distributed as compressed files, with a .xml file to structure the flavour contents. The packaging system should respect the moodle and moodledata directory structure.

On the deployment side, the user interface can be similar to the courses backup and restore M2.0 steps to familiarized users and to specify which flavour contents will be added. Another important point is the versioning, there should be a control of the settings, plugins and language packs versions to avoid incoherences between incompatible releases.

I'm not sure about the nomenclature, packaging/deployment, export/import, backup/restore...

Development:Moodle flavours

2011-05-01T09:37:27Z

Davmon:

{{Infobox Project
|name = Moodle flavours
|state = Planning
|tracker =
|discussion =
|assignee = David Monllaó
}}

''Project specification coming soon...''

==Introduction==

A flavour it's a set of moodle site settings, plugins and language packs. Moodle admins could create flavours from his installation, selecting which settings, plugins and language packs should be packaged into a compressed file and then, share the package with the Moodle community, store it as a backup or use it to replicate the same to other installations he/she manages. It could also be useful for administrators not very experienced with Moodle which haven't enough time to explore all the Moodle settings: they can install the latest Moodle release, look for a flavour which matches his needs and import it.

==Examples==
* Flavours for universities with the most "common" language packs, videoconferencing plugins and the quiz settings with "secure" values
* Flavours for schools with plugins more oriented to children
* Sets of audio plugins for music teaching
* Local language customizations for Italian (for example) and Romanic language packs, for languages teaching
* Packs of admin monitoring / reporting plugins

==GSOC Original Proposal==

===Short description===
This project purpose is to bring Moodle different flavours, allowing administrators to choose and load a flavour from a public repository. Every flavour could contain administration settings, Moodle plugins, sub-plugins, language packs and local language strings. The repository management could be done with a database module instance, that's not the project, the development to do is the flavour packaging and deployment system.

===Long description===
There are a lot of Moodle settings, plugins and integrations with other applications, it's fun to explore all that options, but not everybody has enough time to do it.

To complete the short description and leaving apart the appfuse nomenclature, it is a Moodle packaging/deployment system for administration settings, installed plugins, languages and the local customizations (the recent subplugins and the local language strings) That project will not be useful without a database (like the M&P or themes dbs) on moodle.org to share, describe, comment or rate the submitted flavours.

The flavours should be distributed as compressed files, with a .xml file to structure the flavour contents. The packaging system should respect the moodle and moodledata directory structure.

On the deployment side, the user interface can be similar to the courses backup and restore M2.0 steps to familiarized users and to specify which flavour contents will be added. Another important point is the versioning, there should be a control of the settings, plugins and language packs versions to avoid incoherences between incompatible releases.

I'm not sure about the nomenclature, packaging/deployment, export/import, backup/restore...

Development:Moodle flavours

2011-05-01T08:12:36Z

Davmon:

Admin presets block

2011-03-22T08:16:28Z

Davmon:

Allow users with the site configuration capability to export the site settings to .xml presets, import other sites .xml presets, load (totally or partially) presets settings and rollback the applied changes if necessary.

==Features==
* Export system settings to XML files
* Import presets files
* Preset preview and partial load
* Rollback applied changes
* Option to auto-exclude the sensible data (like passwords) when exporting settings
* Editable sensible setting list
* Third parties plugins supported (as long as they use the moodle core admin_setting classes)

==Installation==
* Download the latest version from the [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry]
* Unzip and rename the folder from dmonllao-moodle-block_admin_presets-xxxxxxx to admin_presets
* Copy the admin_presets folder inside blocks/
* Login as an admin user and install as usual through the 'Notifications' like of the frontpage administration block
* Reconfigure the sensible settings if it's necessary

==See also==
* [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry], where you can find more info about it
* [http://moodle.org/mod/forum/discuss.php?d=171536 Forum discussion]
* [http://tracker.moodle.org/browse/CONTRIB/component/10914 Tracker component], for bugs and other issues

[[Category:Contributed_code]]

Admin presets block

2011-03-22T08:12:59Z

Davmon: New page: Allow users with the site configuration capability to export the site settings to .xml presets, import other sites .xml presets, load (totally or partially) presets settings and rollback t...

Allow users with the site configuration capability to export the site settings to .xml presets, import other sites .xml presets, load (totally or partially) presets settings and rollback the applied changes if necessary.

==Features==
* Export system settings to XML files
* Import presets files
* Preset preview and partial load
* Rollback applied changes
* Option to auto-exclude the sensible data (like passwords) when exporting settings
* Editable sensible setting list
* Third parties plugins supported (as long as they use the moodle core admin_setting classes)

==Installation==
* Download the latest version from the [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry]
* Unzip and rename the folder from dmonllao-moodle-block_admin_presets-xxxxxxx to admin_presets
* Copy the admin_presets folder inside blocks/
* Login as an admin user and install as usual through the 'Notifications' like of the frontpage administration block
* Reconfigure the sensible settings if it's necessary

==See also==
* [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry], where you can find more info about it
* [http://moodle.org/mod/forum/discuss.php?d=171536 Forum discussion]
* [http://tracker.moodle.org/browse/CONTRIB/component/10914 Tracker component], for bugs and other issues

Monitoraccesses report

2011-01-31T22:09:10Z

Davmon:

Admin report to check which users are logged into moodle between defined time ranges.

It counts the time each selected user has passed connected to Moodle between the selected ranges, if the user didn't logout it considers the (login + session timeout) as logout time.

==Features==
Allows users (new capability defined report/monitoraccesses:view, available to admins by default) to
monitor accesses of the selected users from the selected courses between the selected
time ranges (until 3) and the selected days of the year.

* Selection of courses and users
* Filter by time and date/s and/or month/s

==Installation==
Following the [https://docs.moodle.org/en/Installing_contributed_modules_or_plugins Installing contributed code documentation]:
* Copy the monitoraccesses/ folder into the folder admin/report
* Logged as an admin user click 'Notifications' on the frontpage administration block
* Redefine the default capability if necessary

==See also==
*[https://github.com/dmonllao/moodle-report_monitoraccesses Repository link]

[[Category:Contributed_code]]

Monitoraccesses report

2011-01-31T22:04:36Z

Davmon: /* Installation */

Monitoraccesses report

2011-01-31T22:03:56Z

Davmon: New page: Admin report to check which users are logged into moodle between defined time ranges. It counts the time each selected user has passed connected to Moodle between the selected ranges, if ...

Admin report to check which users are logged into moodle between defined time ranges.

It counts the time each selected user has passed connected to Moodle between the selected ranges, if the user didn't logout it considers the (login + session timeout) as logout time.

==Features==
Allows users (new capability defined report/monitoraccesses:view, available to admins by default) to
monitor accesses of the selected users from the selected courses between the selected
time ranges (until 3) and the selected days of the year.

* Selection of courses and users
* Filter by time and date/s and/or month/s

==Installation==
Following the [https://docs.moodle.org/en/Installing_contributed_modules_or_plugins Install contributed code docs]:
* Copy the monitoraccesses/ folder into the folder admin/report
* Logged as an admin user click 'Notifications' on the frontpage administration block
* Redefine the default capability if necessary

==See also==
*[https://github.com/dmonllao/moodle-report_monitoraccesses Repository link]

Journal module

2011-01-31T17:59:09Z

Davmon:

The Journal Module has been disabled during install by default since Moodle 1.5 (when all Journals were converted to Online Assignments)

NOTE: From Moodle 2.0 you will no longer find the Journal module installed by default as part of your CVS version of Moodle. You'll need to install it separately from contrib.
see [http://moodle.org/mod/forum/discuss.php?d=96337]
and [http://moodle.org/mod/forum/discuss.php?d=96334]

In order to avoid data loss, the installation of the journal plugin on a Moodle 2.0 should follow the [https://docs.moodle.org/en/Upgrading_to_Moodle_2.0#A_word_about_optional_plugins_and_themes Upgrading to Moodle 2.0 guidelines]. [http://moodle.org/mod/forum/discuss.php?d=154910 That discussion] about the best way to upgrade contrib plugins to Moodle 2.0 could also be useful.

==See also==
*[http://moodle.org/mod/data/view.php?d=13&rid=325 Journal module for download]
*Using Moodle [http://moodle.org/mod/forum/view.php?id=736 Journal module forum]

[[Category:Contributed code]]

Adobe Connect block

2010-04-09T08:14:15Z

Davmon: /* Features */

The Adobe Connect block is contributed code that provides single sign on (SSO) with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users. As web conferencing software, Adobe Connect has audio/video, screen sharing, text chat and conferencing tools.

==Features==

Simple one-way synchronization from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.

There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.

The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.

The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.

For a more suitable integration with Adobe Connect see Adobe Connect module by Remote Learner:

[http://moodle.org/mod/data/view.php?d=13&rid=3599 Adobe Connect module by Remote Learner modules and plugins page]

[https://docs.moodle.org/en/Remote_learner_adobe_connect_pro Adobe Connect module by Remote Learner Moodle Docs page]

==Usage==
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.

==Requirements==
* Adobe Connect Server, version >= 6
* PHP Curl library installed
* Optional but highly recommended, Adobe Connect application server with SSL

==Installation==
* Copy to Moodle blocks/ folder
* Click "Notifications" link, on frontpage admin settings tree
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role

==Other information==
* Supported languages: English, Español and Català
* Moodle supported versions: 1.9 and 1.9.x

==See also==
* [http://moodle.org/mod/data/view.php?d=13&rid=3594 Adobe Connect Block in Modules and Plugins Database]
* [http://download.moodle.org/download.php/plugins19/blocks/adobeconnect.zip Download for Moodle 1.9]
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]
*[[Remote learner adobe connect pro]] - a contributed code activity module

[[Category:Contributed_code]]

Adobe Connect block

2010-03-18T13:10:21Z

Davmon:

The Adobe Connect block is contributed code that provides single sign on (SSO) with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users. As web conferencing software, Adobe Connect has audio/video, screen sharing, text chat and conferencing tools.

==Features==

Simple one-way synchronization from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.

There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.

The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.

The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.

For a more suitable integration with Adobe Connect see [[Remote learner adobe connect pro]]

==Usage==
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.

==Requirements==
* Adobe Connect Server, version >= 6
* PHP Curl library installed
* Optional but highly recommended, Adobe Connect application server with SSL

==Installation==
* Copy to Moodle blocks/ folder
* Click "Notifications" link, on frontpage admin settings tree
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role

==Other information==
* Supported languages: English, Español and Català
* Moodle supported versions: 1.9 and 1.9.x

==See also==
* [http://moodle.org/mod/data/view.php?d=13&rid=3594 Adobe Connect Block in Modules and Plugins Database]
* [http://download.moodle.org/download.php/plugins19/blocks/adobeconnect.zip Download for Moodle 1.9]
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]
*[[Remote learner adobe connect pro]] - a contributed code activity module

[[Category:Contributed_code]]

Adobe Connect block

2010-03-03T08:17:33Z

Davmon: /* See also */

Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users.

==Features==

One-way synchronization, from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.

There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.

The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.

The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.

==Usage==
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.

==Requirements==
* Adobe Connect Server, version >= 6
* PHP Curl library installed
* Optional but highly recommended, Adobe Connect application server with SSL

==Installation==
* Copy to Moodle blocks/ folder
* Click "Notifications" link, on frontpage admin settings tree
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role

==Other information==
* Supported languages: English, Español and Català
* Moodle supported versions: 1.9 and 1.9.x

==See also==
* [http://moodle.org/mod/data/view.php?d=13&rid=3594 Adobe Connect Block in Modules and Plugins Database]
* [http://download.moodle.org/download.php/plugins19/blocks/adobeconnect.zip Download for Moodle 1.9]
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]

[[Category:Contributed_code]]

Adobe Connect block

2010-03-03T07:52:09Z

Davmon:

Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users.

==Features==

One-way synchronization, from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.

There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.

The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.

The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.

==Usage==
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.

==Requirements==
* Adobe Connect Server, version >= 6
* PHP Curl library installed
* Optional but highly recommended, Adobe Connect application server with SSL

==Installation==
* Copy to Moodle blocks/ folder
* Click "Notifications" link, on frontpage admin settings tree
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role

==Other information==
* Supported languages: English, Español and Català
* Moodle supported versions: 1.9 and 1.9.x

==See also==
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]

[[Category:Contributed_code]]

Adobe Connect block

2010-03-03T07:50:57Z

Davmon: New page: Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users. ==Features== One-way synchronization, from Moodle to Adobe Connect...

Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users.

==Features==

One-way synchronization, from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.

There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.

The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.

The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.

==Usage==
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.

==Requirements==
* Adobe Connect Server, version >= 6
* PHP Curl library installed
* Optional but highly recommended, Adobe Connect application server with SSL

==Installation==
* Copy to Moodle blocks/ folder
* Click "Notifications" link, on frontpage admin settings tree
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role

==Other information==
* Supported languages: English, Español and Català
* Moodle supported versions: 1.9 and 1.9.x

==See also==
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]

[[Category:Contributed_code]]