Access Keys:
Skip to content (Access Key - 0)

Blocks Manual

The most recent documentation for Moodle/Joule 2 has moved.

Please go to http://kb.moodlerooms.com to view the New Knowledge Base.

Table of Contents

1. Campus Vue

1.1. Overview

The Campus Vue block works by sending grade and attendance data from Joule to Campus Vue. The block allows an administrator to configure the SFTP connection to Campus Vue along with the attendance weighting used within Joule. For more information about the initial integration download our Configuration Package by clicking here.

1.1.1. Related Features

1.2. Administrator Documentation

The campus Vue Integration block is mostly used to perform automated tasks in the background. Every 60 minutes the block determines what submitted grades and attendance logs haven't been sent to the Campus Vue server. It then generates a file for grades and attendance records and sends these files to the Campus Vue server for processing via SFTP.

The Campus Vue Integration block also allows an administrator to perform the following tasks:

  • Download a CSV file to resubmit grades from the grade submission block to the Campus Vue server for a course or user.
  • Configure attendance weighting for the site.
  • Download a CSV file to resubmit attendance for one more courses and/or users to the Campus Vue Server.

In order to do any of the following the Campus Vue Integration block must first be added at the site level.

Campus vue integration block installed on a site with the links to resubmit grades

Once added each of the links will allow you got perform one of the actions above. Each of these is described blow.

1.2.1. Resubmit Grades

Grade resubmission is a manual process performed by a Joule and Campus Vue administrator. The Campus Vue Integration block provides an administrator with a way to download comma separated value (.csv) files that can then be uploaded to the Campus Vue server for processing.

When first viewing the report a user will see a list of all of the grades that have been submitted for all classes, this is limited to 50,000 records. The report will look like the image below.

Default grade submission report with headings course student title grade and date submitted

The report is composed of five columns:

  1. Course: The shortname for the course that the teacher submitted the grade for.
  2. Student: The ID number (idnumber) that is associated with the user, this is unique for Campus Vue.
  3. Title: The title for the grade being submitted. This is "Midterm 1" and "Final Grade" only if midterm is enabled in the grade submission block.
  4. Grade: The letter grade that was submitted to Campus Vue for the student in the course listed in the "Course" column.
  5. Date Submitted: The date that the grade was submitted to the Campus Vue server.
1.2.1.1. Filtering the report

The results shown in the report can be filtered via the filter area above the report table. The following are all of the filters that can be used to narrow the amount of data to be resubmitted to Campus Vue.

Filters for the grade resubmission report described below

  • Course: The course field allows the report to display only one of the selected courses. The courses that are selectable in the drop-down are only those courses that have the Grade submission block installed and that have had grades submitted by the teacher.
  • Student: The student drop-down depends on the course being set first. This drop-down lists all of the students that are in the course. To the right of the students' name is the number of grades submitted already.
  • Date Submitted: The date submitted fields allow the administrator to filter the records in the report by when the grade was submitted to Campus Vue. You can search by "is after" or "is before" a specific date.

To filter a report select how you want to filter the information and click the Filter button.

1.2.1.2. Exporting Report

The grades report needs to be exported to a CSV file which the administrator can upload to Campus Vue for processing. The Resubmit Grades report will export data that matches the filter settings and that is displayed in the report area. To export the data, click on the Export drop-down menu and select the CSV file format to export to. A save dialog will then appear based on your browser.

What column is being sorted on and the filters will affect how the CSV file looks. If you open the CSV file you may see something similar to the following:

1 FPC12 2/16/2012 40
14 FPC12 2/16/2012 360

There are no column headers in the file and the data doesn't match the text in the report view. This is because the file is created for Campus Vue processing. The columns in the report are as follows:

  1. Student: The Joule student id number.
  2. Course: The Joule course shortname.
  3. Date Submitted: The date the grade was originally submitted.
  4. Title: This is "M" for midterm and "F" for final.
  5. Grade Type: This is always "L" for letter with the Campus Vue integration.
  6. Grade: The letter grade to be submitted.
1.2.1.3. Report View Types

The resubmit grades report can be displayed in two different views: basic and standard (AJAX). By default the standard view is used to provide the quickest response and most features. However, if the standard view is causing problems, a user can always switch to the basic view and the problem should be alleviated.

1.2.1.3.1. Standard (AJAX) View

The standard view of a report renders the data using AJAX and sorting a column will load data into the report without reloading the page.

1.2.1.3.2. Basic HTML View

The basic HTML view displays all data in an HTML table for processing. Sorting will cause the page to refresh in this view type. It is recommended that the basic HTML view is used when using a screen reader.

1.2.1.3.3. Changing Views

To change your report view, click on the Basic HTML or Standard links at the bottom of the reports. Once you have clicked the desired link, the page will refresh and all reports will display in this view for the rest of your session.

1.2.2. Configure Attendance Weighting

The Campus Vue integration block allows an administrator to set the weights for each loggable action that a student has taken in a course. Whenever the action is performed it is recorded and the value in the weight field is added to the file to be sent to the Campus Vue server. When viewing the Attendance Weighting page the administrator will see a list of all actions for a course that have been currently logged by a student in the system. If at least one student hasn't accessed a course in the system then no rows will be displayed on the attendance weighting page. Furthermore, if at least one student hasn't performed an action that creates a log record for the activity or course, then a row for that action will not display. The page will look similar to the image below when some actions have been performed by students in a course:

Table of attendance actions and their associated weights in the attendance weights page

The attendance weights table has three columns:

  1. Module: The module that creates the log entry. Usually this is an activity, resource type or course.
  2. Action: The action that is being logged for the module that will cause the weight to be recorded.
  3. Weight: The value that will be sent to Campus Vue when the action is logged for the module. This is usually a number between 0 and 100.

The only activities that can be weighted are those that meet the following criteria:

  1. Are an action, an activity or a course work log, blocks are excluded from this.
  2. A student has already caused the action to be logged in one or more courses.

New weightable actions will show up after a new activity has been created in any course on the site and a student has interacted with that activity in some way. Weights are universal and can only be configured at the site level and will affect all courses that are part in Campus Vue.

It is recommended that a demonstration or sample course is created using all of the activities that the Institution plans on weighting and a student interacts with each of those activities before the administrator assigns weights to any activity.

Click the Submit button at the bottom of the page to set the weights for the actions. If weights are changed for existing actions then all actions of that type will need to be resubmitted to Campus Vue. Attendance for all existing courses with student log data will be sent to Campus Vue after the weights are saved. Even courses that are not part of Campus Vue will have their weights sent to CampusVue but not processed by Campus Vue. Only a sum total of the weights for all actions that a student took in a course for the day will be sent, not each individual action and its weight. See the Resubmit Attendance report for what is sent to Campus Vue.

1.2.3. Resubmit Attendance

The resubmit attendance report allows an administrator to download a CSV file of attendance data. This CSV file can then be submitted to Campus Vue for processing. An example of an unfiltered attendance report is below:

Attendance report table with example data. The columns are described below

The report is composed of four columns:

  1. Course: The shortname for the course that the attendance was submitted for.
  2. Student: The ID number (idnumber) that is associated with the user, this is unique for Campus Vue.
  3. Date: The date that the attendance was taken.
  4. Attendance: The sum total weighted attendance the student earned for the date.
1.2.3.1. Filtering the report

The results shown in the report can be filtered via the filter area above the report table. The following are all of the filters that can be used to narrow the amount of data to be resubmitted to Campus Vue.

Filters for the attendance resubmission report described below

  • Course: The course field allows the report to display only one of the selected courses. The courses that are selectable in the drop-down are only those courses that have attendance logs that have weighted attendance actions.
  • Student: The student drop-down depends on the course being set first. This drop-down lists all of the students that are in the course. To the right of the student's name is the number of grades submitted already.
  • Date: The date fields allow the administrator to filter the records in the report by when the attendance was taken and sent to Campus Vue. You can search by a date that "is after" or "is before" a specific date.

To filter a report select how you want to filter the information and click the Filter button.

1.2.3.2. Exporting Report

The resubmit attendance report needs to be exported to a CSV file which the administrator can upload to Campus Vue for processing. The resubmit attendance report will export data that matches the filter settings and that is displayed in the report area. To export the data, click on the Export drop-down menu and select the CSV file format to export to. A save dialog will then appear based on your browser.

What column is being sorted on and the filters will affect how the CSV file looks. If you open the CSV file you will see something like the following:

1 FPC12 2/16/2012 M L A
14 FPC12 2/16/2012 F L C

There are no column headers in the file and the data doesn't match the text in the report view. This is because the file is created for Campus Vue processing. The column in the report are as follows:

  1. Student: The Joule student ID number (idnumber).
  2. Course: The Joule course shortname.
  3. Date: The date that the attendance was for.
  4. Attendance: The sum total weighted attendance the student earned for the date.
1.2.3.3. Report View Types

The resubmit attendance report can be displayed in two different views: basic and standard (AJAX). By default the standard view is used to provide the quickest response and most features. However, if the standard view is causing problems, a user can always switch to the basic view and the problem should be alleviated.

1.2.3.3.1. Standard (AJAX) View

The standard view of a report renders the data using AJAX and sorting a column will load data into the report without reloading the page.

1.2.3.3.2. Basic HTML View

The basic HTML view displays all data in an HTML table for processing. Sorting will cause the page to refresh in this view type. It is recommended that the basic HTML view is used when using a screen reader.

1.2.3.3.3. Changing Views

To change your report view, click on the Basic HTML or Standard links at the bottom of the reports. Once you have clicked the desired link, the page will refresh and all reports will display in this view for the rest of your session.

1.3. Global Settings

1.3.1. General Settings

Campus Vue Integration Block General settings as described below

  • SFTP URL: Fully Qualified Domain Name for the Campus Vue SFTP server. Example: sitename.compusvue.com
  • SFTP Username: The username for the SFTP account on the Campus Vue SFTP server.
  • SFTP Password: The password for the SFTP account identified by "SFTP Username" on the Campus Vue SFTP server.
  • SFTP Port: The port to connect to at the Campus Vue SFTP server identified by "SFTP URL" (In range 0 - 65535). Default: 22
  • SFTP Path: The file path on the Campus Vue SFTP server to which files should be uploaded.
  • Attendance Calculation: The frequency at which the attendance calculation should be run. Default: Daily

1.3.2. Last Successful Integration

last integration dates that have been recorded by the system

  • The last successful grade integration was: The date printed here is the last date that the grades data was sent via SFTP to the Campus Vue server defined in the SFTP URL.
  • The last successful attendance integration was: The date printed here is the last date that the attendance data was sent via SFTP to the Campus Vue server defined in the SFTP URL.

2. Class List

2.1. Overview

The Class List block makes it easy for a user to see other users enrolled in a Joule course. The Class List block displays all people enrolled in a course and allows quick access to user profiles and direct messaging. A (T) differentiates the teacher from the students, and the color of the persons' name in the list indicated whether the user is on/offline.

2.2. User Documentation

2.2.1. Class List block

Navigate to the Class List block.

Note: If you do not see the Class List block, a site Administrator or Teacher with editing permissions will need to add the Class List block to the course.

a list of students in the course with envelope icon for messaging

Click on the envelope next to a person's name to create and send a personal message, or click on a name in the list to visit the profile of that person.

The names of students online will be bold and students who are not online will not be bold. Messages can be sent to users who are not online and they will receive them when they log back in.

A (T) designates that that person is the Teacher in the course.

2.3. Administrator Documentation

2.3.1. Class List block

Navigate to the Settings block and click Site administration>Plugins>Blocks>Class List to access the settings for the Class List block.

menu settings for class list include offline time

Select from the following:

  • Offline time: designates the number of seconds after the last time Moodle recorded an action that the user is considered offline.
  • Enable AJAX updating: check to update the users who log on and off in the time set in the AJAX interval.
  • AJAX interval: enter a time to set how often (in seconds) the live updating of the Class List block should happen.

Click Save changes when you are finished.

3. Collect

3.1. Overview

The Collect block is used to gather data within a course based on the collectors and data points that the site administrator has set to be collected. These data points are then displayed within the Joule reports block.

3.1.1. Site Interface

At the site level, the Collect block displays a link to the settings for the block. However, Moodlerooms recommends that the block is not added to the site level.

3.1.2. Course Interface

At the course level, the administrator can see the following links:

  • Collect course data: Clicking this link will execute the data collection cron for the course based on the collectors and data points set in the global settings
  • Global settings: Clicking this link will bring the user back to the site's global settings to enable and disable collectors and data points

3.2. Global Settings

The Collect block's administrative settings are used to turn on or off collectors and collection data points. All collectors have two settings in common:

  • Enabled: Turn this data collector on or off. Enabling the collector enables data collection for all courses with the collect block in it.
  • Run data collection every: Set the time interval for when this data collection routine should run. The collector must also be enabled and have at least one data collection point enabled before it will run.

You can also force all collectors to run by clicking on the Force data collection cron to run now link above the General settings section.

3.2.1. General Settings

  • Exclude hidden courses: Do not collect data on courses that are not visible. The course itself must be set to hidden and not just its category or parent category.

3.2.2. Course

This data collector collects data about courses. Available data points currently include:

  • Grade: Collect the overall course grade information from the course's grade book.

3.2.3. Course/User

This data collector collects data about users and their enrolled courses. The users who are included are those with a graded role (these are set and listed in Site Administration block > Grades > General Settings) whose enrolled course(s) have the Collect block added to them. Available data points include:

  • Enrollment end: Record the time when a user is unenrolled from a course. This is collected upon the "role unassigned" event.
  • Enrollment start: Record the time when a user is enrolled into a course. This is collected upon the "role assigned" event.
  • Course grade: Record a user's course grade. This is collected on the cron.
  • Course completion: Record a user's completion percent of a course and the date of completion. This is collected on the cron. The percent complete is based on the number of graded quizzes and assignments in the course. An activity is considered complete when there is a grade in the grade book for a user for that particular activity.
  • View: Record the number of times a user has viewed the course and the date of their last view. This data is based on the Moodle log table.

3.2.4. Activity

This data collector collects data about activities within a course. Available data points include:

  • Grade: Collects activity grade information
  • Name: Collects the activity name
  • Sort order: Collects the activity's sort order in a course, which is based on the activity's placement in sections

3.2.5. Activity/User

This data collector collects data about users' interactions with course activities. The users included are those with a graded role whose enrolled course(s) have the Collect block added to them. Available data points include:

  • Attempt: Record the number of attempts, graded attempts and the last attempt date for a user in an activity. This is collected on the cron.
  • Grade: Record a user's activity grade information. This is collected on the cron.
  • Post: Record the number of times a user has posted in an activity and the date of their last post. This data is based on the Moodle log table.
  • View: Record the number of times a user has viewed an activity and the date of their last view. This data is based on the Moodle log table.

3.2.6. SCORM/Track

The SCORM activity places tracking data in one table with a record for each interaction of an attempt. This data collector normalizes SCORM tracking data for SCORM activities in the course creating on collector record for each attempt on the SCORM activity. Available data points include:

  • Track: Normalizes SCORM tracking data into one table with one record per attempt instead of one per interaction.
Removing the Collect block from a course does not remove its data from the collect tables. Deleting a course, activity or enrollment will remove the data from the Collect tables for the Joule reports.

3.3. Permissions

  • Can run course collection: This permission allows the user to execute the collection cron for the course.
    • Default Permissions
      Role Not Set Allow Prevent Prohibit
      Manager   X    
      Course Creator X      
      Teacher X      
      Student X      
      Guest X      
      Authenticated User X      

4. Conduit

4.1. Administrative Documentation

4.1.1. Information

The Information tab provides the user with information about what is happening in Conduit as well as access to this manual from within Joule. The information tab is separated into two sub tabs for general information and Conduit message information.

4.1.1.1. General

The general sub tab provides the site administrator with the current Conduit version as well as a link to the Conduit manual.

General information linking to this manual

4.1.1.2. Messages

The Messages sub tab displays all messages that Conduit can report to a user when a report is generated. Messages are separated into three areas by severity: errors, warnings and informational. Error messages will also print out what debugging information the system can provide. Below is a listing of each error and what they mean and what resolution needs to be taken. Most errors that mention contacting your Application Specialist should never happen on a Production system.

