MoodleDocs - User contributions [en]

bootstrap-Theme

2012-09-28T14:33:49Z

Dwahl:

== Twitter Bootstrap Theme==
This page aims to bring together discussions from the themes forum related to the development of a moodle 'base' theme that conforms to the [http://twitter.github.com/bootstrap/ Twitter Bootstrap] coding conventions. There has already been a great deal of work done by individuals within the Moodle community and it's hoped that by formulating this work we may be able to collaborate and build on this.

== Technical Approah ==
There are 5 major categories of development for this theme family:

* Layouts
* Renderers
* Stylesheets
* Javascripts
* Settings (child themes)

=== Layout ===
The General layout will be a 2 column layout based on the [http://twitter.github.com/bootstrap/examples/fluid.html "Fluid" example] providing an "out of the box" responsive grid.

=== Renderers ===
Multiple renderers will be developed to make Moodle output more bootstrap friendly by 1) outputting classes defined in bootstrap.css and 2) outputting semantic HTML exemplified in the bootstrap documentation

=== Stylesheets ===
Bootstrap.css will be the core CSS sheet with adjustments made to reduce re-duplication (like 'reset') and to define Moodle core classes that can't be matched to bootstrap via a renderer

=== Javascripts ===
[http://jshirley.github.com/bootstrap/javascript.html YUI Bootstrap plugins] will be dropped in to the theme in place of the jQuery version(s).

=== Settings ===
On the roadmap: create a child theme (or themes) to provide end users with custom settings, possibly including:

* static or fixed navbar
* light or dark color
* 2 or 3 column layout
* custom logo
* [http://bootswatch.com/ bootswatches]

== Success criteria ==
To have developed a theme that can be used as a base theme, that looks and feels like the default bootsrap interface. (see: [http://twitter.github.com/bootstrap/getting-started.html#examples examples].

==Future developments ==

* To make a responsive version
* Create a library of custom renderers that can be used in themes to make UI changes
* Add theme settings that allow administrators to change the layout of templates through the theme interface.

== Links to Discussions in Forums ==

* [http://moodle.org/mod/forum/discuss.php?d=212222 (re-)bootstrap: work in progress]
* [http://moodle.org/mod/forum/discuss.php?d=212341 Amelia and Cyborg Bootswatches for Moodle]
* [http://moodle.org/mod/forum/discuss.php?d=208162 Bootstrap for Moodle project]

== Resources ==

* [http://twitter.github.com/bootstrap/ Twitter Bootstrap Home]
* [http://jshirley.github.com/bootstrap/javascript.html Bootstrap YUI Plugins]
* [http://bootswatch.com/ Bootswatch]
* [http://bootsnipp.com/ Bootsnipp]

bootstrap-Theme

2012-09-28T14:28:38Z

Dwahl: /* technical Approah */

== Twitter Bootstrap Theme==
This page aims to bring together discussions from the themes forum related to the development of a moodle 'base' theme that conforms to the [http://twitter.github.com/bootstrap/ twitter bootstrap] coding conventions. There has already been a great deal of work done by inderviduals within the moodle community and it's hoped that by formulising this work we may be able to collaborate and build on this.

== Technical Approah ==
There are 5 major categories of development for this theme family:

* Layout
* Renderers
* Stylesheets
* Javascripts
* Settings (child themes)

=== Layout ===
The layout will be a 2 column layout based on the [http://twitter.github.com/bootstrap/examples/fluid.html "Fluid" example] providing an "out of the box" responsive grid.

=== Renderers ===
Multiple renderers will be developed to make Moodle output more bootstrap friendly by 1) outputting classes defined in bootstrap.css and 2) outputting semantic HTML exemplified in the bootstrap documentation

=== Stylesheets ===
Bootstrap.css will be the core CSS sheet with adjustments made to reduce re-duplication (like 'reset') and to define Moodle core classes that can't be matched to bootstrap via a renderer

=== Javascripts ===
[http://jshirley.github.com/bootstrap/javascript.html YUI Bootstrap plugins] will be dropped in to the theme in place of the jQuery version(s).

=== Settings ===
On the roadmap: create a child theme (or themes) to provide end users with custom settings, possibly including:

* static or fixed navbar
* light or dark color
* 2 or 3 column layout
* custom logo
* [http://bootswatch.com/ bootswatches]

== Success criteria ==
* To have developed a theme that can be used as a base theme, that looks and feels like the default bootsrap interface. (see: [http://twitter.github.com/bootstrap/getting-started.html#examples examples].

==Future developments ==
* To make a responsive version
* Create a library of custom renderers that can be used in themes to make UI changes
* Add theme settings that allo administrators to change the layout of templates through the theme interface.

== Links to discussions in forums: ==

* [http://moodle.org/mod/forum/discuss.php?d=212222 re-)bootstrap: work in progress]
* [http://moodle.org/mod/forum/discuss.php?d=212341 Amelia and Cyborg Bootswatches for Moodle]
* [http://moodle.org/mod/forum/discuss.php?d=208162 Bootstrap for Moodle project]

Adding a new course

2012-04-26T05:01:37Z

Dwahl: Undo revision 97261 by Tesolchina (talk)

{{Courses}}

By default a regular teacher can't add a new course. To add a new course to Moodle you need to have either [[Administrator|Adminstrator]], [[Course creator|Course Creator]] or [[Manager|Manager]] rights.

==Adding a course==
To add a course:
*Go to ''Settings>Site Administration>Courses>Add/edit courses''

[[File:Addeditcourses.jpg]]

*Choose the category where you want your course to be. For more information see [[Course categories|Course categories]]
*Click the "Add a new course" button
*Enter the [[Course settings|course settings]], then click the "Save changes" button.
*On the next screen, choose your students/teachers to assign to the course.

==Deleting a course(s)==

A regular teacher can't delete a course. Administrators and managers (i.e. users with a role for which the capability [[Capabilities/moodle/course:delete|moodle/course:delete]] is allowed) can deleted courses. A [[Course creator|Course creator]] can delete courses they have created themselves.

To delete a course (as an administrator or manager):
*Go to ''Settings > Site Administration > Courses > Add/edit courses''
*Click the course's category (to drill down the category tree) and find the course you wish to delete. Or use the "Search course" textbox at the bottom of the category list.
*Click the "X" icon to the right of the course's name. to delete it.

You can delete multiple courses by:
*Creating a new (temporary) category. You can name it "To be deleted".
*Select and '''move''' the "About to be deleted" courses to that category ("To be deleted").
*Delete the category ("To be deleted") and choose "Delete ALL - cannot be undone".

There is no user interface for course creators to delete courses they have created, however they can do so by editing the URL of the course from <nowiki>http://yourmoodlesite.net/course/view.php?id=N</nowiki> to <nowiki>http://yourmoodlesite.net/course/delete.php?id=N</nowiki> (replacing 'view' with 'delete').

==Course requests==

*There is a course request feature which can be enabled by the administrator in ''Settings > Site administration > Courses > Course request''.
*The default category for new courses requested can be selected from this screen, and users who will be notified when courses are requested can also be selected here. (These are users with the capability [[Capabilities/moodle/site:approvecourse|moodle/site:approvecourse]].)

[[File:Courserequest.png]]

*A button will then appear on the All courses page for users to request a new course.

By default, all authenticated users can make course requests (after you have enabled it). It is controlled by the capability [[Capabilities/moodle/course:request|moodle/course:request]].

==Bulk Course Create Options==
As of Moodle 2.2, this is not an out of the box feature.

The main Tracker item: http://tracker.moodle.org/browse/MDL-13114

Some forum discussions:
#Import files to batch create courses and users http://moodle.org/mod/forum/discuss.php?d=27333
#Bulk / automated course creation with phpMyAdmin http://moodle.org/mod/forum/discuss.php?d=27333
#Bulk Course Creation in v1.9 http://moodle.org/mod/forum/discuss.php?d=96622
#Bulk Course Upload tool question http://moodle.org/mod/forum/discuss.php?d=91850#p572909
#Bulk Course Upload tool for Moodle 2.0 http://moodle.org/mod/forum/discuss.php?d=91850&parent=744931
#uploaduser.php enhanced to upload also courses http://moodle.org/mod/forum/discuss.php?d=128317

The latest real lead (as of February 2012) is this:

:''Piers Harding added a comment - 26/Sep/11 3:23 AM Hi -
:This may or may not be of any use to people on this thread, but I create a basic course uploader for 2.x modelled on the user uploader, as I needed something for NZ schools - it's available here https://gitorious.org/moodle-tool_uploadcourse/moodle-tool_uploadcourse for the curious.
:Cheers,
:Piers Harding.'' From the tracker thread MDL-13114

Old module/plugin: http://moodle.org/mod/data/view.php?d=13&rid=395

==See also==

*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=83830 Hide Courses from some users or students] forum discussion

[[de:Kurs anlegen]]
[[es:Cursos_%28administrador%29]]
[[eu:Ikastaroak_%28Kudeatzaileak%29]]

Plagiarism Prevention Turnitin

2010-12-15T08:25:22Z

Dwahl:

{{Moodle 2.0}}
[[Image:Turnitin_admin.gif|thumb|Turnitin administration]]
Location: ''Administration > Plugins > Plagiarism Prevention > Turnitin''

==Activation of your Turnitin Account==
# obtain a Turnitin Subscription from [http://www.turnitin.com www.turnitin.com]
# obtain an API Integration secret key. - once you have a Turnitin Subscription, to obtain this you will need to visit the administration panel inside your Turnitin account. - there may be an extra cost to have API activated on your account, but your account rep should be able to give you details on this.

==Global Configuration of Turnitin==
# Ensure Admin > Server > Environment indicates you have curl installed
# in the page Admin > Modules > Activities > Turnitin set the following:
## Tick the box "Use Turnitin Submission"
## Enter your Turnitin Account ID
## Enter your Turnitin Secret Key as obtained from your Turnitin Account Rep
## Elect whether to send students an e-mail to allow them to login to the turnitin.com site to view their submissions (this isn't necessary, and will likely cause your students more confusion, as all the information available in the website is available from your moodle site.) - even if no e-mail is sent, students can visit turnitin.com and use the forgotten password functionality on the turnitin site to get their password sent via e-mail. Admins can disable this by adding a prefix to all email accounts created - see below for details.
## Add an e-mail prefix if you don't want students to be able to access the reports on turnitin.com - it is advised that you allow the integration in moodle to control what your students see, however, if you allow them to login to turnitin.com they can bypass the settings made regarding when a report should be available. - it's also possible that they could potentially upload a file to turnitin.com instead of moodle, which you may not notice. It's reccommended that you put something in this box to make the e-mail addresses for students stored on the turnitin.com system invalid.
## Set a Course Prefix - this is not compulsory, however if you have more than 1 Moodle site connecting to the Turnitin API - eg a testing site, and a production site, then a prefix MUST be set, because Turnitin will only allow 1 course with the same name - and only 1 assignment within that course with the same name. - you will potentially get conflicts if this is not set.
## Set the Student Disclosure statement. - this is displayed to all students on the upload screen to notify them that the Turnitin system is in use.

==Configuration of Turnitin inside Moodle Activity Modules==
===Assignment Module===
(currently only available with the advanced file upload and single upload types)
* Create a new Assignment within your course.
* Enable Turnitin Submission

==Debugging==
* when testing the turnitin integration you should make sure debugging is turned on, as it will provide information regarding the process.
* error codes recieved from the turnitin API are also logged in the mdl_tii_files table, so you can view issues with a production system.
* each file that is going to be submitted to turnitin is added to the table mdl_tii_files - the field tiicode gives the "status" of the file, - there are 3 "good" states for this field:
# "pending" - this is a new file that has been uploaded to an activity module, and needs to be submitted to Turnitin (will happen next time cron runs)
# "51" - this is the turnitin API code for Successful upload - this means the file has been uploaded to Turnitin and we are waiting on an originality score,
# "success" - this is a file that has been submitted, and a score has been provided for it.
Any other response code in this field indicates an error state, see the [[Turnitin errors]] page for a complete list of codes.