4.1.1.2.1. Messages that are a result off an error
Error Report Text Description
error:app General application error: (variable) This is a generalized error to denote an issue is not specific to a situation or file.
error:cannotopenfile The file '(variable)' cannot be opened Most likely a permissions error that did not allow Conduit to open the file. The file could also be improperly formatted.
error:conduitgroupsrenamesql Conduit Groups to Conduit Groups re-name SQL failed. Database issue with the SQL this should be reported to your Applications Specialist for diagnosis.
error:conduitsync An unexpected error occurred while synchronizing incoming (variable) data. Error message: (variable) Debug info: (variable) Conduit is unsure what it failed on but it providing as much information as it can for the error. This should be reported to your Applications Specialist for diagnosis.
error:coursearchive Course archiving failed for course with (variable) = (variable). Course deletion skipped. Reason: (variable) There was an issue with the backup of the course; usually this will cause the regular backup to fail. Try to fix the course to remove the issue and delete the course again.
error:coursecreate Course failed to be created with (variable) = (variable). Reason: (variable) There was an error creating the course, usually this is a database error. This should be reported to your Applications Specialist for diagnosis.
error:coursedelete Course failed to be deleted with (variable) = (variable) The course with the course look up field mapping with the value following value failed to be deleted. This is usually a database error and should be reported to your Applications Specialist.
error:coursefieldvaluenotfound Failed to look up course where (variable) = (variable). Perhaps the field/value pair is not unique or the course doesn't exist Conduit could not determine a unique entry for the course provided. Either it doesn't exist or there is more than one record for the look up identifier.
error:coursetemplate Course templating failed for course with (variable) = (variable). Reason: (variable) There was an error creating the course because it was being created from a backup file that caused errors. Please check the backup file and resubmit the course creation request.
error:courseupdate Course failed to be updated with (variable) = (variable). Reason: (variable) Conduit couldn't update the course; usually this is a database error. This should be reported to your Applications Specialist for diagnosis.
error:cron The following error occurred on the cron: (variable) Debug info: (variable) (variable) The Conduit cron ran into an error stated in the text. This should be reported to your Applications Specialist for diagnosis.
error:csvcolumnmissmatch The file '(variable)' does not contain the same number of columns as it does the number of data columns The number of header columns doesn't match the number of columns with data in them. The file is improperly formatted and will need to be fixed and resent
error:csvnoaction The file '(variable)' contains no action column The action column in the CSV file could not be found by Conduit. Either it is miss named, the file is formatted incorrectly or it doesn't exist.
error:csvnodata The file '(variable)' does not contain any data to process (second line not found) Conduit couldn't find a second line in the CSV file. Either there was no data in the file, or the file is improperly formatted.
error:csvnomappings The file '(variable)' does not contain any of the configured field mappings The header of the CSV file doesn't have any of the fields that have been mapped for the file type in Conduit's Settings > Mappings tab.
error:datavalidation Data failed to validate, errors: (variable) Debug info: (variable) The data for the field did not pass the validation for the field. See Mappings section for the validation criteria for the field.
error:emailadminsnotfound Failed to email because admin users with ids = (variable) could not be found. Please update your email_to config. The administrator account set in the Setting > General tab doesn't exist anymore. Update the settings to fix the error.
error:emailsend Failed to send email to user (username = (variable) email = (variable)) There was an issue sending the email to the administrative user, probably with the email server. This should be reported to your Application Specialist.
error:emailunknownconfig Failed to email because email_transactions config is set to unknown value: (variable) The transactions setting under the email form group in the Settings > General tab is not an accepted value any more. Please update the value to one that is in the drop down.
error:emptyfile The file '(variable)' is empty The file that was uploaded to be processed was empty of any data.
error:enrolmentscreate Enrollment failed to be created with course (variable) = (variable) and user (variable) = (variable). Reason: (variable) The enrollment record failed to be created for the user and course provided. Based on the reason this should be resolved by creating the user or course or you will need to contact your Application Specialist.
error:enrolmentsdelete Enrollment failed to be deleted with course (variable) = (variable) and user (variable) = (variable). Reason: (variable) The enrollment for the course and user failed to be deleted. Depending on the reason the user or course may not have existed or you may need to contact your Application Specialist.
error:enrolmentsgroupsmembersdelete Failed to delete group memberships for unenrolled user with (variable) = (variable) The group membership for a user in a course was not deleted. This is usually a database error and should be reported to your Application Specialist.
error:enrolmentsupdate Enrollment failed to be updated with course (variable) = (variable) and user (variable) = (variable). Reason: (variable) The enrollment for the user and course failed to be updated. This is usually a database error and should be reported to your Application Specialist.
error:groups_memberscreate Group membership failed to be created with course (variable) = (variable), group name = (variable) and user (variable) = (variable). Ensure user is enrolled into course. The group membership failed to be created. This could be because the group or user doesn't exist. If both do exist and the Conduit information is correct then this should be reported to your Application Specialist.
error:groups_membersdelete Group membership failed to be deleted with course (variable) = (variable), group name = (variable) and user (variable) = (variable) The group membership failed to be deleted for the course, group and user. This is usually a database error and should be reported to your Application Specialist.
error:groupsclearsql Conduit Groups re-name clear SQL failed. Conduit tried to rename a group and if failed. This is a database error and should be reported to your Application Specialist.
error:groupscreate Group failed to be created with course (variable) = (variable) and group name = (variable) The group failed to be created in the course. The course could not exist, otherwise this is a database error and should be reported to your Application Specialist.
error:groupsdelete Group failed to be deleted with course (variable) = (variable) and group name = (variable) Conduit failed to delete the group. This is usually a database error and your Application Specialist should be notified.
error:groupslogupdate Conduit Groups transaction log update SQL failed. Conduit failed to update the transaction log table for the groups. This is a database error and should be reported to your Application Specialist.
error:groupsmembersrenamesql Conduit Groups to Conduit Group Members re-name SQL failed. Conduit tried to rename the group memberships and failed. This is usually a database error and should be reported to your Application Specialist.
error:groupsrenamesql Conduit Groups to Moodle Groups re-name SQL failed. Conduit tried to rename the group and failed. This is usually a database error and should be reported to your Application Specialist.
error:groupsupdate Group failed to be updated with course (variable) = (variable) and group name = (variable) The group failed to update for the course, either the course doesn't exist or this is a database error and should be reported to your Application Specialist.
error:invalidaction Invalid action found: (variable). Valid actions: (variable) The action that was sent is not one that can be used with the service or any service. Check the action and review the acceptable actions in this manual.
error:moodlecoursenotfound Moodle course could not be found, but should already exist for Conduit course with (variable) = (variable) Conduit was able to locate the course in the database but was not able to locate it via the code; usually there is a case issue here. Please contact your Application specialist.
error:moodlegroupnotfound Moodle group not found, but should have been. Group ID = (variable) with course (variable) = (variable) Conduit was able to locate the group in the database but was not able to locate it via the code; usually there is a case issue here. Please contact your Application specialist.
error:moodleusernotfound Moodle user could not be found, but should already exist for Conduit user with (variable) = (variable) Conduit was able to locate the user in the database but was not able to locate it via the code; usually there is a case issue here. Please contact your Application specialist.
error:mustbearray The passed resource must be an array This is a coding issue and your Application Specialist should be contacted with this error.
error:role_assigncreate Role assignment failed to be created with (variable) = (variable), (variable) = (variable), (variable) = (variable), (variable) = (variable). Reason: (variable) The role assignment for the course and user failed because of the reason. This could be that the user, role or course didn't exist or that there was a database error the needs to be reported to your Application Specialist.
error:syncexception (variable)::(variable)() halted with error: (variable) The synchronization process between Conduit and Moodle stopped. Please contact your Application Specialist.
error:unexpectedexceptiononaction An unexpected error occurred while performing (variable) action: (variable). Error message: (variable) Debug info: (variable) An unexpected error occurred and you should contact your Application specialist with the error and debug information.
error:usercreate User failed to be created with (variable) = (variable) The user with the look up field and id was not created. This is usually a database error and your Application Specialist should be contacted.
error:usercreatenousername Missing username, user creation ignored! Debug info: (variable) The user was not created because no username was provided.
error:userdelete User failed to be deleted with (variable) = (variable) The user with the look up field and value failed to be deleted. This is usually a database error and your Application Specialist should be contacted.
error:userdeleteenrolments Failed to delete enrollments for deleted user with (variable) = (variable) The user was deleted by there was an error that didn't allow the user's enrollments to be removed. This is usually a database error and your Application Specialist should be contacted.
error:userdeleterole_assign Failed to delete role assignments for deleted user with (variable) = (variable) The user was deleted by there was an error that didn't allow the user's role assignments to be removed. This is usually a database error and your Application Specialist should be contacted.
error:userfieldvaluenotfound Failed to look up user where (variable) = (variable). Perhaps the field/value pair is not unique or the user doesn't exist Conduit could not find the user based on the look up field with the provided value. This usually means that there are two or more users in Moodle with the same value in the look up field. This can happen with email or idnumber which don't have to be unique in the Moodle database.
error:usergroupsmembersdelete Failed to delete group memberships for deleted user with (variable) = (variable) The user was deleted by there was an error that didn't allow the user's group memberships to be removed. This is usually a database error and your Application Specialist should be contacted.
error:userinsertcustom Failed to insert custom profile data (field shortname = (variable) and user (variable) = (variable)) Failed to insert custom profile information into the custom profile field for the user. The profile field could have been deleted but this is probably a database error and should be reported to your Application Specialist.
error:userprune Failed to prune extra profile data in Conduit tables for user (variable) = (variable) Conduit failed to correctly prune the Conduit user table. This is a database error and your Application Specialist should be contacted.
error:userrevive Failed to revived (variable) accounts The user account failed to be unsuspended and therefore the user can still login to the site. This is usually a database error and your Application Specialist should be contacted.
error:usersuspend Failed to suspend user with (variable) = (variable) Conduit failed to suspend the user account. The user will still be able to access their account. This is usually a database error and you should contact your Application Specialist.
error:userupdate User update failed with (variable) = (variable) Conduit failed to update the user based on the look up field and the value. This is usually a database error and your Application Specialist should be contacted.
error:userupdatecustom Failed to update custom profile data (field shortname = (variable) and user (variable) = (variable)) Conduit failed to update the custom profile field for the user. This is usually a database error and your Application Specialist should be contacted.
error:userupdatepassword User with (variable) = (variable) has updated their password and the new password has not been saved to Conduit The user password in Moodle has been updated and that password failed to be updated in Conduit. This should be reported to your Application Specialist.
error:xmlschemaerrors The passed XML Schema failed to validate with error:(variable) The XML passed to the web service or uploaded as a file did not properly validate. Please download the XML schema for the web service and validate your XML schema.
4.1.1.2.2. Messages that are a result of a warning
Warning Report Text Description
warning:categorynumbernotexist Conduit course with (variable) = (variable) has a category that is a number and it does not match with any category record IDs in Moodle's database. The value is (variable) The category for the course doesn't exist in Moodle and can't be assigned to the course. This means it is created in the default category in the Course settings.
warning:coursedeleteenrolments Failed to delete enrollments for deleted course with (variable) = (variable) A course was deleted but Conduit could not delete the enrollments for the course. These records can be removed via the Edit tab.
warning:coursedeletegroups Failed to delete groups for deleted course with (variable) = (variable) A course was deleted but Conduit was unable to delete the groups for the course. These records can be removed via the Edit tab.
warning:coursedeleterole_assign Failed to delete role assignments for deleted course with (variable) = (variable) A course was deleted but Conduit was unable to delete the role assignments for the course. These records can be removed via the Edit tab.
warning:groupsmemberscleanup Group memberships failed to be cleaned from Conduit for course (variable) = (variable) and group name = (variable) A course was deleted but Conduit was unable to delete the group memberships for the course. These records can be removed via the Edit tab.
warning:role_assigninvalid Role assignment invalid: id = (variable), context = (variable), moodlekey = (variable), userkey = (variable), rolekey = (variable). Validation: moodlekey is (variable), userkey is (variable) and rolekey is (variable). The role being assigned didn't exist in Moodle and needs to be added or the Conduit entry needs to be modified with an existing role.
4.1.1.2.3. Information messages
Information Report Text Description
none:coursecreate Course created with (variable) = (variable) A course with the look up field matching the value was created.
none:coursedelete Course marked for deletion with (variable) = (variable) A course with the look up field matching the value was marked to be deleted in Moodle.
none:coursedeleteenrolments Deleted enrollments for deleted course with (variable) = (variable) Enrollments for the course with the look up field matching the value were removed.
none:coursedeletegroups Deleted groups for deleted course with (variable) = (variable) Groups in a course that was deleted and matched the look up field with the provided value were deleted.
none:coursedeletemoodle Course deleted with (variable) = (variable) A course with the look up field matching the value was deleted.
none:coursedeleterole_assign Deleted role assignments for deleted course with (variable) = (variable) Role assignments in a course that was deleted and matched the look up field with the provided value were deleted.
none:courseupdate Course updated with (variable) = (variable) A course with the look up field matching the value was updated.
none:enrolmentscreate Enrollment created with course (variable) = (variable) and user (variable) = (variable) An enrollment with the look up field matching the value was created for a course with the look up field matching the value and a user with the look up field matching the value.
none:enrolmentsdelete Enrollment deleted with course (variable) = (variable) and user (variable) = (variable) An enrollment with the look up field matching the value was deleted for a course with the look up field matching the value and a user with the look up field matching the value.
none:enrolmentsgroupsmembersdelete Deleted group memberships for unenrolled user with (variable) = (variable) A group membership for a user that was unenrolled from a course was deleted.
none:enrolmentsupdate Enrollment updated with course (variable) = (variable) and user (variable) = (variable) An enrollment with the look up field matching the value was updated for a course with the look up field matching the value and a user with the look up field matching the value.
none:groups_memberscreate Group membership created with course (variable) = (variable), group name = (variable) and user (variable) = (variable) Group memberships were created for the course with the look up field matching the value and the group with the name matching the value.
none:groups_membersdelete Group membership marked for deletion with course (variable) = (variable), group name = (variable) and user (variable) = (variable) Group memberships were marked to be deleted for the course with the look up field matching the value and the group with the name matching the value.
none:groups_membersdeletemoodle Group membership deleted with course (variable) = (variable), group name = (variable) and user (variable) = (variable) Group memberships were deleted for the course with the look up field matching the value and the group with the name matching the value.
none:groupscreate Group created with course (variable) = (variable) and group name = (variable) Group was created that matches the name for the course that matches the look up field and value.
none:groupsdelete Group marked for deletion with course (variable) = (variable) and group name = (variable) Group was marked to be deleted that matches the look up field and value for the course that matches the look up field and value.
none:groupsdeletemoodle Group deleted with course (variable) = (variable) and group name = (variable) Group was deleted that matches the name for the course that matches the look up field and value.
none:groupsmemberscleanup Group memberships cleaned from Conduit for course (variable) = (variable) and group name = (variable) The group memberships for the course with the look up field matching the value and the group with the name matching the value were cleaned.
none:groupsupdate Group updated with course (variable) = (variable) and group name = (variable) A group with the name matching the value was updated for a course with the look up field matching the value.
none:role_assigncreate Role assignment created with (variable) = (variable), (variable) = (variable), (variable) = (variable), (variable) = (variable) A role assignment with the look up field matching the value was created for a course with the look up field matching the value and a user with the look up field matching the value.
none:role_assigndelete Role assignment deleted with (variable) = (variable), (variable) = (variable), (variable) = (variable), (variable) = (variable) A role assignment with the look up field matching the value was deleted for a course with the look up field matching the value and a user with the look up field matching the value.
none:role_assignupdate Role assignment updated with (variable) = (variable), (variable) = (variable), (variable) = (variable), (variable) = (variable) A role assignment with the look up field matching the value was updated for a course with the look up field matching the value and a user with the look up field matching the value.
none:simpletest1 Simpletest (variable) (variable) A simpletest has returned the value in the variable. This is used by Moodlerooms for testing.
none:simpletest2 Simpletest (variable) A simpletest has returned the value in the variable. This is used by Moodlerooms for testing.
none:usercreate User created with (variable) = (variable) The user with the look up field matching the value has been created.
none:userdelete User deleted with (variable) = (variable) The user with the look up field matching the value has been deleted.
none:userdeleteenrolments Deleted enrollments for deleted user with (variable) = (variable) An enrollment for the user with the look up field matching the value has been deleted.
none:userdeleterole_assign Deleted role assignments for deleted user with (variable) = (variable) Role assignments for the user with the look up field matching the value have been deleted.
none:usergroupsmembersdelete Deleted group memberships for deleted user with (variable) = (variable) Group memberships for the user with the look up field matching the value have been deleted.
none:userrevive Revived (variable) accounts The user with the look up field matching the value has been revived.
none:usersuspend Suspended user with (variable) = (variable) The user with the look up field matching the value has been suspended and will not be able to login.
none:userupdate User updated with (variable) = (variable) The user with the look up field matching the value has been updated.
none:userupdatepassword User with (variable) = (variable) has updated their password and the new password has been saved to Conduit The user with the look up field matching the value provided has had their password from Moodle updated in Conduit.

4.1.2. Reports

4.1.2.1. Report View Types

Conduit reports, as well as the Conduit table views, come in two different views: basic and standard (AJAX). By default, Conduit uses the standard view to provide the quickest response and most features. However, if the standard view is causing problems, a user can always switch to the basic view and the problem should be alleviated.

4.1.2.1.1. Standard (AJAX) View

The standard view of a report or table renders the data using AJAX. For Conduit table views, this allows direct editing of the information from within the cell by double clicking on the cell. Furthermore, sorting will load data into the report without reloading the page.

Log report in the AJAX view mode

4.1.2.1.2. Basic HTML View

The basic HTML view displays all data in an HTML table for processing. Sorting will cause the page to refresh in this view type. It is recommended that the basic HTML view is used when using a screen reader.

basic html view of the report

4.1.2.1.3. Changing Views

To change your report view, click on the Basic HTML or Standard links at the bottom of the reports as in the image below:

click the basic html link below the export drop down to change to eh basic html view of the page.
or
click the basic html link below the with selected drop down

Once you have clicked the desired link, the page will refresh and all reports will display in this view for the rest of your session.

4.1.2.2. Logs

Conduit produces a log report that displays the processing details of every action requested of Conduit and any errors that occur. A log record is created for each manual modification as well as each file or Web services request that Conduit has processed for each Conduit service:

  1. Course
  2. Enroll
  3. Group
  4. Group members
  5. Role assign
  6. User

The initial view of the Logs report is the transaction overview page, where each transaction lists the transaction details below for each log record:

  • Action Checkbox: Checking this checkbox allows for actions in the With selected... drop-down menu to be taken on this record.
  • View Logs Icon: Magnifying glass icon to view transaction log details
  • Transactions: The number of transactions processed by Conduit for Conduit's tables and Moodle for this request
  • Name: Name of the method, file or table manually edited
  • Type: Type of plug-in processed:
    • Conduit/edit
    • File/CSV
    • File/XML
    • Webservice/XML
  • Status: Status of processing the file
    • OK
    • ERROR
  • Time Started: The time the data source was consumed
  • Time Completed: The time the data source was completed

Log report in the AJAX view mode

Each heading can be clicked to sort the transactions according to that item.

4.1.2.2.1. Viewing Transactions

To access detailed information about the actual actions taken for each transaction in Conduit and in Moodle, you will need to view the detailed record for the transaction. To view the transaction log, click the magnifying glass icon next to the desired transaction to view the logs. This takes you to a screen that lists each action processed by Conduit with the following populated fields:

  • Severity: Severity of any error during processing individual record
  • Source: The system the transaction was processed for either conduit or Moodle.
  • Message: Short message of the action taken and information on any error that occurred when importing the file to Conduit
  • Time Created: Time the action was completed

detailed transaction view of a specific report

Click the Back button to return to the "View All Transactions" overview. Here, you can delete older log records in order to keep your overview organized.

4.1.2.2.2. Filtering Logs/Detailed Transaction Report

Logs and detailed transaction log filtering works much the same as the other filter in Conduit. In the "Filter" area of the screen, select the values you wish to filter by and then click the Filter button. The records listed will then be filtered by the values entered or selected.

You can filter by the following fields in the transactions report:

  • Transaction Name
  • Transaction Type
  • Exclude Empty Transactions (advanced option)
  • Time Started
  • Time Completed (advanced option)

filters for the log reports screen to reduce the number of records

You can filter by the following fields in the transaction logs report:

  • Message
  • Severity
  • Source

filters for the detailed transaction logs

4.1.2.2.3. Deleting Transaction logs

In order to reduce the number of log records kept in the system, it is recommended that you delete older logs. To delete old log records manually, follow these steps:

  1. Select the checkboxes next to the transactions you wish to delete or alternatively click Select All.
  2. Choose Delete from the With Selected... drop-down menu.
    Logs selected and the with selected drop down expanded to delete.
  3. A message will appear asking you to confirm that you want to delete these transaction logs. Click Yes.
4.1.2.3. Related Logs

The Related Logs report is designed to assist administrators in finding all transactions for a given user, course, enrollment, group or group member. This provides administrators with a view into all of the Conduit actions that have been processed on the given user, course, enrollment, group or group member along with what date the transaction was processed.

related logs report screen

4.1.2.3.1. Filter Related Logs

Filtering fields for related logs depend on the Conduit table selected. The common fields are:

  • Log Message
  • Severity
    • All
    • None
    • Warning
    • Error
  • Source
    • All
    • Conduit
    • Moodle
  • Time Created

The Conduit table-specific fields are:

  • username (user table)
  • shortname (course tables)
  • course key (enrolments, groups, group_members and role_assign tables)
  • userkey (enrolments, group_members, and role_assign tables)
  • groupkey (groups and group_members tables)
  • moodlekey (role_assign table)
  • context (role_assign table)

related logs filter screen shot

4.1.2.4. Unmatched Records

The Unmatched records report is designed to assist administrators in identifying records in Moodle that aren't in Conduit and vis versa. The administrator selects the Conduit table that will be compared and then selects the Unmatched source. When the unmatched source is Moodle then Moodle's table is compared to Conduits and any record in Moodle not in Conduit is displayed. When Conduit is set then Conduit's table is compared to Moodle and any record in Conduit that is not in Moodle is displayed.

Example unmatched records report for the course comparing Moodle to Conduit

4.1.2.4.1. Filtering Unmatched Records

Filtering fields for the unmatched records report depend on the Conduit table selected and the fields mapped for the table. There are no common fields and the common table specific fields are:

  • username (user table)
  • shortname (course tables)
  • course key (enrolments, groups, group_members and role_assign tables)
  • userkey (enrolments, group_members, and role_assign tables)
  • groupkey (groups and group_members tables)
  • moodlekey (role_assign table)
  • context (role_assign table)
4.1.2.5. Grades

The Grades report is designed to display course total, manual, category and manual grades (depending on the grade's Web services settings) for all users (in Conduit enrollments or another method) in all courses with the Collect block in it. The grade report can be accessed through the Conduit Reports tab > Grades sub-tab.

grade report screen

Note
The Grades report doesn't display data in a column if the data is the same as the previous record. However, when the grade book report is downloaded, the data will be in the record.
Note
The Grades report requires that the Collect block be configured to collect grade data and that the block is added to all courses that grade data is to be collected for. For more information about the Collect block, review [Collect Block Manual].
4.1.2.5.1. Filtering Grades Report

The Grades report can be filtered on the following fields:

  • User
  • Course
  • Grade Item Type
  • Time Modified

The user and course fields have type ahead filters, which show a list of possible matches as a user types - they can even search multiple fields, such as a user's name and e-mail address, at the same time.

Grade filters for the grade report

4.1.2.6. Exporting Logs/Related logs/Grades

Any Conduit report can be exported in CSV and Excel formats. This report will export data that matches the filter settings. To export the reports, click on the Export drop-down menu and select the file format you want to export to. A save dialog will then appear based on your browser.

4.1.3. Edit

The Edit tab allows the Administrator to manually manage the data stored within Conduit separate from the data in Joule. Besides being able to view the data in Conduit's tables the Edit tab allows the Administrator to:

  • Edit a Row of Data
  • Delete a Single Row of Data
  • Delete Multiple Rows
  • Search the Table's Data
4.1.3.1. Viewing Conduit Data

Conduit's data is stored in six tables:

  • Course: Course information
  • Enroll: Enrollment information
  • Groups: Group information
  • Group members: Group member information
  • Role assignment: Role assignment information
  • User: User information

Viewing a table's data is done by selecting the table name from the Conduit table drop-down menu.
Drop down to select the Conduit table to switch to for editing

The records for the table are displayed below the Filter area of the page. The columns of the table displayed are based on the fields mapped in the Settings > Mappings for the table. The records displayed for the table are based on the filters set.

4.1.3.2. Filter Conduit Records

Conduit provides filters for all fields mapped in the Settings > Mappings for the table. The Time created and Time modified filters are displayed if the Show advanced button is clicked. The filters are located above the listing of records for the table. Below is a listing of sample filters for the Conduit Course table for a site.

Filters for the course edit screen

To filter the records displayed for the Conduit table, you can perform the following:

  1. Enter a string value for the field to filter on (Ex. Enter "conduit1" in the username field)
  2. Click the Filter button

Conduit will then only display records with the value set. Multiple filters can be used to reduce the number of records shown.

4.1.3.3. Create a New Record

Administrators can add records to any Conduit table manually by selecting the table from the Create new drop down menu. When adding a record, Conduit only displays the mapped fields as values that can be entered for the new record, similar to the image below:

Create a new course screen based on the course mappings page

To add a new record to any Conduit table, follow the steps below:

  1. Select the table name from the Create new drop-down menu
  2. Enter the information for each field
    Note
    If you leave a field blank, Conduit will use the default value for that field
  3. Click the Save Changes button.
4.1.3.4. Edit a Record

When editing a Conduit record, you will only see the fields mapped in the Settings > Mappings for the table.

To edit an entire row of data for the table follow these steps:

  1. Find the row you wish to edit. You can sort the list of fields by clicking on the header name (in the example below, you could sort by ID, user name, last name or any of the gray heading links). You may also use the filters to filter the records.
  2. Click the edit icon.
    edit icon in the action column to the left of the id column
  3. Edit any of the data columns as necessary. Identifier fields for the table will not be editable, except for the user table.
  4. Click Save Changes to commit the changes back to the external database, or click Cancel to cancel all changes.
Site administrator can manually edit the value in the user key field (username, email, idnumber). The changes to this field's value will be propagated throughout the system. This allows for the re-identification of a user within Joule.
4.1.3.5. Delete a Database Row

You can completely remove data from the external database via two methods: deleting individually or in bulk.

WARNING
There will be no confirmation for either of these delete methods, so be absolutely sure you wish to delete these records before clicking.

To delete individual rows of data from a table, follow these steps:

  1. Locate the row you wish to delete
  2. Click on the red X icon (this is the delete button)
    The delete button in the action column to the left of the id column
  3. Click the Yes button to confirm that the row is to be deleted. After a successful deletion, you will see a green message saying "Rows deleted successfully."

To bulk delete rows of data from the table, follow these steps:

  1. Check the checkbox(es) next to each record you wish to delete or click the Select All link.
  2. From the With selected... drop-down menu, choose Delete.
  3. Click the Yes button to confirm that the row is to be deleted. After a successful deletion, you will see a green message saying "Rows deleted successfully."
4.1.3.5.1. Exporting Records

Any records from the Conduit tables can be exported in CSV and Excel formats. The data that will be exported is the data that matches the filter settings. To export the table data, click on the Export drop-down menu and select the file format you want to export to. A save dialog will then appear based on your browser.

4.1.4. Operations

4.1.4.1. Upload

The Upload sub tab allows a Site administrator to upload a single file to any of the Conduit tables for processing. This can be useful if your automated process has broken, if you need to disable it temporarily or if you have a small set of changes that are easier to process in a single file than manually. The file uploaded must still be either a CSV or XML formatted file and follow all the same rules of these files found in the Mappings Global settings area

Upload file form screen shot

To upload a file follow these steps:

  1. Click on the Operations tab
  2. Select the Conduit table to have the file processed for in the Conduit table field
  3. Click the Chose a file... button
  4. Click the Upload a file link on the left hand column
  5. Click the Choose File button
  6. Select the file to upload
  7. Click the Upload this file button
  8. Click the Upload button

The file will be processed by Conduit as if it was SFTPed to the file directory. A report will be created for all changes, warnings and errors created by the file.

4.1.4.2. Administer

The Administer tab allows a Site administrator to manually execute the Conduit process which processes uploaded files (normally run during the Moodle administrative cron job). This is useful for when a Site administrator needs to process changes now for a file they uploaded via SFTP or the Upload sub tab.

To run the Conduit file process follow these steps:

  1. Click on the Operations tab
  2. Click on the Administer sub tab
  3. Click the Run Conduit Now button
  4. Review the results (the page will refresh every 30 seconds to keep a running update of what is happening)

4.2. Installation

In order for Conduit to fully function, configuration must first take place.

Conduit currently functions with the following file formats and services:

  • Uploaded CSV or XML files
  • RESTful Web Services XML files

To set up Conduit, you must:

  1. Configure the Conduit General Settings for users, courses and enrollments
  2. Map your CSV or XML column headings/data fields to the Conduit fields in the Settings > Mappings tab. Optionally you can download the example files as a template in this location too.
  3. If using file upload, you will define the name and location of your files in the Settings > Files tab.
  4. If using RESTful Web Services, define your password, whether or not you're using HTTPS, any IP restrictions and what grade data is captured in the Settings > Web services tab.

To configure Conduit, you must first add the Conduit block to your site page. To do this, follow these steps:

  1. Log in to your Moodle instance with a site-level admin account.
  2. Go to the site homepage and click the Turn Editing On button.
  3. Add the Conduit block via the Add block drop down. This will display the Conduit site-level administrator block.
    Conduit block in the site course
  4. Click on the Settings link in the Conduit block.

4.3. Settings Tab

4.3.1. General Sub-Tab

4.3.1.1. Restricted

These settings determine what restrictions are placed on the information being sent to Conduit.

Conduit settings under the restricted form grouping

  • Validation: This setting forces Conduit to validate any data being sent to it (via file, web service or manual processes) against valid values for the field. See the Mappings section for the exact field and how it is validated by Conduit if this setting is enabled. If a value doesn't pass validation it is ignored and an error is reported in the Conduit reports. It is recommended that this setting be enabled and is enabled by default for all new clients but current clients will need to enable it.
4.3.1.2. Cron

These settings determine if the Conduit cron is enabled and what Conduit should do with the Conduit logs.

Conduit settings under the cron form grouping

  • Cron Enabled: This setting determines if the Conduit block should run during Moodle's cron or not. If enabled, the cron will perform a full synchronization of the Conduit's external tables to Moodle's tables.
  • Remove logs: This configuration helps to manage the size of the Conduit logs. Set whether to delete or archive the logs and then how old the log should be before it is deleted or archived.
    Archived location
    Archived logs are stored in the Moodle data directory under archive/conduit/logs in a zip file. These files can be downloaded via SFTP and extracted locally. The data in the file is all SQL insert statements to add the records back into a database.
4.3.1.3. E-mail

This group of options controls Conduit e-mail notifications of incoming transactions. You can configure what types of transactions to be notified about, which admins are e-mailed, and if you would like to add an attachment to the e-mail of all the transaction logs.

Conduit settings under the email form grouping

  • Transactions: This setting determines what types of transactions cause an e-mail to be sent to the e-mail addresses in the Sent to setting. Options are:
    • None - No transactions are e-mailed
    • File and Web services - Only file and Web services transactions are e-mailed – the administrative cron transactions are ignored
    • Non-Empty - Only transactions where there is a transaction are sent for file, Web services and administrative cron
    • Errors and Warning - Transactions that have warnings and errors are e-mailed
    • Errors Only - Only transactions with errors are e-mailed
    • All - All transaction files are sent to the e-mail addresses, including files, Web services, and administrative cron, regardless of state
  • Send To: What users and e-mail addresses transactions should be e-mailed to
  • Attachment: The transaction records will be attached as a file instead of in the body of the message if this is set. Options are:
    • None - No file is attached to the e-mails sent
    • CSV - Attach the transaction report as a comma separated value file
    • TSV - Attach the transaction report as a tab separated value file
4.3.1.4. Conduit Module Lookup Fields

These fields determine how Conduit looks up information in Moodle and compares it to the information in Conduit.

Conduit settings under the Conduit to Moodle lookup fields form grouping

  • User field: The mapping field to use to link the user's record between Conduit and Moodle. The options are:
    • username
    • idnumber
    • email
  • Course field: The name of the field to use as the course ID in Conduit and in Moodle's
    • shortname
    • idnumber
  • Role field: The name of the field used for identifying the role for enrollment.
    • shortname
    • name
4.3.1.5. User Settings

These settings determine how user data sent to Conduit is processed and what Conduit should do with that information in Moodle.

Conduit settings under the user form grouping

  • When external is removed: Specify if you want to "Keep," "Suspend," or completely "Delete" the Moodle account when you use the "Remove" action for a user. Only suspended users are automatically revived if they reappear in your submitted CSV, XML or Web services files.
  • Password Hash: This setting informs Conduit what type of password to expect in the CSV or XML files or the Web services request. The options are:
    • MD5 Hash
    • Plain Text
  • Create Password: If the password type is set to internal, then this setting determines if a unique password is created and e-mailed to the user's e-mail address in the external database.
  • Create password if it is: Adding a value to this field causes Moodle to only create a password for those users that have their password set to the value. For example: "changeme" will cause all users with the password "changeme" to have a unique password created and e-mailed to them. Leave this blank if you want to change all users' passwords when their account is first created.
  • Force password change: This setting determines if the user is forced to change their password upon their first log in.
  • Update all user accounts: If set to "Yes," Conduit will update all users regardless of the authentication type set.
4.3.1.6. Course Settings

These settings determine how course data sent to Conduit is processed and what Conduit should do with that information in Moodle.

Conduit settings under the course form grouping

  • Auto-Create: Leave this set to "Yes" to have Conduit create your courses in Moodle
  • Auto-Update: If set to "Yes," Moodle will automatically update any settings that exist in Conduit that are set differently inside Moodle
  • Auto-Delete: If set to "Yes," Moodle will automatically delete any courses that you associate with the "Remove" action in Conduit
  • Auto-Archive: If setting is "Yes," then:
    • When a course is deleted by Conduit, the course will be automatically backed up prior to deletion
    • Course is backed up and the backup is moved to SITEFILES/backupdata/autoarchive/
    • All errors are logged and, upon error, course is not deleted
    • Backup output is logged
    • The archive is logged
  • Default category: The default category for auto-created courses that don't have a defined category
  • Auto-create category: If courses are automatically created and they belong to a category that doesn't yet exist in Moodle, those categories can be created automatically if you select "Yes"
  • Category Separator: Leave this empty if you don't want to use subcategories in Conduit. Otherwise, specify the character you are using as the category separator. You need to specify the "path" of the subcategory in the category field as the names of the categories that are separated by the category separator. For example, if we use '/' as the separator, we should have something like category1/category2 (i.e. category2 is inside category1, which is a top level category)
  • Parent Separator: Leave this empty if you don't want to use meta courses in Conduit. Otherwise, specify the character you are using as the separator between courses that will be assigned as the parent of the course being created.
  • Default template: Auto-created courses can copy their settings from a template course. Enter the shortname of the template course here.
  • Restore: This setting determines if Conduit course templating feature is being used. Options are:
    • No
    • Restore from backup - Set this to restore a course from a course backup that is stored in the Course Settings > Backups as the backup file area. The file name in the backups file area must be the exact same as the file name in the Restore template name field of the settings below.
    • Restore current version - Set this if you want to back up and then restore the live or current version of the course that matches either the default template (which is linked to the default template field) or a course's mapped template into auto-created courses (found in the Mappings tab).
  • Restore template name: This is the name of the backup file to use when Restore from backup is set for the Restore setting. For example, if this setting is set to "conduit_template.mbz" and in a course's backup files there is a backup named "conduit_template.mbz", then Conduit will use that backup file as the template. Otherwise, Conduit will create its own backup file to use and name it "conduit_template.mbz" by default.
4.3.1.7. Enrollment Settings

These settings determine how enrollment data sent to Conduit is processed and what Conduit should do with that information in Moodle.

Conduit settings under the enrollment form grouping

  • Auto-unenroll users: If you select "Yes" to enable, then users can be unenrolled from courses. Most common reason for an unenrollment would be if a user's enrollment entry was removed from Conduit they should be unenrolled from Moodle.
  • Control existing matches: This setting is carried over from 1.9 and is no longer in use in Moodle 2.
4.3.1.8. Groups Settings

These settings determine how course group data sent to Conduit is processed and what Conduit should do with that information in Moodle.

Conduit settings under the groups form grouping

  • Auto-create groups: This option will automatically create course groups that do not exist in Moodle, but are present in the Conduit group table. Otherwise, new Conduit group records will be ignored.
  • Auto-update groups: This option will automatically update course groups in Moodle that match updated records in Conduit's group table. Otherwise, updated Conduit group records will be ignored.
  • Auto-delete groups: This option will delete matching groups in Moodle if the group record in Conduit is marked to be deleted. Otherwise, the groups deleted in Conduit will be ignored.
4.3.1.9. Group Members Settings

These settings determine how group membership data sent to Conduit is processed and what Conduit should do with that information in Moodle.

Conduit settings under the group members form grouping

  • Auto-assign members: This option will automatically create course group members that do not exist in Moodle, but are present in the Conduit group members table. Otherwise, new Conduit group member records will be ignored.
  • Auto-remove members: This option will delete matching group members in Moodle if the group member record in Conduit is marked to be deleted. Otherwise, group member deletes in Conduit will be ignored.

4.3.2. Mappings Sub-Tab

The next step is to configure the data field mappings between your CSV or XML files and Conduit. You "map" a field in Moodle by telling it what sort of nomenclature your CSV file is using for column headers (or XML tags for the Web services).

For instance, if you use the term "User" instead of "Username," then you would define this for the Username field. Moodle can then map the action in the export file to the corresponding field in Moodle. It is important for action headings to be in lowercase.

  1. Click on the Mappings link under the Conduit Settings tab.
    settings tab screen shot
  2. Define the mappings between your export and Moodle's Conduit.
  3. If you are starting out with a blank CSV or XML file, get a head start by downloading the template based on these mappings in the "Download example mappings" option.
  4. Don't forget to click the Save changes button when you have finished mapping your fields.
4.3.2.1. Exporting Mapped Data Fields

Each area on the settings page is associated with three different functions in Moodle. For CSV files, the mappings you provide are your column headings. For XML files, these are your tags. Each of the fields marked with an asterisk * are required for Conduit to work. All of the others are completely optional and will vary according to your SIS/CRM/HR/etc. system and/or organizational needs.

If your export does not have specific fields defined already, Moodlerooms recommends that you use the same value as the field name on the settings page. For example, the username field would have the value "username."

However, if you do have specific fields defined as the column headers in your CSV file or the tags in your XML, you'll want to enter those. For example, if your CSV file contains the heading "account name" for the username you want created in Moodle, then enter "account name" in the username field in the "Conduit User" section of the form.

4.3.2.2. Conduit User

The Conduit user mappings affect the auth.csv or auth.xml file by determining what the column headings or mapping tag value attribute should be.

There are three options here for updating user profile information, depending on if you'd like to use Moodle or Conduit as the primary place for changes made to the profile field:

  • Default: Several of the field mappings now have a default field. When Conduit adds a new user to Moodle and does not have a value for a field, it will use the entered default value.
  • Update Moodle every sync: This will update the user's Moodle profile based on changes made in Conduit. Updates will be made anytime the cron is run or your file is uploaded.
  • Update Conduit: This will take changes made using Moodle's edit profile interface and update Conduit with those changes.

user mappings screen shot

The following are the mappable fields with their descriptions and accepted values:

  • username: This is a required field
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Validates that the value is a valid Moodle username
  • idnumber: The idnumber for the user, such as student ID, SSN number (not recommended) or any other value your organization uses to track unique users
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • email: The user's e-mail address, used by Conduit to e-mail a new password
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is an email address
  • externalkey: This value is stored in the Conduit tables but not sent to Moodle. It can be used as an external identification for the user, mostly used for LIS support.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • auth: This is the type of authentication that the user is expected to use when they log in. This is typically used if you are planning to use another authentication plug-in other than Conduit, such as LDAP. Conduit is used by default if no value is passed.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Changes the following values: uib to conduit for backwards compatibility
      • Validates that the value is one of the following: accessid, alfrescosso, cas, conduit, db, efolio, email, fc, gsaml, imap, ldap, liveid, manual, mnet, nntp, nologin, none, pam, pop3, radius, shibboleth, webservice
  • mnethostid: Moodle network host ID – usually not set unless you know your site will be using Moodle networking. If you are, refer to the Moodle networking documentation.
    • Validation
      • Trims strings of white space
      • Validates that the value is a MNet Host ID
  • suspended: This field determines if the user can login or if they account is suspended from user. Suspended accounts have their grades and enrollments kept but the user cannot log in to the site. Valid values are 0 for not suspended and 1 for suspended.
    • Validation
      • Trims strings of white space
      • Validates that the value is an integer
  • password: This is the user's password. Set this to the value in the Settings > User > Create password if it is file if you want an Conduit to generate a password for the user and e-mail it to them. Otherwise, this can be a plain text or MD5 hash.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 32 characters long
      • Validates that the password meets the Site's Password Policy (Settings Block > Site Administration > Security > Site Policy) if the password is plaintext and the Password policy filed is checked.
  • firstname: User's first name
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
  • lastname: User's last name
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
  • emailstop: This is whether the e-mail is enabled or disabled. The values are 0 for enabled and 1 for disabled.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • icq: The user's ICQ number
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 15 characters long
  • skype: The user's Skype account name
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 50 characters long
  • yahoo: The user's Yahoo account name
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 50 characters long
  • aim: The user's AIM account name
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 50 characters long
  • msn: The user's MSN account name
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 50 characters long
  • phone1: The user's main phone number
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 20 characters long
  • phone2: The user's secondary (i.e. mobile phone) number
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 20 characters long
  • institution: The institution the user attends – can be used for other things as desired
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 40 characters long
  • department: The department the user is a part of
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 30 characters long
  • address: The street address for the user
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 70 characters long
  • city: City the user lives in
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 120 characters long
  • country: These are the same values used when determining the country in a user's profile using the Conduit Mapping User Table.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Upper cases strings
      • Validates that the value is one of the following: AF, AX, AL, DZ, AS, AD, AO, AI, AQ, AG, AR, AM, AW, AU, AT, AZ, BS, BH, BD, BB, BY, BE, BZ, BJ, BM, BT, BO, BA, BW, BV, BR, IO, BN, BG, BF, BI, KH, CM, CA, CV, KY, CF, TD, CL, CN, CX, CC, CO, KM, CG, CD, CK, CR, CI, HR, CU, CY, CZ, DK, DJ, DM, DO, EC, EG, SV, GQ, ER, EE, ET, FK, FO, FJ, FI, FR, GF, PF, TF, GA, GM, GE, DE, GH, GI, GR, GL, GD, GP, GU, GT, GG, GN, GW, GY, HT, HM, VA, HN, HK, HU, IS, IN, ID, IR, IQ, IE, IM, IL, IT, JM, JP, JE, JO, KZ, KE, KI, KP, KR, KW, KG, LA, LV, LB, LS, LR, LY, LI, LT, LU, MO, MK, MG, MW, MY, MV, ML, MT, MH, MQ, MR, MU, YT, MX, FM, MD, MC, MN, ME, MS, MA, MZ, MM, NA, NR, NP, NL, AN, NC, NZ, NI, NE, NG, NU, NF, MP, NO, OM, PK, PW, PS, PA, PG, PY, PE, PH, PN, PL, PT, PR, QA, RE, RO, RU, RW, BL, SH, KN, LC, MF, PM, VC, WS, SM, ST, SA, SN, RS, SC, SL, SG, SK, SI, SB, SO, ZA, GS, ES, LK, SD, SR, SJ, SZ, SE, CH, SY, TW, TJ, TZ, TH, TL, TG, TK, TO, TT, TN, TR, TM, TC, TV, UG, UA, AE, GB, US, UM, UY, UZ, VU, VE, VN, VG, VI, WF, EH, YE, ZM, ZW
        Conduit Value Country
        AX Åland Islands
        AF Afghanistan
        AL Albania
        DZ Algeria
        AS American Samoa
        AD Andorra
        AO Angola
        AI Anguilla
        AQ Antarctica
        AG Antigua And Barbuda
        AR Argentina
        AM Armenia
        AW Aruba
        AU Australia
        AT Austria
        AZ Azerbaijan
        BS Bahamas
        BH Bahrain
        BD Bangladesh
        BB Barbados
        BY Belarus
        BE Belgium
        BZ Belize
        BJ Benin
        BM Bermuda
        BT Bhutan
        BO Bolivia
        BA Bosnia And Herzegovina
        BW Botswana
        BV Bouvet Island
        BR Brazil
        IO British Indian Ocean Territory
        BN Brunei Darussalam
        BG Bulgaria
        BF Burkina Faso
        BI Burundi
        CI Côte D'Ivoirev
        KH Cambodia
        CM Cameroon
        CA Canada
        CV Cape Verde
        KY Cayman Islands
        CF Central African Republic
        TD Chad
        CL Chile
        CN China
        CX Christmas Island
        CC Cocos (Keeling) Islands
        CO Colombia
        KM Comoros
        CG Congo
        CD Congo, The Democratic Republic Of The
        CK Cook Islands
        CR Costa Rica
        HR Croatia
        CU Cuba
        CY Cyprus
        CZ Czech Republic
        DK Denmark
        DJ Djibouti
        DM Dominica
        DO Dominican Republic
        EC Ecuador
        EG Egypt
        SV El Salvador
        GQ Equatorial Guinea
        ER Eritrea
        EE Estonia
        ET Ethiopia
        FK Falkland Islands (Malvinas)
        FO Faroe Islands
        FJ Fiji
        FI Finland
        FR France
        GF French Guiana
        PF French Polynesia
        TF French Southern Territories
        GA Gabon
        GM Gambia
        GE Georgia
        DE Germany
        GH Ghana
        GI Gibraltar
        GR Greece
        GL Greenland
        GD Grenada
        GP Guadeloupe
        GU Guam
        GT Guatemala
        GG Guernsey
        GN Guinea
        GW Guinea-Bissau
        GY Guyana
        HT Haiti
        HM Heard Island And Mcdonald Islands
        VA Holy See (Vatican City State)
        HN Honduras
        HK Hong Kong
        HU Hungary
        IS Iceland
        IN India
        ID Indonesia
        IR Iran, Islamic Republic Of
        IQ Iraq
        IE Ireland
        IM Isle Of Man
        IL Israel
        IT Italy
        JM Jamaica
        JP Japan
        JE Jersey
        JO Jordan
        KZ Kazakhstan
        KE Kenya
        KI Kiribati
        KP Korea, Democratic People's Republic Of
        KR Korea, Republic Of
        KW Kuwait
        KG Kyrgyzstan
        LA Lao People's Democratic Republic
        LV Latvia
        LB Lebanon
        LS Lesotho
        LR Liberia
        LY Libyan Arab Jamahiriya
        LI Liechtenstein
        LT Lithuania
        LU Luxembourg
        MO Macao
        MK Macedonia, The Former Yugoslav Republic Of
        MG Madagascar
        MW Malawi
        MY Malaysia
        MV Maldives
        ML Mali
        MT Malta
        MH Marshall Islands
        MQ Martinique
        MR Mauritania
        MU Mauritius
        YT Mayotte
        MX Mexico
        FM Micronesia, Federated States Of
        MD Moldova, Republic Of
        MC Monaco
        MN Mongolia
        ME Montenegro
        MS Montserrat
        MA Morocco
        MZ Mozambique
        MM Myanmar
        NA Namibia
        NR Nauru
        NP Nepal
        NL Netherlands
        AN Netherlands Antilles
        NC New Caledonia
        NZ New Zealand
        NI Nicaragua
        NE Niger
        NG Nigeria
        NU Niue
        NF Norfolk Island
        MP Northern Mariana Islands
        NO Norway
        OM Oman
        PK Pakistan
        PW Palau
        PS Palestinian Territory, Occupied
        PA Panama
        PG Papua New Guinea
        PY Paraguay
        PE Peru
        PH Philippines
        PN Pitcairn
        PL Poland
        PT Portugal
        PR Puerto Rico
        QA Qatar
        RE Réunion
        RO Romania
        RU Russian Federation
        RW Rwanda
        BL Saint Barthélemy
        SH Saint Helena
        KN Saint Kitts And Nevis
        LC Saint Lucia
        MF Saint Martin
        PM Saint Pierre And Miquelon
        VC Saint Vincent And The Grenadines
        WS Samoa
        SM San Marino
        ST Sao Tome And Principe
        SA Saudi Arabia
        SN Senegal
        RS Serbia
        SC Seychelles
        SL Sierra Leone
        SG Singapore
        SK Slovakia
        SI Slovenia
        SB Solomon Islands
        SO Somalia
        ZA South Africa
        GS South Georgia And The South Sandwich Islands
        ES Spain
        LK Sri Lanka
        SD Sudan
        SR Suriname
        SJ Svalbard And Jan Mayen
        SZ Swaziland
        SE Sweden
        CH Switzerland
        SY Syrian Arab Republic
        TW Taiwan, Province Of China
        TJ Tajikistan
        TZ Tanzania, United Republic Of
        TH Thailand
        TL Timor-Leste
        TG Togo
        TK Tokelau
        TO Tonga
        TT Trinidad And Tobago
        TN Tunisia
        TR Turkey
        TM Turkmenistan
        TC Turks And Caicos Islands
        TV Tuvalu
        UG Uganda
        UA Ukraine
        AE United Arab Emirates
        GB United Kingdom
        US United States
        UM United States Minor Outlying Islands
        UY Uruguay
        UZ Uzbekistan
        VU Vanuatu
        VE Venezuela
        VN Viet Nam
        VG Virgin Islands, British
        VI Virgin Islands, U.S.
        WF Wallis And Futuna
        EH Western Sahara
        YE Yemen
        ZM Zambia
        ZW Zimbabwe
  • lang: The user's language to display Moodle string in. This is associated with the language installed on the site, which is usually a language code. If a language pack is installed on the site, these are the acceptable language codes to use.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 30 characters long
        Conduit Value Language
        af_utf8 Afrikaans (af)
        ar_utf8 arabic (ar)
        be_utf8 Belarusian (be)
        bg_utf8 Bulgarian (bg)
        bn_utf8 Bengali (bn)
        bs_utf8 Bosnian (bs)
        ca_utf8 Catalan (ca)
        cs_utf8 Czech (cs)
        cy_utf8 Welsh (cy)
        da_utf8 Danish (da)
        de_du_utf8 German - Du (de_du)
        de_utf8 German (de)
        el_utf8 Greek (el)
        en_us_utf8 English (en_us)
        en_utf8 English (en)
        es_ar_utf8 Spanish - Argentina (es_ar)
        es_es_utf8 Spanish - España (es_es)
        es_mx_utf8 Spanish - Mexico (es_mx)
        es_utf8 Spanish - Internacional (es)
        et_utf8 Estonian (et)
        eu_utf8 Basque (eu)
        fa_utf8 Persian (fa)
        fil_utf8 Filipino (fil)
        fi_utf8 Finnish (fi)
        fr_ca_utf8 French - Canada (fr_ca)
        fr_utf8 French (fr)
        ga_utf8 Gaelic (ga)
        gl_utf8 Gallego (gl)
        gu_utf8 Gujarati (gu)
        he_utf8 Hebrew (he)
        hi_utf8 Hindi (hi)
        hr_utf8 Croatian (hr)
        hu_utf8 Hungarian (hu)
        hy_utf8 Armenian (hy)
        id_utf8 Indonesian (id)
        is_utf8 Icelandic (is)
        it_utf8 Italian (it)
        ja_utf8 Japanese (ja)
        ka_utf8 Georgian (ka)
        kk_utf8 Kaeakwa (kk)
        km_utf8 Khmer (km)
        kn_utf8 Kannada (kn)
        ko_utf8 Korean (ko)
        la_utf8 Latin (la)
        lo_utf8 Lao (lo)
        lt_utf8 Lithuanian (lt)
        lv_utf8 Latvian (lv)
        mi_tn_utf8 Maori - Tainui (mi_tn)
        mi_wwow_utf8 Maori - Waikato (mi_wwow)
        mk_utf8 Macedonian (mk)
        ml_utf8 Malayalam (ml)
        mn_utf8 Mongolian (mn)
        ms_utf8 Malaysian (ms)
        nl_utf8 Dutch (nl)
        nn_utf8 Nynorsk (nn)
        no_gr_utf8 Norwegian (no_gr)
        no_utf8 Norwegian(no)
        pl_utf8 Polish (pl)
        pt_br_utf8 Portuguese - Brasil (pt_br)
        pt_utf8 Portuguese - Portugal (pt)
        ro_utf8 Romanian (ro)
        ru_utf8 Russian (ru)
        si_utf8 Sinhala (si)
        sk_utf8 Slovak (sk)
        sl_utf8 Slovenian (sl)
        sm_utf8 Samoan (sm)
        so_utf8 Somali (so)
        sq_utf8 Albanian (sq)
        sr_cr_bo_utf8 Serbian (sr_cr_bo)
        sr_cr_utf8 Serbian(sr_cr)
        sr_lt_utf8 Serbian (sr_lt)
        sv_utf8 Swedish (sv)
        ta_lk_utf8 Tamil - Sri Lanka (ta_lk)
        ta_utf8 Tamil (ta)
        th_utf8 Thai (th)
        tl_utf8 Tagalog (tl)
        to_utf8 Tongan (to)
        tr_utf8 Turkish(tr)
        uk_utf8 Ukrainian (uk)
        uz_utf8 Uzbek (uz)
        vi_utf8 Vietnamese (vi)
        zh_cn_utf8 Chinese (zh_cn)
        zh_tw_utf8 Chinese (zh_tw)
  • theme: This is the shortname of the theme that the user will use. This is only used if you allow user themes in the site administration.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 50 characters long
  • timezone: This is the user's time zone code. These are the same values used when determining the time zone in a user's profile when using the Conduit Mapping User Table.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
        Conduit Value Timezone Name
        -13.0 UTC-13
        -12.5 UTC-12.5
        -12.0 UTC-12
        -11.5 UTC-11.5
        -11.0 UTC-11
        -10.5 UTC-10.5
        -10.0 UTC-10
        -9.5 UTC-9.5
        -9.0 UTC-9
        -8.5 UTC-8.5
        -8.0 UTC-8
        -7.5 UTC-7.5
        -7.0 UTC-7
        -6.5 UTC-6.5
        -6.0 UTC-6
        -5.5 UTC-5.5
        -5.0 UTC-5
        -4.5 UTC-4.5
        -4.0 UTC-4
        -3.5 UTC-3.5
        -3.0 UTC-3
        -2.5 UTC-2.5
        -2.0 UTC-2
        -1.5 UTC-1.5
        -1.0 UTC-1
        -0.5 UTC-0.5
        0.0 UTC
        0.5 UTC+0.5
        1.0 UTC+1
        1.5 UTC+1.5
        2.0 UTC+2
        2.5 UTC+2.5
        3.0 UTC+3
        3.5 UTC+3.5
        4.0 UTC+4
        4.5 UTC+4.5
        5.0 UTC+5
        5.5 UTC+5.5
        6.0 UTC+6
        6.5 UTC+6.5
        7.0 UTC+7
        7.5 UTC+7.5
        8.0 UTC+8
        8.5 UTC+8.5
        9.0 UTC+9
        9.5 UTC+9.5
        10.0 UTC+10
        10.5 UTC+10.5
        11.0 UTC+11
        11.5 UTC+11.5
        12.0 UTC+12
        12.5 UTC+12.5
        13.0 UTC+13
        99 server time zone
  • picture: The image used for the user
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
  • url: A URL that the user wants to be seen in their profile
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • description: A description of the user – this can include HTML
    • Validation
      • Converts numbers to strings
  • descriptionformat: The text format the description of the user is in.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1, 2, 4
        Conduit Value Summary Format
        0 Moodle auto-format
        1 HTML format
        2 Plain Text Format
        4 Markdown Format
  • mailformat: This is how the user chooses to receive e-mails.
    • Validation
      • Trims strings of white space
      • Validates that the value is 0 or 1
        Conduit Value Mail Format
        0 Plain text
        1 HTML
  • maildigest: This determines if the user receives e-mails in the form of digests from forums.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1, 2
        Conduit Value Mail Digest
        0 No digest (single e-mail per forum post)
        1 Complete (daily e-mail with full posts)
        2 Subjects (daily e-mail with subjects only)
  • maildisplay: This is whether the user's e-mail is displayed or not.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1, 2
        Conduit Value Mail Display
        0 Hide my e-mail address from everyone
        1 Allow everyone to see my e-mail address
        2 Allow only other course members to see my e-mail address
  • htmleditor: This is whether the user uses the HTML editor when adding text to text areas.
    • Validation
      • Trims strings of white space
      • Validates that the value is 0 or 1
        Conduit Value Editor Value
        0 Use standard Web forms
        1 Use HTML editor
  • autosubscribe: This is if the user is automatically subscribed to a forum.
    • Validation
      • Trims strings of white space
      • Validates that the value is 0 or 1
        Conduit Value Subscription Options
        1 Yes (when I post, subscribe to that forum)
        0 No (don't automatically subscribe to forums)
  • trackforums: This is whether the user tracks the number of unread and read forum posts when viewing the forum.
    • Validation
      • Trims strings of white space
      • Validates that the value is 0 or 1
        Conduit Value Forum Track
        0 No (don't keep track of unread posts)
        1 Yes (highlight new posts)
  • imagealt: The alt text to describe the user's picture
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • screenreader: This is whether the user uses a screen reader or not.
    • Validation
      • Trims strings of white space
      • Validates that the value is 0 or 1
TIP: Download Example Mappings
Use this to get a template to base your CSV or XML files on. It will populate the file for you with all your appropriate custom headings.
4.3.2.2.1. Custom Profile Fields

Conduit allows for the creation and update of Moodle's custom profile fields. When a custom profile is created in Moodle, it will be displayed at the bottom of the "User Mapping" area under the Screenreader field.

custom profile what is your favorite food? mapping field under user mappings

Custom profile fields have all the extra information that a profile field will have except that you cannot specify a default value. You will need to instead use the Moodle default value in the profile field interface that Moodle provides.

4.3.2.3. Conduit Course

The Conduit course mappings affect the course.csv or course.xml file by determining what the column headings or mapping tag value attribute should be. There are three options here for updating course information, depending on if you'd like to use Moodle or Conduit as the primary source of authority.

  • Default: Several of the field mappings now have a default field. When Conduit adds a new course to Moodle and does not have a value for a field, it will use the entered default value.
  • Update Moodle every sync: This will update the course settings based on changes made in Conduit. Updates will be made anytime the cron is run or your file is uploaded.
  • Update Conduit: This will take changes made using Moodle's course settings interface and update Conduit with those changes.

course mappings screen shot

The following are the mappable fields with their descriptions and accepted values:

  • shortname: The shortname for the course – this must be unique for each course and is a required field
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
  • idnumber: The idnumber for the course
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
  • externalkey: This value is stored in the Conduit tables but not sent to Moodle. It can be used as an external identification for the course, mostly used for LIS support.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • parent: The identification (based on general settings) of the parent course of the course being created. Used in meta course associations where child enrollments populate into the parent course. See Metacourse for more information about meta courses.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space before and after parent separator in the course settings area.
  • category: The category(s) that the course is in. These should have the same separator as the category separator in the course area of the settings general sub tab.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
  • fullname: The course's full name
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 254 characters long
  • summary: The summary for the course. This can be in HTML.
    • Validation
      • Converts numbers to strings
  • summaryformat: Format that the summary field is in
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1, 2, 4
        Conduit Value Summary Format
        0 Moodle auto-format
        1 HTML format
        2 Plain Text Format
        4 Markdown Format
  • format: The format for the course.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Validates that the value is one of the following: flexpage, folderview, social, topics, weeks
        Conduit Value Course Format
        flexpage Flexpage format
        folderview Folder View format
        scorm SCORM format
        social Social format
        topics Topics format
        weeks Weekly format
  • showgrades: Whether to show the grades to the users or not.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • newsitems: The number of news items displayed.
    • Validation
      • Trims strings of white space
      • Validates that the value is between 0 and 10
  • startdate: The UNIX time stamp for when the course will start
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
  • enddate: Used by certain SIS integrations. Clients should not use this field unless directed by Client Engagement.
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
  • numsections: The number of sections in the topics or weeks format
    • Validation
      • Trims strings of white space
      • Validates that the value is between 0 and 52
  • marker: Marks the current section that is visible to the student. Used mostly in topics and weekly course format and can be no higher than the number of sections.
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
  • maxbytes: The maximum number of bytes a user can upload to a forum in the course.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 8388608, 5242880, 2097152, 1048576, 512000, 102400, 51200, 10240, 0
        Conduit Value Maximum Bytes
        524288000 500MB
        104857600 100MB
        52428800 50MB
        20971520 20MB
        10485760 10MB
        5242880 5MB
        2097152 2MB
        1048576 1MB
        512000 500KB
        102400 100KB
        51200 50KB
        10240 10KB
        0 0 bytes
  • showreports: Whether or not activity reports are available for each participant that show their activity in the current course.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • visible: Whether the course is visible to students or not. You will use 0 for not available to students and 1 for available.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • hiddensections: This determines if sections that are hidden are shown collapsed or completely hidden. Valid values are 0 for shown collapsed and 1 for hidden completely.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • groupmode: This determines if groups are to be used in the course. Valid values are:
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1, 2
        Conduit Value Moodle Group Mode
        0 No groups
        1 Separate groups
        2 Visible groups
  • groupmodeforce: This determines if groups are forced in the course. Values are 0 for no and 1 for yes.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • defaultgroupingid: Default group that a user is assigned to if the course has groups set up.
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
  • lang: This determines if the language for the course is forced. This follows the same languages as the user table mapping and depends on what language packs are installed on the site.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
        Conduit Value Language
        af_utf8 Afrikaans (af)
        ar_utf8 arabic (ar)
        be_utf8 Belarusian (be)
        bg_utf8 Bulgarian (bg)
        bn_utf8 Bengali (bn)
        bs_utf8 Bosnian (bs)
        ca_utf8 Catalan (ca)
        cs_utf8 Czech (cs)
        cy_utf8 Welsh (cy)
        da_utf8 Danish (da)
        de_du_utf8 German - Du (de_du)
        de_utf8 German (de)
        el_utf8 Greek (el)
        en_us_utf8 English (en_us)
        en_utf8 English (en)
        es_ar_utf8 Spanish - Argentina (es_ar)
        es_es_utf8 Spanish - España (es_es)
        es_mx_utf8 Spanish - Mexico (es_mx)
        es_utf8 Spanish - Internacional (es)
        et_utf8 Estonian (et)
        eu_utf8 Basque (eu)
        fa_utf8 Persian (fa)
        fil_utf8 Filipino (fil)
        fi_utf8 Finnish (fi)
        fr_ca_utf8 French - Canada (fr_ca)
        fr_utf8 French (fr)
        ga_utf8 Gaelic (ga)
        gl_utf8 Gallego (gl)
        gu_utf8 Gujarati (gu)
        he_utf8 Hebrew (he)
        hi_utf8 Hindi (hi)
        hr_utf8 Croatian (hr)
        hu_utf8 Hungarian (hu)
        hy_utf8 Armenian (hy)
        id_utf8 Indonesian (id)
        is_utf8 Icelandic (is)
        it_utf8 Italian (it)
        ja_utf8 Japanese (ja)
        ka_utf8 Georgian (ka)
        kk_utf8 Kaeakwa (kk)
        km_utf8 Khmer (km)
        kn_utf8 Kannada (kn)
        ko_utf8 Korean (ko)
        la_utf8 Latin (la)
        lo_utf8 Lao (lo)
        lt_utf8 Lithuanian (lt)
        lv_utf8 Latvian (lv)
        mi_tn_utf8 Maori - Tainui (mi_tn)
        mi_wwow_utf8 Maori - Waikato (mi_wwow)
        mk_utf8 Macedonian (mk)
        ml_utf8 Malayalam (ml)
        mn_utf8 Mongolian (mn)
        ms_utf8 Malaysian (ms)
        nl_utf8 Dutch (nl)
        nn_utf8 Nynorsk (nn)
        no_gr_utf8 Norwegian (no_gr)
        no_utf8 Norwegian(no)
        pl_utf8 Polish (pl)
        pt_br_utf8 Portuguese - Brasil (pt_br)
        pt_utf8 Portuguese - Portugal (pt)
        ro_utf8 Romanian (ro)
        ru_utf8 Russian (ru)
        si_utf8 Sinhala (si)
        sk_utf8 Slovak (sk)
        sl_utf8 Slovenian (sl)
        sm_utf8 Samoan (sm)
        so_utf8 Somali (so)
        sq_utf8 Albanian (sq)
        sr_cr_bo_utf8 Serbian (sr_cr_bo)
        sr_cr_utf8 Serbian(sr_cr)
        sr_lt_utf8 Serbian (sr_lt)
        sv_utf8 Swedish (sv)
        ta_lk_utf8 Tamil - Sri Lanka (ta_lk)
        ta_utf8 Tamil (ta)
        th_utf8 Thai (th)
        tl_utf8 Tagalog (tl)
        to_utf8 Tongan (to)
        tr_utf8 Turkish(tr)
        uk_utf8 Ukrainian (uk)
        uz_utf8 Uzbek (uz)
        vi_utf8 Vietnamese (vi)
        zh_cn_utf8 Chinese (zh_cn)
        zh_tw_utf8 Chinese (zh_tw)
  • theme: This determines if a theme is forced for the course. It follows the same valid values as the user mapping theme and is dependent on the themes installed on the site.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Validates that the value is one of the following: base, anomaly, afterburner, canvas, express, standard, magazine, formal_white, boxxie, serenity, leatherbound, binarius, nonzero, sky_high, arialist, overlay, nimble, fusion, brick, mrmobile, formfactor, flexpage, standardold, cherub
  • requested: Whether the course was requested by a student or teacher rather than created by an administrator.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • enablecompletion: Turns on or off the course completion tracking for the course.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • completionstartonenrol: Enabled course completion based on when the user is enrolled in the course as opposed to the Date setting for the course completion settings.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • completionnotify: Enabled or disable notifications for completion.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
  • coursedisplay: This setting determines whether the whole course is displayed on one page or split over several pages. The setting has no affect on certain course formats, such as SCORM and folderview format.
    • Validation
      • Trims strings of white space
      • Validates that the value is 0 or 1
        Conduit Value Moodle Group Mode
        0 Show all sections on one page
        1 Show one section per page
  • coursetemplate: This field is where you add the shortname for the master course. The new course will be created from a backup of this master course
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
4.3.2.4. Conduit Enrollments

The Conduit enrollments mappings affect the enroll.csv or enroll.xml file by determining what the column headings or mapping tag value attribute should be.

enrollments mappings area

The following are the mappable fields with their descriptions and accepted values:

  • externalkey: This value is stored in the Conduit tables but not sent to Moodle. It can be used as an external identification for the enrollment, mostly used for LIS support.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • coursekey: This is mapped to the primary identification of the course in Conduit. Usually this is either the short name or ID number for the course.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
  • userkey: This is mapped to the primary identification of the user in Conduit. Usually this is either the user name, ID number or e-mail for the user.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Validates that the value is a valid Moodle username
  • rolekey: The short name for the role of the user being enrolled in the course. This field in the export should have a value of the short name for any of the roles on the site. ** ** Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
        Conduit Value Moodle Fullname
        manager Manager
        coursecreator Course Creator
        editingteacher Teacher
        teacher Non-Editing Teacher
        student Student
        guest Guest
        user Authenticated User
  • status: The status of the enrollment
    • Validation
      • Trims strings of white space
      • Validates that the value is 0 or 1
        Conduit Value Moodle Value
        0 Enabled
        1 Disabled
  • timestart: A UNIX time stamp for the date and time when the user should be added to the given role
    • Validation
  • timeend: A UNIX time stamp for the date and time when the user should be removed from the given role
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
Note
You can map multiple fields in Conduit to one data field in your export. For example, if you want the e-mail and username to be the same, you could use "e-mail" as the mapping for both fields.
4.3.2.5. Conduit Role Assign

The Conduit role assign mappings affect the role_assign.csv or enroll_assign.xml file by determining what the column headings or mapping tag value attribute should be.

role assignments field mapping form grouping

The following are the mappable fields with their descriptions and accepted values:

  • externalkey: This value is stored in the Conduit tables but not sent to Moodle. It can be used as an external identification for the role assignment, mostly used for LIS support.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • context: This is mapped to identify the type of enrollment coming in. This mapping is optional and if left blank, then it will default to course enrollments.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Validates that the value is one of the following: user, course
  • moodlekey: This is mapped to the primary identification of the course or user in Moodle. If the type is set to "course" then this is either the short name or the ID number of the course. If the type is set to "user," then this is either the user name, e-mail or idnumber of the user.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • userkey: This is mapped to the primary identification of the user in Conduit. Usually this is either the user name, ID number or email for the user.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Validates that the value is a valid Moodle username
  • rolekey: The short name for the role of the user being enrolled in the course. This field in the export should have a value of the short name for any of the roles on the site.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
        Conduit Value Moodle Fullname
        manager Manager
        coursecreator Course Creator
        editingteacher Teacher
        teacher Non-Editing Teacher
        student Student
        guest Guest
        user Authenticated User
  • timestart: A UNIX time stamp for the date and time when the user should be added to the given role
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
  • timeend: A UNIX time stamp for the date and time when the user should be removed from the given role
    • Validation
      • Trims strings of white space
      • Validates that the value is positive integer (zero or greater)
4.3.2.6. Conduit Parent Role Assignment

In order to set up conduit to create parent access you need to do following:

  1. Create an account for a parent - if you are using any type of authentication (LDAP, CAS, etc.) but you do not authenticate parents' accounts against it, you can simply set up their authentication as manual.
  2. Create Parent/Mentor role, available in the user context and set up with the permissions you want. Click here to learn more
  3. Go to Conduit>Settings>Mappings scroll down to the section Conduit Role Assignments. Use this area to assign a parent/mentor/guardian to a student.
Field Maping Comments
externalkey leave empty It can be used as an external identification for the role assignment, mostly used for LIS support.
context context You would be using "user" as a context to assign a parent.
moodlekey student_account Under the Conduit Settings tab see what you are using as a unique identifier for your users. Can be an e-mail, idnumber, or username. Set this accordingly - this is your student account. (primary key you selected)
userkey parent_account This is the lookup field for your parent/mentor account. Can be e-mail, idnumber, or username. *(primary key you selected)
rolekey role You may use name or short name for a role, see under Settings what lookup field you have decided on. (primary key you selected)
timestart At your discretion If you need to specify the period of time for a parent to have access to the student's information, you may set this up. Has to be in UNIX format.
timeend At your discretion If you need to specify the period of time for a parent to have access to the student's information, you may set this up. Has to be in UNIX format.
Note
User lookup field would be the same for all the users in the system despite the role they may have.

All the mappings can be changed to match your needs.
Once you set this up, you can download the csv headers file. The csv file would look as follows (assuming you have e-mail as key field):

action context student_account parent_account role
create user student@email.com parent@email.com parent

Use Operations tab to do the testing of the file.
If everything was setup correctly, the parent will be assigned to a student. At this point you can add the Mentees block to the parent's page so they could easily navigate to the student they needed.

4.3.2.7. Conduit Groups

The Conduit groups mappings affect the groups.csv or groups.xml file by determining what the column headings or mapping tag value attribute should be.

group mapping form group area

The following are the mappable fields with their descriptions and accepted values:

  • externalkey: This value is stored in the Conduit tables but not sent to Moodle. It can be used as an external identification for the group, mostly used for LIS support.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • coursekey: This is mapped to the primary identification of the course in Conduit. Usually this is either the short name or the ID number of the course.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • groupkey: This is mapped to the name of the group
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • newgroupkey: This is used to replace the name column with the new name as the name of the group in Conduit and Moodle
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • idnumber: The id for the group
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 100 characters long
  • description: This is mapped to the description of the group
    • Validation
      • Converts numbers to strings
  • descriptionformat: The format of the description field
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1, 2, 4
        Conduit Value Summary Format
        0 Moodle auto-format
        1 HTML format
        2 Plain Text Format
        4 Markdown Format
  • enrolmentkey: Enrollment keys allow users to enroll themselves into a course. Usually there is one key for the whole course defined in the course settings. However, if you define a group enrollment key, then not only will entering that key let the user into the course, but it will also automatically make them a member of the specific group.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 50 characters long
  • hidepicture: This determines if the group picture is hidden. Valid values are 0 for visible or 1 for hidden.
    • Validation
      • Trims strings of white space
      • Validates that the value is one of the following: 0, 1
4.3.2.8. Group Members Mappings

The Conduit group members mappings affect the group_members.csv or group_members.xml file by determining what the column headings or mapping tag value attribute should be.

group members mapping form group area

The following are the mappable fields with their descriptions and accepted values:

  • externalkey: This value is stored in the Conduit tables but not sent to Moodle. It can be used as an external identification for the group members, mostly used for LIS support.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • coursekey: This is mapped to the primary identification of the course in Conduit. Usually this is either the short name or the ID number of the course.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long
  • userkey: This is mapped to the primary identification of the user in Conduit. Usually this is either the user name or the ID number for the user.
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Lower cases string
      • Validates that the value is a valid Moodle username
  • groupkey: This is the name of the group the user is being created in
    • Validation
      • Converts numbers to strings
      • Trims strings of white space
      • Validates that the value is less than 255 characters long

4.3.3. File Location and Names

The File area is where you define the location of your CSV files and optionally customize the names of your CSV files.

  1. Click the File link under the Settings tab.
    settings tab screen shot
  2. Enter the absolute file path to the directory that you will SFTP the CSV files to. This should be provided to you by a Moodlerooms employee and will look like "/clients/yoursitename/conduit" - this path may be different according to your customization.
  3. If your CSV files use a different naming structure than the Conduit default (auth.csv, course.csv, enroll.csv, role_assign.csv, groups.csv and group_members.csv), type in the file names you use here.
  4. Files settings screen shot

  5. Lastly, be sure to click Save Changes.
  • File Directory: The SFTP directory that Conduit cron looks at for the CSV or XML files to process
  • Users File Name: The file name that Conduit looks at for user processing
  • Courses File Name: The file name that Conduit looks at for course processing
  • Enrollments File Name: The file name that Conduit looks at for enrollments processing
  • Role Assignments File Name: the file name that Conduit looks at for role assignments
  • Groups File Name: The file name that Conduit looks at for groups processing
  • Group Members File Name: The file name that Conduit looks at for group members processing

5. Course Categories

5.1. Overview

The Courses Available to You block is designed to provide an alternative and more flexible solution to access courses within a category or that a student is enrolled in. The block displays courses within a specific category or the whole site, in an AJAX expandable tree format or a static nested list format. In the site administration area the block is referred to as Course Categories.

5.2. Benefits

The benefits of the Course Categories (Courses Available to You) block are:

  • Alternative display of courses and categories
  • Multiple views into the courses within multiple areas
  • Expanded display options allow the administrator or teacher to determine how they want course information displayed

5.3. Usage Scenarios

5.3.1. Navigation of Course in Flexpage Format

In this scenario, one block is placed on the page and allows the student or teacher to navigate to all courses they are enrolled in. Changing the title of the block and choosing to make it expandable or not is optional, depending on the site administrator's preference.

5.3.2. Display Multiple Course Categories/Programs on a Page

In this scenario, multiple instances of the block are added to a page. The Category Display Start setting is used only to display courses within a specific category or categories. Each block should have a different block title to differentiate the content of the blocks. These blocks can be expandable or not, depending on how the user wants the courses to be displayed.

5.4. Teacher Documentation

The Course Categories block is mostly used by site administrators to provide users with course navigation. This can be used for the same purpose by teachers or program directors. Each instance of the block has its own settings, and multiple blocks can be placed on a page. It is recommended that each block has a different title to help differentiate between the content. The Category Display Start setting for the block can be used to display courses in specific programs or degrees.

5.4.1. Block Views

The Use expandable categories setting for the block allows the block to be displayed in multiple views. These views provide flexibility in how the block is used in a course.

5.4.1.1. Expandable

The expandable view of the block provides a plus/minus icon for each category or sub category within the category selected. Expanding a category will display all courses within that category, depending on the other settings for the block. This provides a quick view of the courses being used.

5.4.1.2. Not Expandable

The "not expandable" view of the block displays all categories, sub categories and courses in an expanded format. This provides an overall listing of courses and can be used with course descriptions to provide a course and category view of the courses the student is enrolled in.

5.4.2. Block Settings

  • Block Title: Title of the block displayed to the user Default: Courses Available To You
  • Category Display Start: The top category from which to start the display of courses Default: All Categories
  • All classes visible: Should all visible classes be displayed, or only classes the current user is enrolled in? Default: No
  • Class Display Name: Which field from the class should be displayed as the class name in the block? Default: Full name
    • Short name: Display the course short name
    • Full name: Display the course full name
  • Use expandable categories: Display categories in an expandable and contractable format Default: Yes
  • Metacourses are visible: Should the block display metacourses or keep them hidden? Default: No
  • Show all Categories: Show all visible categories whether or not the user is enrolled in them Default: No
  • Display the category description: Display the category description below the category name Default: No
  • Show Hidden Categories: Shows all visible classes under hidden categories Default: No
  • Show sub categories: Should sub categories be shown? Default: Yes

5.5. Global Settings

  • Block Title: Title of the block displayed to the user Default: Courses Available To You
  • Category Display Start: The top category from which to start the display of courses Default: All Categories
  • All classes visible: Should all visible classes be displayed or only classes the current user is enrolled in? Default: No
  • Class Display Name: Which field from the class should be displayed as the class name in the block? Default: Full name
    • Short name - Display the course short name
    • Full name - Display the course full name
  • Use expandable categories: Display categories in an expandable and contractible format Default: Yes
  • Metacourses are visible: Should the block display metacourses or keep them hidden? Default: No
  • Show all Categories: Show all visible categories whether or not the user is enrolled in them Default: No
  • Display the category description: Display the category description below the category name Default: No
  • Show Hidden Categories: Shows all visible classes under hidden categories Default: No
  • Show sub categories: Should sub categories be shown? Default: Yes

6. Course Completion Status

6.1. Overview

The Course Completion Status block is used to provide students and teachers with access to the course completion tracking report. For the student, the block provides a simple view of their course completion status and what criteria have been met and what criteria need to be met for the course to be considered complete. For the teacher, the block provides access to the full course completion tracking report on all students in the course.

6.2. Student Documentation

The Course Completion Status block provides the student access to both a simple and detailed report of their completion status for the course.

There are eight completion criteria types that a teacher can set in any combination for a course. Those criteria types are:

  1. Course prerequisites: Displayed as Prerequisites completed in the simple and detailed reports. A student is required to meet the completion criteria in different course that has been marked as a prerequisite to the current course in order to have the current course considered complete.
  2. Manual self completion: Displayed as Self Completion in the simple and detailed reports. A student is required to mark a course as complete using the Self Completion block.
  3. Manual completion by: Displayed as Manager, Course creator, Teacher, Non-editing teacher or a custom role name in the simple report and Manual completion by in the detailed report with the role in the Criteria column of the report. A user with the specified role must mark the course complete for a student in order for the course to be considered complete.
  4. Activities completed: Displayed as Activities completed in the simple and detailed reports. A student is required to meet the completion criteria for selected activities in the course. The detailed report will provide the exact activities that must be completed.
  5. Date: Displayed as Date in the simple and detailed reports. A student is required to wait until a date specified by the teacher before the course can be considered complete. The detailed report displays the specific date.
  6. Duration after enrollment: A student is required to stay enrolled in the course for a set number of days before the course is marked as complete. The detailed report displays the number of days until the course is marked as complete.
  7. Grade: Displayed as Grade in the simple report and Course grade in the detailed report. A student is required to have achieved a total grade above a specified passing percentage in order for the course to be considered complete.
  8. Unenrollment: Displayed as Unenroll in the simple report and Unenrollment in the detailed report. A student is required to wait until they are unenrolled from the course before the course is marked as complete.

6.2.1. Simple Report

The simple report is what a student sees when viewing the Course Completion Status block in a course. The simple report provides a quick view of all the completion criteria for the course and the student's status. Each completion criteria set for the course provides an indicator of status, a "Yes" or "No" or a number of completions out of the total number needed for the specific criteria. Below is an example view:

6.2.2. Detailed Report

From the simple report/block view, click on the More details link to access the detailed report. The detailed report lists the current status of the course completion, if all or just one of the criteria is required for completion, and all criteria for a course to be considered complete.

The detailed report has the following columns:

  • Criteria group: This is one of the eight criteria listed above. Some of the criteria have multiple entries like Activities completed, in which case the second row of this type will display if all of the criteria must be met or just one for the criteria to be completed as a whole.
  • Criteria: This is the specific criteria to be met, such as the activity name, course name or passing grade. This is specific to the criteria group and will link to specific activities and prerequisites to allow the student to directly access these criteria to begin completing them.
  • Requirement: This specifies how the criteria are completed. This can either be a date, a grade value, or someone marking the criteria complete.
  • Status: Status is used to show the status of activities and prerequisites completed to allow the student to view more details about the completion of those criteria.
  • Complete: This states whether the criterion is completed or not.
  • Completion date: This shows what date the criterion was completed on.

6.3. Teacher Documentation

The teacher simply views a link to the course completion report, similar to below.

Clicking on the View course report link will bring the teacher to the course completion report for all users with a role that has its progress tracked. By default, this is the student role.

The course completion report has three header rows that describe the following:

  • Criteria group: One of the eight criteria the teacher sets in the completion settings page
  • Aggregate type: This field displays how each of the enabled criteria groups combine together to determine if a student has completed the course.
    • Any: The course is marked as complete if any of the criteria for the criteria group have been marked as completed for the student.
    • All: The course is marked as complete if all of the criteria for the criteria group have been marked as completed for the student.
  • Criteria: The specific criteria that must be completed.

After the header rows, the report displays a list of students with a column for each criterion. The Criteria column for the student has a check mark if the criterion has been completed and a blank square if it has not. The Course criteria group displays if the user has completed the course.

6.3.1. Filtering the Report

The course completion report can be filtered on the first letter in the student's first or last name by clicking on the letters at the top and bottom of the report.

6.3.2. Downloading the Report

The report can be downloaded to the teacher's desktop by clicking on the Download in spreadsheet format (UTF-8 .csv) or Download in Excel-compatible format (.csv) links at the bottom of the report.

7. Course Converter

7.1. Overview

The Course Converter block was developed to assist clients in migrating course content from other learning management systems to Moodle and speed up the transition process. The converter currently supports courses from the following learning management systems:

  • Blackboard (versions 6, 7, 8, 9 and 9.1)
  • ANGEL (versions 7.2, 7.3 and 7.4)
  • Desire2Learn
  • WebCT (versions 4 and 6)

7.1.1. Related Features

7.2. Changes

7.2.1. From Joule 1.x to Joule 2

  • New Manage converted files tab to display all Moodle 1.9 backup files and allow them to be downloaded or deleted
  • At this time, the Course Converter block converts to a Moodle 1.9 backup file, not a Moodle 2 backup file.
  • Moodle 1.9 backup files cannot be restored directly from the Course Converter block anymore – they must be converted to a Moodle 2.0 backup file.

7.2.2. Joule Summer 2011 Patch Release

  1. Added support for Blackboard 9.1 exports

7.3. How to Export Courses from Your LMS

7.3.1. ANGEL

7.3.1.1. What Will a Migrated Course Look Like

Angel lessons are converted as Topics formatted courses with sections.

7.3.1.2. Content Items Are Converted To
Angel Moodle
Drop Box Advanced Upload Assignment
Assessment Quiz
Form Questionnaire
SCORM SCORM
Folder Label
HTML Label
File Resources (files, links, etc)
Page Resources (files, links, etc)
Link Resources (files, links, etc)
Syllabus Resources (files, links, etc)
Toollink Resources (files, links, etc)
Discussion Forum Forum
Blog Forum
Wiki Wiki
7.3.1.3. Question Types Are Converted To
Angel Moodle
Essay Essay
Matching Matching
Multiple Choice Multiple Choice
Multiple Select Multiple Choice
Fill in the bank Embedded Answers (Cloze)
Short Answer Essay
True/False True/False
Algorithmic Calculated
7.3.1.4. What Is Not Converted
7.3.1.5. How to Export a Course for Conversion
7.3.1.5.1. ANGEL 7.2 and 7.3

Use the ANGEL Export Wizard to export the course as an ANGEL Archive.

  1. Log in to ANGEL
  2. Navigate to the course home page
  3. Click on the Manage tab
  4. Click on the Export Wizard link under the Data Management block
  5. Click the Angel Archive link
  6. Click the Export button
  7. Download the export once finished
7.3.1.5.2. ANGEL 7.4

Use the ANGEL Export Wizard to export the course as an ANGEL Archive.

  1. Log in to ANGEL
  2. Navigate to the course home page
  3. Click on the Manage tab
  4. Click on the Export Console link under the Data Management block
  5. Click the Angel Format link
  6. Click the Export button
  7. Download the export once finished

7.3.2. Blackboard

7.3.2.1. What a Migrated Course Will Look Like

Blackboard courses can be converted to a Topics formatted course in Moodle. Blackboard exports organize content into folders, and Moodlerooms converts these folders into a section and label for each folder. The top folder is converted to a Moodle topic.

7.3.2.2. Content Items Are Converted To
Blackboard Moodle
Assessment Quiz
Folder Label
Question bank Question bank
File Resources (files, links, etc)
External Link Resources (files, links, etc)
Page Resources (files, links, etc)
Staff Info Resources (files, links, etc)
Discussion Board Forum
Calendar item Event (course)
Drop Box Assignment
Most activities' visibility statuses (hidden or visible) are converted and assigned properly in Moodle.
7.3.2.3. Question Types Are Converted To
Blackboard Moodle
Numeric Numerical
Essay Essay
Short Response Essay
Matching Matching
Multiple Answer Multiple Choice (multiple answers allowed)
Multiple Choice Multiple Choice (one answer allowed)
Fill in the bank Short Answer
Fill in the bank Embedded Answers (Cloze)
True/False True/False
7.3.2.4. What Is Not Converted
  • File upload question type is not supported in Moodle. It is best if an instructor converts this to an Advanced Assignment.
7.3.2.5. How to Export a Course for Conversion
7.3.2.5.1. As a Blackboard Course Archive
  1. Log in to the Blackboard site
  2. Navigate to the course
  3. Under the My tab, click the Control Panel link
  4. Under the Course Options area, click the Archive Course link
  5. Click the Export button or download an already created export
  6. Under export, check the checkbox under the select course materials you want to export
  7. Click the submit button
  8. Click the Ok button
  9. Wait for the e-mail to arrive
  10. Click the link to the export
  11. Download the export
7.3.2.5.2. As a Blackboard Course Export
  1. Log in to the Blackboard site
  2. Navigate to the course
  3. Under the My tab, click the Control Panel link
  4. Under the Course Options, area click the Export Course link
  5. Click the Export button or download an already created export
  6. Under export, check the checkbox under the select course materials you want to export
  7. Click the Submit button
  8. Click Ok
  9. Wait for the e-mail to arrive
  10. Click the link to the export
  11. Download the export

7.3.3. Desire2Learn

7.3.3.1. What Will a Migrated Course Look Like

Desire2Learn content modules are converted as topics/sections, aka all Quizzes are under the topic Quizzes.

7.3.3.2. Content Items Are Converted to
Desire2Learn Moodle
Survey Quiz
Quiz Quiz
Question Bank Question Bank
Files or other content items Resources (files, links, etc)
Discussion Board Forum
Drop Box Advanced Upload Assignment
7.3.3.3. Question Types Are Converted to
Desire2Learn Moodle
Long Answer Essay
Matching Matching
Multiple Choice Multiple Choice
Multiple Select Multiple Choice
Fill in the bank Embedded Answers (Cloze)
Ordering Embedded Answers (Cloze)
Short Answer Embedded Answers (Cloze)
True/False True/False
7.3.3.4. What Is Not Converted
  • Question Type Likert
  • Question Type Arithmetic
  • Question Type Significant figures
  • Question Type Multiple Short Answer
7.3.3.5. How to Export a Course for Conversion
  1. Log in to the Desire2Learn site
  2. Navigate to the course you want to export
  3. Click the Edit Course button
  4. Click the Import / Export / Copy Components link under the Tools section of the page
  5. Select the Export Components option and check the Include course files in the export package checkbox.
  6. Click the Next button
  7. Check the Select All Components checkbox
  8. Click the Next button
  9. Click the Next button after verifying all settings
  10. The course will begin exporting at this time
  11. Once the export is finished, click the Done button
  12. Click the Click here to download the export ZIP package link
  13. Depending on your browser, select the location locally to download the ZIP file to.

7.3.4. WebCT 4

7.3.4.1. What Will a Migrated Course Look Like

WebCT 4 content modules are converted as topics/sections. Content module headers/footers are converted to labels and placed in the corresponding topics.

7.3.4.2. Content Items are Converted to
Web CT Moodle
Self Test Quiz
Quiz Quiz
Question Bank Question Bank
Image Database Database Activity
Glossary Glossary
Web content Resources (files, links, etc)
Discussion Forum
Calendar Events
Syllabus Resource
Assignment Assignment
Chat Chat
7.3.4.3. Question Types Are Converted to
Web CT Moodle
Numerical Calculated
Paragraph Essay
Matching Matching
Multiple Choice Multiple Choice
Short Answer Short Answer
7.3.4.4. What Is Not Converted
  • No user information is converted using the batch course conversion tool. For example, discussions and chats are converted, but no user posts (including the instructor’s posts) are converted.
  • Whiteboard does not convert
7.3.4.5. How to Export a Course for Conversion

The Moodlerooms WebCT converter expects WebCT courses to be exported via WebCT's "IMS Content Migration Utility" (CMU). This comes bundled with WebCT CE 4.1, and can only be used by an administrator. (For WebCT CE 4.0, the script was only available as a separate download, which is apparently no longer available.)

7.4. Administrator Documentation

The Course Converter block can only be added at the site level and be used by site administrators to convert course backup files from other learning management systems to Moodle 1.9. The block is separated into three areas:

  • Convert: Used to convert uploaded LMS course backup files to Moodle 1.9
  • Manage File: Used to upload, download and delete the other LMS course backup files
  • Manage Converted Files: Used to download or delete converted Moodle 1.9 course backup files and logs. They can only be restored through the Convert 1.9 to 2.0 backups process at this time.

Block view at the site level

7.4.1. To add the Course Converter block to your site, do the following:

  1. On the site's home page, turn editing on.
  2. In the Add a Block drop down menu, choose Course Converter.
  3. Click on a link within the block to begin the course conversion process. If you find yourself on the wrong tab, look towards the top and click on the correct tab.

7.4.2. Managing Uploaded LMS Backup Files

The Manage files area of the Course Converter block allows site administrators to view, upload, download and delete LMS course backup files. The page is separated into two sections. The Upload a file for Converting area is used to upload a new LMS course backup file while the Uploaded files area allows the Site administrator to view, download and delete the uploaded LMS course backup files. The Uploaded files area only displays ZIP files – all other uploaded files will be ignored.

To upload an LMS course backup file to the site use the Upload a file for converting upload interface. You can either use the Choose a file option to navigate to the file on your hard drive or you can drag and drop the file into the drag and drop area of the file upload interface.

7.4.2.1. Uploading a Course Backup

To upload a single LMS course backup file through the Manage files tab of the Course Converter block, click on the Choose a file... button.

Click the choose a file button in the upload area

Next, click the Upload a file link and then click the Browse button. Select a file from your computer and click the Open button. Click the Upload this file button.

Select upload a file and then browse to the file to upload.

Finally, click the Save changes button. The file will be added to the Uploaded files area in alphabetical order.

Saving Changes Saves All Changes on the Page
Clicking the Save changes button of the Manage files page saves all changes on the page. This means any file that is selected for deletion will be deleted, and any file in the File to upload box will be uploaded.
7.4.2.2. Bulk Upload Course Backups via SFTP

The LMS course backup files can be uploaded to your Joule site in batch or one at a time using your favorite FTP/SFTP program. The following are a few recommended SFTP programs:

First, connect to your SFTP account using the information provided by a Moodlerooms employee. You will initially be placed in a Clients directory. From here, navigate to /clients/<yoursitename>/block_convert directory, and replace the <yoursitename> string with the beginning of the URL for your site provided by Moodlerooms (for example branch.mrooms2.net would use clients/branch/block_convert). This is where you will upload all of your LMS course backup .zip files, and you will see a list of all the files you have uploaded via the Manage files tab's upload interface.

7.4.2.3. Downloading a Course Backup

To download a backup file you have already uploaded, click on the link with the name of the file you want to download. A new window will pop up and, depending on your browser settings, the file will start downloading or ask you where you want to save the file.

click the link to download the file

7.4.2.4. Deleting a Course Backup

To delete a backup file you have already uploaded click the check box to the right of the file name you want to delete. Next click the Save changes button.

Click the checkbox to delete the file

The page will reload and a message stating that the file was successfully deleted will appear.

No confirmation screen is shown when deleting a file, so make sure you have a local backup if you are not sure you want to completely delete the file or if you are concerned you will accidentally delete a file.

7.4.3. Converting Courses

Once LMS course backup files have been uploaded to the Manage files tab, the site administrator is ready to start converting the LMS course backups to Moodle 1.9 course backups. This is done within the Convert tab. The Convert tab is separated into three questions that the site administrator needs to answer when determining how they want to convert files. These questions are:

  1. What LMS version are you converting to what Moodle course format? (This is the Select convert and format)
  2. What LMS backup files are you converting?
  3. Do you need to intervene in the conversion process?

To answer the first question, select the LMS and version you are converting from in the first drop-down menu of the Convert/Format drop downs.

Select the LMS to be converted from

Based on this selection, you will then select the Moodle 1.9 course format to convert to (Folder View, Weekly or Topics course format). Next, you will move on to select which LMS course backup files to convert. Mark the checkbox to the left of each of the LMS course backup files you wish to convert.

Select LMS course backup files to convert

For clients who are uploading files from several LMSs or different versions of an LMS, make sure that the LMS course backup files are named to identify the LMS and version. The Convert tab only allows the selection of one LMS and version to convert from at a time and the tool will try to convert any file selected, even if it is from a different LMS or an incompatible version.

Finally, you will need to determine if the course should be restored into a specific category and, if so, choose the category from the drop down menu. If you want to watch the course conversions, click a Continue button to start the next conversion or if you want to have the block automatically start the next LMS backup file to convert and you can review the logs once all files have been completed. Moodlerooms generally recommends Unattended operation be checked for large batches of courses and it be left unchecked with small batches or when you are retrying a conversion of a file.

Once all the questions have been answered, click the Convert button. The conversion process will then start and you will view the progress of each file's conversion on screen. The Logs will display differently depending on the LMS that the course backup file is from, but everything being converted will display on screen. If you did not check the Unattended operation checkbox, then you will see a link to the converted backup file and to the log file for the conversion of that single file, as well as a Continue button.

Tail end of the on screen display of a single file conversion

Clicking on either file link will download the file locally. Click the Continue button to continue with the next file to be converted. After all files have been converted, a page will be displayed that shows a link to each Moodle 1.9 backup file that was created and a link to the full log of each conversion.

The final page of the process showing the converted files and the log for the entire conversion

Clicking on a link will download the file locally. It is recommended at this time that the site administrator review the log file for any warnings or errors. Clicking the Continue button will return you to the Convert tab to start the process again.

7.4.4. Managing Converted Files

In Joule 2, there is a new tab called Manage converted files in which the site administrator is able to manage all of the Moodle 1.9 course backup files that have been converted. Moodle 2.0 cannot restore a Moodle 1.9 backup file at this time, so instead, to add a converted course to your site, you will need to use the Convert 1.9 to 2.0 backups process to convert the Moodle 1.9 files to Moodle 2.0.

7.4.4.1. Downloading a Course Backup

To download a Moodle 1.9 course backup file, click on the link with the name of the file you want to download. A new window will pop up and, depending on your browser settings, the file will either start downloading or ask you where you want to save the file.

click the link to download the file

7.4.4.2. Deleting a Course Backup

To delete a Moodle 1.9 course backup file, click the checkbox to the right of the file name you want to delete. Next, click the Save changes button.

Click the checkbox to delete the file

The page will reload and a message stating that the file was successfully deleted will appear.

No confirmation screen is shown when deleting a file, so make sure you have a local backup if you are not sure you want to completely delete the file or if you are concerned you will accidentally delete a file.

8. Drag and Drop

8.1. Overview

The Drag and drop feature allows Teachers to easily add files from their computers to sections (topic, week, or folder) in a course. The file is saved and automatically turned into a File resource without needing to manually create a resource or upload the file through the Filepicker.

8.2. Benefits

The benefits of Drag and drop:

New Experience:

  • Instructor can add files to a course by dragging the file onto the browser and depositing in a specific place on the page
  • The file is immediately saved and turned into a "Resource File" without the need of creating a resource type or uploading the file through a filepicker

8.3. Teacher Documentation

8.3.1. Drag and drop block

Before enabling this feature the Drag and drop upload block must be added to the course.

To do this, follow the steps below:

  1. Log in to your Moodle site.
  2. Go to the site homepage and click the Turn Editing On button.
  3. Add the Drag and drop block via the Add block drop down. This will display the Drag and drop upload block.
Note: The file settings will be set as the default settings set at the site level. If you want to change these settings, click the Edit icon next to the file.

drag and drop block image

To add files to your courses, simply grab a file from your computer and drag it to a section in the course. You will see a plus icon with Add file(s) here wherever you can drop a file.

file being added to interface

The file is saved and automatically turned into a File resource without needing to manually create a resource or upload the file through the Filepicker.

file added to course

Note: The File resource name is based on the name of the file dropped into a course, with underscores represented as spaces and without a file extension. For example, the file "Pop_quiz.doc" would become the resource "Pop Quiz." The resources' settings can be edited at any time by editing the File resource.

9. eFolio

9.1. Overview

The eFolio block, in conjunction with the eFolio authentication module, provides a way to link a student's Joule account with their eFolio account. The eFolio block is used to create an initial user account and navigate to eFolio once the user has created an account.

9.1.1. Related Features

9.2. User Documentation

The eFolio block provides the same functionality to all user accounts regardless of role. The block allows a user to create an account on and navigate to the institution's eFolio site.

9.2.1. Connection a User Account to an eFolio Site

Upon first viewing the block on a Joule site, the user will be presented with a single link Connect.

Clicking on this link will prompt the user to verify if they have an existing eFolio account or not.

Clicking the No button will cause the user to go through the account creation process at the institution's eFolio site. After creating an account on the eFolio site, the user will need to click the Login to your account link.

Clicking the Yes button will take the user to the institution's eFolio site login page, where the user will be prompted to enter their existing user name and password.

Once the user has logged into the institution's eFolio site, the user's account is linked between the two systems. The user will then be able to navigate back and forth between Joule and the institution's eFolio site without logging into eFolio again.

9.2.2. Navigating from Joule to eFolio

If the account has been linked to the institution's eFolio site previously, then the user can click the "Go to eFolio" link wherever the eFolio block has been added.

9.2.3. Navigating from eFolio to Joule

Navigating from the institution's eFolio site back to the institution's Joule site starts by clicking on the Accounts tab within the institution's eFolio site.

Next, click on the Services menu tab in the left-hand menu and then the name of the institution's site you wish to return to.

Finally, click on the Go to Moodlerooms Account button.

9.2.4. Disconnecting a Joule Account from eFolio

Disconnecting the user's Joule account from the institution's eFolio site can be done from either the institution's Joule site, or the institution's eFolio site.

  • To disconnect from the institution's Joule site -- Click on the Disconnect link in the block and confirm that you want to disconnect the account by clicking the Yes button. Finally, click the Continue button.
  • To disconnect from the institution's eFolio site -- Click the Accounts tab, then the Services menu tab in the left-hand menu, and then the name of the institution's site from which you want to disconnect. Finally, click the Disconnect button.

10. Flexpage Navigation

10.1. Overview

The Flexpage menu block is a helper block that is used by the Flexpage course format to display Flexpage menus. The Flexpage Menu block is required for the Flexpage course format to work properly. The Flexpage Menu block replaces the Joule 1 page module in Joule 2.

10.1.1. Related Features

10.2. Teacher Documentation

The Flexpage Menu block cannot be directly added to a course page as a block, it must be added through the Flexpage action Add menu via Add > Add existing menu link.

10.3. Permissions

  • Manage Flexpage Menus: allows a user to create, update and delete flexpage menus in a flexpage course
    • Default Permissions
      Role Not Set Allow Prevent Prohibit
      Manager   X    
      Course Creator   X    
      Teacher   X    
      Non-Editing teacher X      
      Student X      
      Guest X      
      Authenticated User X      
    • Risks
      • XSS: Users could add files and texts that allow cross-site scripting (XSS)
  • View Flexpage Menus: allows the user to view flexpage menus in a flexpage course
    • Default Permissions
      Role Not Set Allow Prevent Prohibit
      Manager   X    
      Course Creator   X    
      Teacher   X    
      Non-Editing teacher   X    
      Student   X    
      Guest   X    
      Authenticated User   X    

11. Flexpage Activity

11.1. Overview

The Flexpage Activity block is a helper block for the Flexpage course format and is required for Flexpage to work properly. The block determines how activities added to a Flexpage are displayed. The Flexpage Activity Block in Joule 2 is a replacement for the Page module block in Joule 1.

11.1.1. Related Features

12. Grade Submission

12.1. Overview

The grade submission block is a generalized block that can be used to set midterm and final grades for a course. These grades are intended to be snapshots of the course total grade in the Joule Gradebook and passed to an external system. Currently this block works with the Campus Vue integration block to submit grades for processing by the Campus Vue Integration block.

12.1.1. Related Features

12.2. Teacher Documentation

In order to submit a snapshot of a student's current course total grade to be processed by an external system a teacher must first add the grade submission block to the course. This is done by selecting the Grade Submission block from the drop-down in the Add block block. The grade submission block will then appear:

the grade submission block as it appears in a course with a link to submit grades

From here a teacher clicks the Submit Grades link when they want to submit one or more student grades for processing by an external system. The submit grade form is displayed:

Example submit grades form with the columns for first name/surname current grade midterm 1 and final grade

The submit grades form displays the following information:

  • Populate with course grade drop-down: This drop-down is used to populate one of the midterm grades or final grade with the current grades the students have.
  • Submit Grades table: This table displays the user's first and last name, their current course total grade from the Joule Gradebook, one to six midterm grade columns and a final grade column.
  • Grader report link: This link brings the user to the Joule Gradebook.

To submit a grade a teacher must enter the grade in the submit grades table for the grade column and student row they wish to submit. Depending on the administrative configuration there will be 1 to 7 gradable columns. There will be 0 to 6 midterm grade columns which depend on the administrator to setup and there will always be a final grade column. A teacher can either manually enter a letter grade into the grade field for a grade type and a student or they can use the Populate with course grade drop-down to place the student's current course total grade into the grade column for all students with a course total grade. The current grade column informs the teacher what grade will be copied into when the Populate with course grade drop-down is used.

Only letter grades can be submitted for processing. Any other value not in the course's letter tab (found by going to Course Administration > Grades > letter tab) will produce and error.

Once all the grades the teacher wishes to submit to the external system are added, click the Submit Grades button to submit the grades for processing. Depending on the blocks site settings a teacher may or may not change a grade after it has been sent, please speak to your Site administrator to determine how they have configured the block on your site.

12.3. Global settings

Screen shot of the global settings for the grade submission block as described below

  • Lock Grades: Allow faculty to modify final grades after submission? Default: No
  • Category grade cutoff: You can define one or more cutoff dates, after which midterm grades and final grades will no longer be visible in the grade submission form. A cutoff date is associated with a course category and applies to all courses in that category and its subcategories, unless you define a separate cutoff date for a subcategory.
  • Midterm Grades: Number of midterm grades to display Default: 0
    For Campus Vue integration this should be set to 0 or 1
  • Additional Grade Letters: Enter additional letter grades that can be submitted for mid-term or final grades, separated by commas.

12.4. Permissions

  • Edit: The user is allowed to edit and submit grades for processing.
    • Default Permissions
      Role Not Set Allow Prevent Prohibit
      Manager   X    
      Course Creator X      
      Teacher   X    
      Non-Editing teacher X      
      Student X      
      Guest X      
      Authenticated User X      

13. ILP Integration

13.1. Overview

The Intelligent Learning Platform block is part of Moodlerooms' Datatel integration. The block provides Datatel clients with the ability to set midterm and final grades for a course, send retention alerts, and view the last date of attendance for a student in the course. The midterm and final grades can also be published directly to the Datatel system.

13.2. User Documentation

The ILP Integration block provides students with a link back to the Intelligent Learning Platform from the course. Click the Back to Portal link to return to or access the Datatel Portal (WebAdvisor) from the course.

13.3. Teacher Documentation

The ILP (Intelligent Learning Platform) Integration block looks like the following to a teacher in a course:

Each link in the block provides the teacher with access to a feature of the Intelligent Learning Platform.

13.3.1. Back to Portal

The Back to Portal link provides a direct link back to the Intelligent Learning Platform site collection home page, where users are redirected to their constituency home page. This links displays to students as well.

13.3.2. Retention Alert

The Retention Alert page displays a listing of all students with a link that goes to the Contribute Retention Info page in the Intelligent Learning Platform's WebAdvisor.

If a teacher identifies a potential problem based on assignment scores or attendance, the teacher can click that link to contribute retention information.

Note
This feature is available only if you have licensed the optional Student Retention Alert module.

A retention alert is a feature of the Intelligent Learning Platform and is configured and sent through the Intelligent Learning Platform, not Joule.

13.3.3. Midterm Grades

The Midterm Grades page allows a teacher to submit up to six midterm grades (depending on the site settings for the block) for each student in the course as well as the student's last date of attendance or if the student has never attended the course, just like with the Last Date of Attendance page.

The Populate with course grade... drop-down menu can be used to automatically populate any of the midterm grades with the current course grade as seen in the Current Grade column. Otherwise, the teacher can manually enter a letter grade in each midterm column for the student. Once the teacher has entered all the data for the students, clicking the Submit Grades button will mark the grades and last date of attendance for import into Datatel Colleague.

Grade Validation
When the teacher clicks Submit Grades, the entered grades are checked against both the Moodle grade letters table and the ILP blocks list of additional grade letters. If a submitted grade is not found in either place, an error message is displayed immediately.

13.3.4. Final Grades

The Final Grades page allows a teacher to submit the student's final grade for the course.

The Populate with course grade... drop-down menu can be used to automatically populate any of the midterm grades with the current course grade as seen in the Current Grade column. Otherwise, the teacher can manually enter a letter grade in each midterm column for the student. The Expire Date column is used to set the grade for the student to expire in Colleague. It is recommended that this only be used for incomplete grades. Once the teacher has entered all the data for the students, clicking the Submit Grades button will mark the grades, expire date and last date of attendance for import into Colleague.

Grade Validation
When the teacher clicks the Submit Grades button, the entered grades are checked against both the grade letters table and the list of additional grade letters. If a submitted grade is not found in either place, an error message is displayed immediately.
Locked grades
The site administrator can configure the ILP Integration block to lock the final grades after the teacher has submitted them. If this is configured, the teacher will be unable to change the student's final grade after submission and the Final Grades tab will display the submitted grades to the teacher from then on.

13.3.5. Last Date of Attendance

The Last Date of Attendance page displays a list of all students in the course with a field that allows the teacher to enter a last date of attendance for a student or indicate that the student never attended the class. It also displays a link to create a retention alert just like with the Retention Alert page.

13.3.5.1. Mark Last Attendance Dates for Import into Colleague

To mark the last attendance dates for import into Colleague, follow these steps:

  1. Add a date in the format required by the site settings for the block (MM/DD/YYYY, DD/MM/YYYY, or YYYY/MM/DD) to the text field in the Last Date of Attendance column or check the checkbox in the Never attended column of the page for each student you wish to submit data for.
  2. Click the Submit LDA button.
Date Format
If the teacher enters the date in a format that doesn't match the site settings for the block, then an error will appear at the top of the page. The error will instruct the teacher as to the proper date format to use.

13.3.6. Daily Attendance

The Daily Attendance link goes to an attendance form in WebAdvisor. The behavior depends on whether the Colleague course section uses the positive attendance method for funding accounting, as specified in the Funding Acctg Method field on the Section Financial Info (SFIN) form:

  • If the course does not use positive attendance, the link is to the Attendance Calendar form in WebAdvisor.
  • If the course does use positive attendance, then the link is to a menu in WebAdvisor where the user can access either the Attendance Calendar form or the Attendance Hours form.

13.3.7. ST Gradebook

The site administrator can choose to have teachers submit students' grades and last date of attendance in the ST Gradebook in WebAdvisor. If the site administrator has set this feature, then the ILP Integration block will display the ST Gradebook link instead of the Midterm Grades, Final Grades and Date of Last Attendance links.

Once the teacher clicks on the ST Gradebook link, they will be forwarded to WebAdvisor to enter grades and see a screen similar to below:

13.4. Global Settings

  • Gradebook Application: This setting determines which application is handling the grade reporting. Default: Moodle
    • Moodle
    • ILP ST
  • Retention alert link: This setting determines if a link to the Datatel retention alert will be displayed to the teacher in the course. Default: Yes
  • Daily attendance link: Display the Daily Attendance {} link? Default: Yes
  • Show last attendance: Display Last Date of Attendance links? Default: Yes
  • Lock Grades: Allow faculty to modify final grades after submission? Default: No
  • Date format: This determines the format of the date for date entry boxes. YYYY represents the four digit year, MM represents the two digit month and DD represents the two digit day. Default: MM/DD/YYYY
    • MM/DD/YYYY
    • DD/MM/YYYY
    • YYYY/MM/DD
  • Category grade cutoff: You can define one or more cutoff dates, after which midterm grades and final grades will no longer be visible in either the ILP integration block or the grading form. A cutoff date is associated with a course category and applies to all courses in that category and its subcategories, unless you define a separate cutoff date for a subcategory.
  • Midterm Grades: Number of midterm grades to display Default: 1
  • Additional Grade Letters: Enter additional letter grades that can be submitted for mid-term or final grades, separated by commas.
  • ILP URL: URL to the ILP Portal site
  • Retention alert process ID: The Datatel retention alert process ID Default: CORE-WBCOS067
  • Attendance process ID: The Datatel attendance process ID Default: ST-WESTS041
  • ST Gradebook process ID: The Datatel ST Gradebook process ID Default: ST-GBS005
  • Token: This string is passed along with Web service requests from the Datatel Portal.
  • IP Addresses: This setting determines the IP addresses that the Web services will accept requests from. This can be set to the IP range for the Datatel servers to only allow Datatel servers to request data from the Web services. IP addresses can be a comma separated list of subnet definitions. Subnet definitions can be in one of the following three formats:
    • xxx.xxx.xxx.xxx/xx
    • xxx.xxx
    • xxx.xxx.xxx.xxx-xxx (A range)
  • Datatel Web Service Endpoints
    • http://<site URL>/blocks/intelligent_learning/webservices/course.php
    • http://<site URL>/blocks/intelligent_learning/webservices/enroll.php
    • http://<site URL>/blocks/intelligent_learning/webservices/user.php
    • http://<site URL>/blocks/intelligent_learning/webservices/groups.php
    • http://<site URL>/blocks/intelligent_learning/webservices/groups_members.php

13.5. Permissions

  • Edit: This permission allows the user to access the grade and retention alert link (if enabled).
    • Default Permissions
      Role Not Set Allow Prevent Prohibit
      Manager   X    
      Course Creator X      
      Teacher   X    
      Non-Editing Teacher X      
      Student X      
      Guest X      
      Authenticated User X      

14. Joule Mobile

14.1. Overview

Joule Mobile allows for contact information to be shared between users in the Joule site via the Joule Mobile phone application. In the Joule Mobile block, users have the ability to specify which information they would like to share with other users. Administrators can determine what information should be shared with other users by default. This allows the administrator to create an opt-in policy (all contact data is hidden by default and individual users must enable the sharing of contact data), an opt-out policy (all contact data is on by default and the individual user must disable the sharing of contact data), or some contact data is shared by default and other data must be enabled. If users do not share their e-mail address, then they cannot take advantage of the Dubmenow card exchange platform.

14.2. User Documentation

The block is accessible by all users at all levels (site and course) and allows the user to set their own preferences for what contact data is shared with other users within the Joule Mobile phone application. When you view the block, you are provided with a single link called Update preferences:

Once have entered the preferences, you will be presented with the following options that you can set:

  • Share my email?: This preference determines if your e-mail address is displayed when another user accesses your profile through Joule Mobile. If you choose to share your e-mail address, then you can receive cards from fellow students.
  • Share my address?: This preference determines if your address, city and country are displayed when another user accesses your profile through Joule Mobile.
  • Share my phone numbers?: This preference determines if your phone numbers are displayed when another user accesses your profile through Joule Mobile.
  • Share my IM clients?: This preference determines if your ICQ Number, Skype ID, AIM ID, Yahoo ID and MSN ID are displayed when another user accesses your profile through Joule Mobile.

14.3. Administrator Documentation

The administrative user interface is different from the instructor or student interface only by adding a link to the block's global settings. An administrator will see the following view of the block:

14.4. Global Settings

Joule Mobile's global block settings are used to set the default view permissions for the Joule Mobile phone application for all users on the site as well as the level of course displayed. The global settings are as follows:

  • Share email default: Determines if, by default, the user's e-mail address should be displayed in Joule Mobile. Default: unchecked(No)
  • Share address default: Determines if, by default, the user's address, city and country should be displayed in Joule Mobile. Default: unchecked(No)
  • Share phone numbers default: Determines if, by default, the user's phone numbers should be displayed in Joule Mobile. Default: unchecked(No)
  • Share IM clients default: Determines if, by default, the user's ICQ Number, Skype ID, AIM ID, Yahoo ID and MSN ID should be displayed in Joule Mobile. Default: unchecked(No)
  • Course category depth: When fetching courses for mobile services, limit returned courses to categories of this depth or lower. Additionally, the course will appear underneath the category of the matching depth. Use a depth of zero to include all courses and categories. Use a depth of one or more to dive deeper into sub categories. Default: 0
    • Sample category and course listing:
      • Cat 1
        • Course 1
        • Cat 2
          • Course 2
      • Cat 3
        • Course 3
        • Cat 4
          • Course 4
    • If the course category depth is set to zero, the mobile course listing would look similar to:
      • Cat 1
        • Course 1
        • Course 2
      • Cat 3
        • Course 3
        • Course 4
          **If the course category depth is set to one, the mobile course listing would look similar to:
      • Cat 2
        • Course 2
          • Cat 4
        • Course 4

15. Joule Synchronous Instant Meeting

15.1. Overview

The Joule Synchronous Instant Meeting block is used to create, update and display instant Joule Synchronous meetings for the course. The block uses the settings from the Joule Synchronous activity to create instant meetings for synchronous discussions with users enrolled in the course. This allows for easy one off conversations with students who are online at the time or the creation of instant office hour sessions at a given period of time only if students are interested.

15.2. Benefits

The benefits of the Joule Synchronous Instant Meeting block are:

  1. Easy to create instant synchronous sessions that allow users to:
    1. Screen share
    2. Chat
    3. Voice Chat
    4. Video Chat
    5. Share documents
  2. Recording of meetings
  3. Viewing of expired sessions recordings to allow other students to gain the benefits of an impromptu student teacher conversation.
  4. Easy presentation recording that can be shared with student.

15.3. User Documentation

15.3.1. Current Meetings

Current meetings are Joule Synchronous Instant Meetings that have not passed their duration period. These are meetings that the student maybe able to join if enough seats are available. To access an instant meeting click on the Current tab if it isn't already selected and then click on the name of the meeting you want to join.

The Joule Synchronous instant meeting has 3 views depending upon if the host has joined and if there are seats available. The screens are:

  1. The host has joined
  2. No seats available
15.3.1.1. The Host has Joined

Students will see the Host has not yet joined the meeting message when the host (the user that created the meeting usually the teacher) has not joined the meeting. At this time the student's only course of action is to click the browser's refresh button until they see the message stating they can join the session, the host has joined section for more information on joining a meeting.

15.3.1.2. The Host has Joined

After the host has joined a meeting students will be able to join the meeting. The image above is an example meeting; students will also see a box showing who has joined the meeting already below the link to join the meeting.

15.3.1.3. No seats available

A teacher determines how many seats are available in a Joule Synchronous Instant meeting and it is possible for a teacher to create a meeting that has fewer seats than there are students in the course who wish to join. In this case any student who would be in a seat over the limit will see the message The are more enrolled users than the number of seats reserved for this course. Sorry this meeting is now at capacity. Students will be unable to join even if another student leaves the meeting after the number of available seats has been filled.

15.3.2. Expired Meetings

Expired meetings are Joule Synchronous Instant Meetings that have passed their duration period. These meetings are used to display recordings to a student who was unable to attend the instant meeting. To access an expired meeting click on the link with the name of the meeting you would like to view.

An expired meeting will display the date and time the meeting happened, who attended the meeting and links to view a recording of the meeting.

15.3.3. Viewing Recordings

If a teacher has started a recording for the meeting then the recording will appear in the meeting after it has expired. A student can view the recording from the web by clicking on the name of the record in the Meeting Contents column. This will connect the user to the meeting server and play back the session.

15.4. Teacher Documentation

15.4.1. Create an instant meeting

To create an instant meeting the teacher must:

  1. Click on the Create tab in the Joule Synchronous Instant Meeting block
  2. Click on the Create Instant Meeting link
  3. Add a Joule Synchronous name and description
  4. Adjust the number of seats
  5. Adjust the language
  6. Adjust the invitation type
  7. Save the form

15.4.2. Instant Meeting Settings

15.4.3. General

general activity settings

  • Joule Synchronous Name: The name of the Joule Synchronous session that is displayed in the course, grade book and when viewing the Joule Synchronous meeting. There is a maximum of 45 characters allowed in the name of the meeting. Joule Synchronous also adds a unique ID to the end of the meeting name.
  • Introduction: The introduction text that appears below the activity title when a user is viewing the activity. This is limited to 1,000 characters, including HTML characters.

15.4.4. Meeting

meeting activity settings

  • Start time: The date and time that the meeting starts
  • Duration: How long the meeting will last. Once the duration is met, the meeting's seats will be open for other meetings.
  • Seats: The number of seats that the meeting is expected to use. This counts against the total capacity for the site if using a seminar room license.
    A teacher in the session takes up a seat. Always invite one more than the number of students you wish to attend the session in order to have adequate seats.
  • Conflict Status: This field displays whether the start time, duration and number of seats taken as a whole are in conflict with another meeting. For named organizers, there will be a conflict only if another meeting has been created by this user within the given time period.
  • Language: This sets the language that the menus and interface information within the meeting will be displayed in. The current supported languages are:
    • English
    • Spanish
    • French
    • Italian
    • German
    • Dutch
    • Portuguese
    • Turkish
    • Polish
    • Japanese
  • Access: This determines the type of meeting. Currently, only private meetings are allowed. This means the meeting is not displayed within the Joule Synchronous site, but is displayed within the course. It also means that only users that have been invited to the meeting can join.
  • Invite: This determines which users will be able to access the meeting.
    • All Users in the Course (default) - All users enrolled in the course are allowed to join the meeting, but no invitations will be sent. You must make sure the number of seats you requested accommodates the number of users enrolled in the course.
    • Number, First Come First Served - Any users on the Joule site are able to join the meeting until the specified number of seats is reached. The number of seats is the limiting factor. No users receive an e-mail invite for this option.
    • Specific Users - Add specific users to the list of invitees. After saving the Joule Synchronous activity, a link will display the next time you edit the activity. This link will allow you to select which users to invite to the meeting. Users invited to the Joule Synchronous activity are sent an e-mail invitation.
Joule Synchronous is a seat-based system that allows an allotted maximum number of users to access meetings at any point in time. If your meeting exceeds the number of seats available for the site, then an error will appear that prevents the meeting from being created and warns the user that the meeting exceeds the maximum seats allowed. Instant meetings will be prevented from being created.

15.4.5. Joining an Instant Meeting

To join a meeting the teacher can click on the join link under the join column of the Current tab that appears after the teacher has created an instant meeting.

Alternatively a teacher can click on the instant meeting name in the Current tab in the Joule Synchronous Instant Meeting block.

15.4.6. Recording a Meeting

Joule Synchronous meetings allow for multiple recordings to be created of a meeting. These recording(s) are then showed to the students in the course after the meeting's duration has passed. To start a recording select the Meeting menu in the Joule Synchronous meeting and the check the Record Meeting... menu item.

A pop up window will appear asking for the name of the recording, which will be displayed to the user after the meeting ends, and a summary of the recording, which will not display to the user.

To stop recording a session a host can uncheck the Record Meeting... from the Meeting menu or click Stop recording in the popup the displays after placing the mouse on the Red record circle in the upper right hand corner.

16. Locations

16.1. Overview

A location signifies a building, meeting place, or point of interest to the institution's users. Administrators are able to use the Locations block to create site-wide locations for an institution. Instructors can then associate meeting times with these locations in a course to set up course study groups, office hours and events for an institution. Users can use the Joule Mobile application to view a location's information in the Maps module as well as find directions to that location. Meeting times are presented to the user in Joule Mobile's Course module's information screen, and from here the user can get directions to the location or view it in the Maps module.

16.2. Teacher Course Interface

Adding the Locations block to a course provides an instructor with access to the meetings interface to create, update and delete meeting times.

Clicking on the Meeting link provides the user with access to a list of currently existing meetings for the course as well as the Add a meeting time tab.

Meeting times are unique to the course and must be associated with a location. An administrator must create a location before a meeting time can be created within a course. Meeting times are displayed to students within the Joule Mobile application's Course module's information screen. Students will be able to get directions to the location from within the Joule Mobile application.

16.2.1. Add a Meeting Time

Adding a meeting time to a course consists of completing the form below. A meeting time cannot be created without a location first existing at the site level.

  • Title: (Required) The title of the meeting time, which will be displayed to the students in Joule Mobile on the Course modules information screen. Ex: Office Hours
  • Location: (Required) Select the location that the meeting time is associated with from the drop-down list of all site-wide locations.
  • Hours: The meeting's time and date information as a single line of text. The format of this information is open to however the instructor wants to display this information and will be shown to the student in Joule Mobile on the Course modules information screen. Ex: MWF 3-5 PM
  • Room: The room number or name of the exact meeting area within the location selected, if applicable. Ex: 410A

16.2.2. Update a Meeting Time

In order to update a meeting time, the instructor must click on the name of an existing meeting time in the Meeting Times tab. This will bring the instructor to the Add a meeting time screen with all of the fields pre-filled with the meeting time's previously set information.

16.2.3. Delete a Meeting Time

To delete a meeting time, the instructor clicks on the delete link to the right of the Room column. There will be no verifications before deleting the meeting time — this action is permanent and instantaneous. As soon as the meeting time is removed from the Locations block, the meeting time will no longer be displayed in the Joule Mobile course information screen.

16.3. Administrator Documentation

Adding the Locations block to the site level provides users with the Administrator role with access to view and create locations. The block looks like the image below when added to the site level:

Clicking the Locations link provides the user with a list of all previously created locations. This list will be blank to begin with and a second New Location tab can be used to create a location.

16.3.1. Create a Location

Click on the New Location tab to bring up the location creation screen below:

  • Campus: (Required) A textual description of the overall area the location exists in. Institutions may have multiple campuses that users can toggle between within Joule Mobile's Maps module. Ex: Main Campus
  • Category: A text string that allows locations to be grouped together in the main Locations listing screen. Ex: Dorms
  • Location: The name of the location, which will be displayed to the user in the Joule Mobile application and the instructor when creating meeting times. This should be the common name for the location. Ex: Smith Dormitory
  • Description: A description of the location. For example: "Joseph Smith was an exemplary freshman, so the dorms were named in his honor."
  • Address: The street address for the location – used to provide directions.
  • City: The city associated with the location – used to provide directions.
  • State: The state associated with the location, if applicable.
  • Zipcode: The zip code for the location – used to provide directions.
  • Latitude: This field is required for the pin to be displayed in Joule Mobile's Maps module.
  • Longitude: This field is required for the pin to be displayed in Joule Mobile's Maps module.

16.3.2. Update a Location

To update an existing location click on the name of the location in the Location column. Modify the fields that need to change and click on the Save changes button.

16.3.3. Delete a Location

To delete a location click on the delete link to the right of the location name in the blank column. The location will be deleted without a confirmation page, clicking on the delete link accidentally will cause the location to be deleted.

16.4. Global Settings

  • Campus: Default campus name when creating a new location. Default: Main Campus
  • City: Default city name when creating a new location. Default: Empty
  • State: Default state when creating a new location. Default: Empty
  • Zipcode: Default zip code for the city used when creating a new location. Default: Empty
  • Country: Default country code when creating a new location. Default: United States
  • Zipcode Search Priority: This option returns more precise default geographic coordinates on the map when creating a location that is within the United States. Default: Yes

16.5. Permissions

  • View and Add Locations (block/locations:viewedit_locations): This permission allows the user to view and add locations for the entire site.
    • Default Permissions
      Role Not Set Allow Prevent Prohibit
      Manager   X    
      Course Creator X      
      Teacher     X  
      Non-Editing teacher     X  
      Student       X
      Guest X      
      Authenticated User X      
  • View and Add Meetings (block/locations:viewedit_meetings): This permission allows the user to view and add meetings to a course.
    • Default Permissions
      Role Not Set Allow Prevent Prohibit
      Manager   X    
      Course Creator   X    
      Teacher   X    
      Non-Editing teacher   X    
      Student X      
      Guest X      
      Authenticated User X      

17. Microsoft Live Services

17.1. Overview

The Microsoft Live Services Plug-in for Moodle implements an integration with Windows Live™ Services allowing users to log into courses using their Windows Live ID and display Live Services on a Moodle site. Users can see and create emails and calendar events with Outlook® Live or Windows Live Hotmail®, and access Windows Live Messenger chat, Bing™ search and more within a course.

17.2. User Documentation

Log in to your Moodle site and Navigate to a course with the Microsoft® Live Services block.

microsoft live services block with email

Note: If you do not see the Microsoft Live Services block, a site Administrator or Teacher with editing permissions will need to add the block to the course.

The following links are at the top of the block under your Live ID:

  • Profile: takes you to your my.live.com account profile page.
  • FAQ: opens a list of frequently asked questions that may answer questions you may have.
  • Privacy: opens the Microsoft Live privacy policy.

17.2.1. Search the web

You can search the web using Bing™. Enter text in the box and click on the search (magnifying glass) icon to open results in a new window.

search box with magnifying glass icon for searching terms

Note: You can also highlight any text on the page and click the search icon to search and display results in a new window.

17.2.2. E-mail and Calendar

The Microsoft Live Services block gives you quick access to e-mail and calendar events. You will either have access to Windows Live Hotmail® or Outlook Live and calendar events. New messages and events are displayed in the block right in your Moodle course.

outlook live portion of block with new e-mail messages and new events displayed

The following links are available:

  • Inbox: opens a new window to display your inbox.
  • New E-mail: opens a new message so you can create e-mails from within your course.
  • New Event: opens a new event so you can create new events from within your course.

New messages and Upcoming events are listed in the block so you don't have to navigate away from your course to view them. Simply click on a message or event to view them from within a course.

Messages:

Click New E-mail to open the new message creation window.

pop-up window with new e-mail creation form displayed

From this window you can enter the email address of the person you are sending the e-mail To:, enter the Subject: and compose a message.

Note: In Joule 1.9 you have the option to include resource files from the course as a message attachment by clicking Attach and selecting a file.

Click on a message you wish to read under new messages

e-mail from inbox displayed with message and reply and forward options

From this window you can view previous, next, Reply and Forward the message or click Inbox to open your inbox in a new window.

Events:

Click New Event to open the new event creation window.

window with to

Enter the following information:

  • To: The e-mail address of the person(s) invited to the event.
  • Subject: Description of the event.
  • Message: Personal message to person(s) invited.
  • Start Date: The date the event starts. You can click on a date in the embedded calendar to fill this field.
  • Start Time: The time the event starts.
  • End Date: The date the event ends. You can click on a date in the embedded calendar to fill this field.
  • End Time: The time the event ends.
  • All Day Event: Check to make the event an all day event.

Click Send to send the message or Cancel to discard the event invitation and close the window.

Click on an event under upcoming events to view the event details.

pop-up window with event information displayed

From this window you can view event details for events on your calendar as well as click Inbox to open your inbox in a new window.

17.2.3. Messenger

The Microsoft Live Services block gives you quick access to Windows Live Messenger where you can easily determine who is on/off line and send messages to Teachers and students in the course.

messenger portion of block with Teachers and Classmates lists displayed

Note: Only students and Teachers with a Microsoft Live ID and are enrolled in the course will populate the contacts list.
17.2.3.1. Web Settings

You will need to allow others to see you in your Windows Live Web Settings before you can see and chat with each other.

To allow others to see you follow the steps below:

  1. Log in to Windows Live Messenger Web Settings.
  2. If necessary, log in using your Windows Live ID credentials.
  3. Check Allow anyone on the web to see my presence and send me messages.
  4. Click Save to save your changes.

web settings check box for allow anyone to see me

17.2.3.2. Add/Accept Contacts

You will also need to add classmates/Teachers to your contact list and they will need to accept the invitation.

Note: There are several ways to do this, in this example we are using the Windows Outlook Web Application.

Go to your Contact List and click Add contact....

inbox with add contact link highlighted

The Add Contact pop-up displays.

add contact pop-up with invite button and message box

Enter the IM/e-mail address of the person you wish to add. If you want you can add a personal message to the invite. Click Invite to send the invitation to that person.

Note: The person must accept your invitation and have their Web Settings set to allow others to see them as set above.

You will receive an e-mail if/when someone adds you to their contacts.

Open the e-mail and click the link to View Invitation.

email with link to view invitation to add to contacts

The Contact Requests invitation will display.

invitation with accept all

You have three options:

  1. Click Accept All to accept all invitations.
  2. Click Accept to accept the current invite only.
  3. Click Decline to decline the invite.

Once invitations have been sent/accepted and web settings are set, you will see a list of contacts in the MS Live Services block. Click on a Teacher or Student name to open a new window and chat. 

Note: You may want to use the MSN Messenger Application in addition to the MS Live Services block. The MS Live Services block does not log you into MSN Messenger, so if you are not logged in to your course your classmates will not see you as available to chat. This can be very helpful for a Teacher who stays logged in to MSN Messenger so they are available to students who log in to the course or for students who wish to chat with their classmates without being logged in to the course.

For more information see the links below:

17.3. Administrator Documentation

Log in to a course and navigate to Settings>Site administration>Plugins>Blocks>Microsoft® Live Services.

These settings are required. They allow this Moodle to access the Windows Live™ Services APIs. Before your users can use any Microsoft Live Services Plug-in, you need to register for an Application ID from Microsoft. This Application ID and Secret Key, along with your Moodle's domain name, create a Relying Party Suite (RPS). This allows Microsoft to ensure that users are logging into your Moodle site and allows your users to come back your site after successfully authenticating with their Windows Live ID credentials. Registration takes less than five minutes.

17.3.1. Get Windows Live Application ID and Secret Key

To get a Windows Live Application ID:

  1. Visit http://live.azure.com/
  2. Sign in with your Windows Live ID. If you do not have a Windows Live ID, visit http://windows.live.com to get one free.
  3. After signing in, you need to create a new Azure account if you don't have one yet. The Azure account will be associated to your Windows Live ID.
    • Read the Privacy Statement and then click I Agree.
    • After your account is created, click Continue.
    • You do not need an invitation Token. Click Cancel to skip this step.
  4. Select the Live Services tab on the left.
  5. Click New Service on the upper right. You will be redirected to "Create a new service component" page.
  6. Click Live Services: Existing APIs.
  7. Read the terms of use, and then click I Accept.
  8. Provide the following information:
    • Project Label: Enter a descriptive name for your Moodle site. For example, English Department Moodle.
    • Project Description (optional): Enter a longer description for your Moodle site.
    • Domain: Enter the domain of your Moodle site. For example: www.contoso.edu
      The domain name should contain no slashes ("/"). Domain names such as "http://www.contoso.edu" are invalid.
    • Return URL: Enter the Web address of your Moodle site. For example: http://www.contoso.edu
  9. Click Create.
  10. After this step you will get your Application ID and Secret Key. You can edit or delete this service at any time.

Enter your Application ID and Secret Key in the appropriate fields.

17.3.2. Outlook Live Preparation

Outlook Live is a free e-mail service available to schools enrolled with Microsoft Live@edu. With the Microsoft Live Services Plug-in for Moodle you can easily access the Outlook Live service. In this section you will find steps to set up your Live@edu account and create an impersonation account.

To use Outlook Live with the Microsoft Live Services Plug-in for Moodle, you will need to perform the following configuration steps. If you are not using Outlook Live, skip this section.

  1. Enroll your school in the Live@edu program.
  2. Set up and Impersonation Account.
17.3.2.1. Enroll your school

Register your school’s domain with Live@edu. You can enroll your school in the Live@edu program at http://www.microsoft.com/liveatedu/. After you have enrolled your domain, Live@edu will provide instructions to update your domain mail records to use Outlook Live services as your e-mail service provider.

After you complete the Live@edu enrollment process, you need to create an impersonation account in Outlook Live.

17.3.2.2. Set Up Impersonation Account

Microsoft Live Services Plug-in for Moodle communicates with Outlook live through Exchange Web Services (EWS). Exchange Impersonation is an authorization mechanism designed for use within EWS. An impersonation account can only be created by the administrator. By verifying the impersonation information, the Exchange server knows whether a user is authorized by the administrator.

To set up an impersonation account:

  1. Create a new account for the impersonation role at Outlook Live (https://outlook.com/ecp/). For example, impersonation@yourliveatedu.com. In order to create an account you need to sign in to Outlook Live with the Administrator account.
  2. Install Powershell 2 ctp3 + WinRM 2 ctp3.
    Note: WinRM 2ctp3 requires Windows Vista. Windows 7 testing is not complete.
  3. Run Powershell as administrator. You may need to run the following cmdlet to create a remote session "Set-ExecutionPolicy RemoteSigned". For more information, refer to this Outlook help document.
  4. Run the following cdmlets to complete the setup process:

$LiveCred = Get-Credential # Use your admin account open a new PS session
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri `https://ps.outlookcom/powershell/ -Credential $LiveCred -Authentication Basic `
-AllowRedirection
Import-PSSession $Session
New-ManagementRoleAssignment -Name:EWSImpersionation -Role:ApplicationImpersonation `
-User: impersonation@yourliveatedu.com

Please replace "impersonation@yourliveatedu.com" with the account you set up in step 1.

More details about the cmdlets above can be found here.

17.3.3. Email and Calendar

Give users access to their online email and calendar using Microsoft Office Outlook® Web Access (OWA). The Outlook block allows the user to create a new email or calendar event without leaving the current screen. If more customized options are needed, or if the user wants to see all of the emails or calendar events, the full online application can be launched in a new browser window by clicking the Inbox link. If you choose not to use Outlook live, leave Use Outlook Live unchecked. The e-mail used in the block will be Hotmail® and the calendar will be Windows Live Calendar.

To disable all email and calendar options, uncheck all checkboxes in this section:

  • Use Outlook Live: Check to use Outlook Live for e-mail and calendar. Note: In Joule 2.0 only Outlook Live is supported.
  • Service Account: Enter your complete Windows Live ID. For example: "impersonation@yourliveatedu.com"
  • Password: Enter the password for your impersonation account.
  • Outlook URL: Enter the URL of your Outlook Live domain.
  • Show Email: Check to show e-mail in the Microsoft Live Services Block.
  • Show Calendar: Check to show calendar events in the Microsoft Live Services Block.
Note: In Joule 1.9 you have the option to hide the New E-mail link in the block. Uncheck Show New E-mail Link and it will not display from the block.

In order to obtain your Outlook URL:

  1. Open a new browser window and go to http://www.outlook.com.
  2. Log in using your Windows Live ID credentials.
  3. Copy the URL from your address bar omitting "/owa". For example: "https://pod51004.outlook.com"
For more information about configuring and deploying Outlook Live see http://help.outlook.com/en-us/140/dd277852.aspx.

17.3.4. Windows Live Messenger®

Windows Live Messenger is now available for Moodle. Users can now use the familiar Messenger application for chatting with their classmates, or Teachers.

Check Show Messenger to show Messenger contacts in the block.

17.3.5. Powerset and Bing® Search

Provide your users with the ability to highlight onscreen text and search the web for related information using Powerset and/or Bing search engines from Microsoft. A textbox is also provided for user input so any topic can be searched from Moodle.

If you wish to show search options in the Microsoft Live Services block check Show Search.

If the Enable Bing Search check box is checked, Bing will be the default search. Disabling Bing Search will make Powerset the default search.

Click Save Changes when you are finished.

For more information about Microsoft Live Services for Moodle see http://www.educationlabs.com/Pages/Microsoft_Live_Services_for_Moodle_Getting_Started.htm.

18. Profile Redirect

18.1. Overview

The Profile Redirect block is designed to automatically redirect a user from the front page of the site or the My Moodle page (depending on the location of the block) to a different course. The course that the user is redirected to is based on a value in a mapped profile field that matches the value in a specified field within the course settings. This block, in combination with other Moodlerooms-developed features, provides clients with flexibility in their user's landing page beyond the Moodle/Joule front page and My Moodle page.

18.2. Usage Scenarios

The Profile Redirect block, in combination with other Moodlerooms features, provides clients with flexible options for the default landing page for different users as well as the ability to provide separate groups of users with separate themes. In each scenario below, the user is automatically redirected to the course that is identified in their specified user profile field.

18.2.1. User Redirected to a Department Course

In this scenario, the user is redirected to a department course page, which contains department-specific resources, activities and courses via the Courses Available to You block. This scenario is beneficial for institutions wishing to provide their students with a visual association with the department of their major or with department-specific information within Joule. The course can be branded to the department's specifications using Express.

To configure this scenario, the Profile Redirect block is mapped to the Department field within a user's profile. A course should then be created for each potential option (department) with a matching value in the Short name, Full name, or Course ID fields, depending on the Course Field setting within the Profile Redirect block. Department-specific activities, events and resources can then be added to the course.

It is recommended that the My Courses or Courses Available to You block is then also added to the course to provide the student with access to the courses they are enrolled in, thus making this course a portal-like area. Alternatively, Express menu's %MYCOURSES% variable can be used to create a dynamic menu of the courses that the student is enrolled in. An Express design should be created to brand the course to the specific department, providing the student with visual clues as to what department they belong to.

18.2.2. User is Redirected to an Introduction Course in Their Language

In this scenario, the user is redirected to a course that has been developed in a specific language. This introductory course provides instructions for a user based on the language they have set in the user profile. This scenario is particularly useful for language-oriented institutions or international organizations wishing to provide basic knowledge of the system in the user's native language.

To configure this scenario, the Profile Redirect block's Profile Field is set to match against the Language field within the user's profile. A course should then be created for each potential option (language) with a matching value in the Short name, Full name, or Course ID fields, depending on the Course Field setting within the Profile Redirect block. It is recommended that ID number is used in this scenario, because this field is not displayed to users and the value saved for the Language field in the user profile is not human readable (and thus should not be added to a visible field). The course's language should be set to the same language as the ID number of the course. All content developed in this course should be written in the language of the course.

18.3. Administrator Documentation

The Profile Redirect block consists of the global settings for the block. Once these are set and the block is added to the page that will redirect the user, the block is set and will display something similar to the following, but only for site administrators:

Within the Profile Redirect block settings there is a Default Course Setting field that is used to identify which course the user should be redirected to. The block's Course Field field is used to identify which field within the course settings need to match the value specified in the Profile Redirect block's Default Course Setting field. For example, if the Default Course Setting field is set to Eng101 and the Course Field field is set to "short name," then the Profile Redirect block will redirect the user to the course that has "Eng101" as its short name.

It is recommended that the Profile Redirect block be placed in the upper left-hand corner of the course page. This means it will be the first item loaded after the header and will redirect the user quicker.

Use an Authentication Plug-in
It is recommended that Conduit or some other authentication system be used to create users and set the value for the user's profile field that matches the value set in the Profile Redirect block's Profile Field setting. The user profile field set in the Profile Redirect block's Profile Field setting can be locked for the authentication plug-in used within the authentication plugin's settings page. Locking the field will not allow users to update the profile field manually and cause misdirections.

18.4. Global Settings

  • Profile Field: This is the field in a user's profile that the Profile Redirect block will match against the course field. The user will then be redirected to the corresponding course. If there is not a valid value in the specified profile field, the block will instead redirect the user to the default course identified in the Default Course field. Default: Institution
    • ID number
    • Institution
    • Country
    • City/town
    • Language
    • Department
  • Course Field: This is the field in the course settings that the Profile Redirect block will match against the user's profile field for redirecting. Default: Short name
    • Short name
    • Full name
    • ID number
  • Default Course: This field identifies the course that all non-admin users who do not have a valid value in their profile field will be directed to upon viewing the block. This field should have the short name, full name, or course ID number of the course, depending on the value specified in the Course Field drop-down menu.

19. Self Completion

19.1. Overview

The Self Completion block provides the student with access to mark a course as complete. This block works with the Course Completion tracking settings in a course and requires that a teacher has enabled manual completion for the course.

19.2. Student Documentation

The Self Completion block simply contains a link to manually set the completion status of the course for the student.

Clicking the Complete course... link will bring up a confirmation screen. Click the Yes button to complete the course and the No button to cancel and return to the course.

A course cannot be set to incomplete by a student after it has been marked complete. The Self Completion block will not show up for a student who has already marked a course as complete.

Note
A teacher can delete completion status for all students in a course. Only all students' completion status can't be reset for individual students. If this happens, the Self Completion block will reappear in the course and each student will need to manually mark the course as complete again.

20. Streams and Alerts

20.1. Overview

Joule Streams and Alerts keep users up-to-date on course events and messages by enabling various types of notifications for important events. Teachers and students can customize the types of notifications they wish to receive and when they would like to receive them by updating their message settings. Notifications can be delivered when on and offline via the Activity stream, popup notification, email and alert badge.

20.2. Benefits

The benefits of Streams and Alerts:

New Experience:

  • Place the streams block on your myMoodle page to see the most recent activity from all of your courses (similar to a social network news feed)
  • Glance at the counter on the "Alert badge" to see how many alerts are in your queue
  • Access your alerts by clicking a convenient "Alert badge" in the header
  • Click on links within the streams and alerts to navigate to the triggering course events

More Choice:

  • Choose the events that you want displayed in your streams
  • Select more critical events that you want displayed as course alerts

20.3. User Documentation

20.3.1. Activity Stream

The Activity stream is a live stream of course activity and an easy way to keep track of important course activities. The My home/My Moodle page is the perfect place to add the Activity stream block. This will allow you to view the most recent activity from all of your courses in one place.

Add the Activity stream block to your site home page, if it has not been added already. To do this, follow these steps:

  1. Log in to your Moodle site.
  2. Go to the site homepage and click the Turn Editing On button.
  3. Add the Activity stream block via the Add block drop down. This will display the Activity stream block.

For more information on adding a block, click here.

Streams and Alerts will deliver event information based on the settings in message center preferences. Students can determine their message preferences for Streams and Alerts by clicking My profile settings > Messaging in their Settings block.

settings block image

The Messaging settings allow you to configure your notification methods for event messages. Check the options for Activity stream and Alert badge notification, when logged in, offline, or both for each notification type.

check boxes to enable messages

When selecting what messages to send to the Activity stream and what messages you would like to receive Alerts for, keep in mind that you may want to make important messages Alert notifications and less important messages Activity stream notifications. For example, you may want to know about things like Joule Gradebook messages and messages about a recent activity that has been graded without having to navigate to your Activity stream, if so, set them up as Alert notifications. If there are less important messages, set them up as Activity stream notifications, that way you check them when you have time to review your Activity stream.

Note
Don't forget to scroll down to the bottom of the page and click the Update profile button to update these settings.

Click Visit, or on any link in the Activity stream to navigate to that area in a course.

activity stream with posts alerting user of messages

To see older activities in a stream, just click on the More button in the block. The block will reveal more items for your viewing.

20.3.2. Alerts

Alerts are almost the same as streams. Alerts are triggered by various course events, but are most likely important enough that you want to know about them without having to navigate to the My home/My Moodle page to view the stream. When there is a new alert, the Alert badge will display a number indicating how many alerts are in your queue. The Alert badge is located at the top of the page and is automatically loaded when you use the Express theme. The Alert badge can be moved to a different location on your page by editing your Express theme.

alert badge exclamation point in red

Click on the alert badge to display a list of alerts.

alert menu with alerts listed

Click Remove, Read, or Visit to perform that action on each alert. You can also click on any link in the alert to navigate to that area in the course.

Note
Alerts are removed from the list once they have been read, visited, or removed.

21. Quickmail

21.1. Overview

The Quickmail block enhances the existing communication systems of messaging (one user) and subscribed fourums (all subscribers) by allowing teachers to select customize sets of students.

21.2. User Documentation

Log in to your course and navigate to the Quickmail block. 

Note: If you do not see the Quickmail block, a site Administrator or Teacher with editing permissions will need to add the Quickmail block to the course.

21.2.1. Compose E-mail

Click Compose New Email to open Quickmail's e-mail composition page.

From this page you can click View Drafts and View History to view any drafts you have and history of e-mails you have sent.

21.2.2. Filter and/or Add Recipients

Filter options:

  • Role Filter: if roles are set up in the course this drop-down filters recipients by role. For example: Teacher, Student, etc.
  • Potential Sections: if sections are set up in the course this drop-down filters recipients by section.

Choose users you'd like send a message to using the following options:

  • Add: will add a user(s) that has been selected from the Potential Recipients list.
  • Remove: will remove a user that has been selected from the Selected Recipients list.
  • Add All: will add all users in the Potential Recipients list.
  • Remove All: will remove all users in the Selected Recipients list.
Note: You can add more than one recipient by holding the Ctrl key and clicking on multiple users.

21.2.3. Attachments

Once recipients have been added you can add attachments and compose the message.

Click Add to open the File Picker and attach a file; or alternatively drag file from the computer directly into the files area.

Click Create Folder to add a folder to add multiple files. Enter a folder name and click OK.

Once a folder has been created, click on the folder name and click Add to add files to the folder. Click on the list icon to the right of the folder to Zip, Rename, Move or Delete the folder. You will notice a Path: above the attached files that allows for easy navigation between attachments.

Enter a Subject for the e-mail and compose the message in the text editor.

21.2.4. Signatures

To manage Signatures click the link in the Quickmail block.

The Quickmail Signatures page opens.

Enter a Subject for the signature which will appear in the drop-down menu for selecting signatures. Compose the signature in the text editor, check Default if you wish to use this signature on all messages.

Click Save changes to save the signature or click Cancel to cancel creating the signature.

Select a signature from the Signatures drop-down when composing a message to include one at the bottom of your e-mail.

21.2.5. Send a message

If you would like to Receive a copy of the e-mail click the Yes radio button.

Click Send Email to send the message, click Save Draft to save this message as a draft, or click Cancel to cancel the message and discard it.

21.3. Teacher Documentation

Log in to a course and navigate to the Quickmail block.

There are two options available in the block for Teachers, View History and Configuration, that are not available for students.

Click View History to open the Quickmail history page and display a list of recent sent messages. Click Continue to move to the e-mail composition page.

Click Configuration to open the settings for Quickmail.

Select from the following:

  • Allow students to use Quickmail: select Yes from the drop-down to allow students to use Quickmail.
  • Roles to filter by: select the role(s) available to filter by when creating a message.
    Note: Select more than one role by holding Ctrl and clicking on multiple roles.
  • Add Breadcrumbs to Message Body: check to add breadcrumb links to the site and course at the top of every Quickmail message.
  • Prepend Course name: check to prefix all Quickmail message subjects with the course Short name or ID number.
  • Receive a copy: select Yes to receive a copy of emails sent via Quickmail.

Click Save changes when you are finished.

21.4. Administrator Documentation

Log in to a course and navigate to Settings>Site Administration>Plugins>Blocks>Quickmail.

The Quickmail settings page opens.

Select from the following:

  • Allow students to use Quickmail: select Yes from the drop-down to allow students to use Quickmail.
  • Roles to filter by: select the role(s) available to filter by when creating a message.
    Note: Select more than one role by holding Ctrl and clicking on multiple roles.
  • Add Breadcrumbs to Message Body: check to add breadcrumb links to the site and course at the top of every Quickmail message.
  • Receive a copy: If set to Yes then the creator will receive a copy of the email.
  • Prepend Course name: To attach the shortname of the course to the subject line of the email select Short name from the drop-down menu, alternatively the course ID number can be used.
  • FERPA Mode: Use this setting to define how the Quickmail block will behave when groups are used in a course.

Click Save changes when you are finished.

22. Product Manual Terms of Use

Permission for the use of Product Manual is granted subject to the following terms and conditions:

By accessing this page and using this manual, you agree to and are bound by the terms of this Terms of Use. If you do not agree to all of the terms and conditions contained in the Terms of Use, you are not authorized to use this page or these documents.

In using Product Manual, you agree that you will use them only for their intended purpose and not use them for any purpose that is unlawful or prohibited by these terms. You may not misuse or alter any document in any way, including any derivative work, or reproduce or display these documents outside your enterprise without the express written consent of Moodlerooms.

Except as expressly granted in the Terms of Use, no other permissions, licenses or rights are granted, either express or implied, to the Product Manual, or to any information, data, software or other intellectual property contained therein.

Moodlerooms reserves the right to withdraw the permissions granted herein whenever, in its sole discretion, the use of the Product Manual is detrimental to its interest or, as determined by Moodlerooms, the instructions contained herein are not being properly followed.

Moodlerooms makes no guarantee about the content of the Product Manual. Use of the Product Manual is at your own risk. They are provided “as is” and without warranty of any kind, either express or implied, including, but not limited to implied warranties of merchantability, non-infringement and fitness for a particular purpose.

The Content, Software, Services and all other aspects of this web site are subject to these Terms of Use. Moodlerooms reserves the right to update these Terms of Use at any time without notice to you. The applicable and most current version of the Terms of Use can be reviewed by clicking on the “Terms of Use” hypertext link located at the bottom of our web pages.

Your Rating: Results: PatheticBadOKGoodOutstanding! 4 rates
Adaptavist Theme Builder Powered by Atlassian Confluence