MoodleDocs - User contributions [en]

Plagiarism plugins

2024-05-28T15:07:58Z

Joeythibault: added new plugin based on the API

==Introduction==
The Plagiarism API is a core set of functions that all Moodle code can use to send user submitted content to Plagiarism Prevention systems

A typical user story:
# When Plagiarism tools are enabled (in site administration/advanced features and also check site administration/plugins/plagiarism/manage plagiarism plugins), every module that allows it will have a group of settings added to allow management of sending the user content to a plagiarism service.
# A user enters some content/submits a file inside a module that a teacher/Admin has configured the tool to be used.
# An Event is triggered which contains details about the user, module and submission they have made
# Event handlers in the Plagiarism plugin are triggered and process anything required.
# Hooks for displaying information returned from the Plagiarism tools to both the user and teacher (controlled by the plugin)
===Supported Modules ===
The following modules are the only ones who have currently implemented support for the plagiarism api
* Assignment 2.2 -
** Single Upload Assignment
** Advanced Assignment
** Online Text Assignment
* Assignment
* Forum
* Workshop

==Examples==
* Urkund https://github.com/danmarsden/moodle-plagiarism_urkund
* Turnitin https://github.com/turnitin/moodle-plagiarism_turnitin
* Originality.AI https://moodle.org/plugins/plagiarism_origai
* PlagScan https://api.plagscan.com/plagscan_2015071501.zip

==Template==
Use this git branch as a base for your new plugin: https://github.com/danmarsden/moodle-plagiarism_new
(replace all instances of "new" with the folder name of your new plugin)
==Naming conventions==
Following Naming conventions should be kept in mind while writing a plagiarism plugin:-

*Folder name should be same as pluginname
*Name of the extended class should be plagiarism_plugin_pluginname
*Each plugin must define the string "pluginname" in the language files.

== Interfacing to APIs ==

======cron======
This function was deprecated in 3.1, Moodle 2.7 added the new [[Task_API]] which should now be used instead. in versions prior to 3.1 this function must exist within your local class but can be empty if you have migrated to using the newer [[Task_API]]

======get_form_elements_module======
This function allows the addition of any Plagiarism specific settings to an mform inside a module settings page.

======save_form_elements======
This function is triggered when a teacher saves the settings on a module page to allows storing of any Plagiarism specific settings.

======get_links======
This function provides a hook to allow information to be displayed beside a users submission - for example the grading page for teachers to display an originality score/link to more information or to allow a student to see the same information.

======print_disclosure======
This function allows the plugin to display a message to users inside the submission page to let them know that the submission will be passed to a plagiarism prevention system.

======update_status======
This function is called on pages that display a full list of users eg grading pages to allow the status of any submissions to be checked. This function is called every time the report page is loaded so it should perform appropriate caching.

===Event Triggers===
Modules that support the Plagiarism API should have appropriate event triggers when a user has updated text that requires processing by the Plagiarism API

==See also==
* [[How_to_add_support_for_a_Plagiarism_Plugin_to_my_activity_module]]

[[Category:Plugins]]

GSoC with Moodle

2015-09-22T11:23:29Z

Joeythibault:

{{GSOC}}

==Overview==

Moodle has been involved in Google's [http://code.google.com/soc Summer of Code] program since 2006. This program pays students to work on open source software products for about three months (over the northern hemisphere summer), mentored by existing developers of those products. The work usually adds a new feature or a new module. The intention is that this new code improves the software, as well as helping new programmers to become familiar with developing in an open source community.

==Applying to be a GSoC student with Moodle==

Students apply for projects via the GSOC site. The project applications are then passed on to Moodle are evaluated and selected by the full group of Moodle mentors. The best proposals are often from students who take the time to interact and discuss their ideas before submitting a proposal.

If you are a student older than 18 years and wish to participate in the GSoC with Moodle as the target project:

# Check out what's involved in the [http://code.google.com/soc/ Google Summer of Code] (which can change from year to year).
# Look at the list of [[Projects_for_new_developers|projects for new developers]], or think up one of your own.
# Find out [[Applying_to_work_with_Moodle_for_GSOC|how to apply]] to complete a GSoC project with Moodle.

==Matching students and mentors==

Mentors are regular Moodle developers who volunteer to help guide and support students in the program. The final decision on who can be a mentor is made by [[:en:Martin Dougiamas|Martin Dougiamas]]. Successful mentoring is quite a commitment, so this task should not be taken on lightly.

==Development process==

Once students and mentors have been matched with projects within Moodle, our process runs something like this:

; Create a project specification page
: A page will be created in [[Main_Page|Moodle Dev Docs]] (this wiki) for each project when they are selected. On the wiki page students should start developing a detailed specification with feedback from mentors. The page should include database table designs, GUI mockups, class structures and other implementation details. The document should be clear and logically organised.

; Seek and utilise community feedback
: Students should introduce the project in the appropriate forums on [http://moodle.org/course/view.php?id=5 Using Moodle] to help draw attention to it and to stimulate some discussion around their development. The more feedback we have the better, especially if it includes a wide variety of users (developers, teachers, students, etc). Students should be responsive in those forums to build a dialogue with the community.

; Evolve the specification
: Students and mentors should use the feedback to evolve the specification into something that all users are happy with. Sometimes it's worth doing more research to find the "best" way to do something without adding Yet Another Option.

; Set up tasks in the [http://tracker.moodle.org Moodle Tracker]
: Once the specification has settled down, it's time to start work. The mentor should create a new issue in the [http://tracker.moodle.org Moodle Tracker] (in the CONTRIB project) and assign it to the student (after they added to the "contrib-developer" Tracker group). Students should add sub-tasks in roughly chronological order for different parts of the project. This helps students keep track of where they are, but also allows the community to "watch you" develop and to help you where they can.

; Develop in Git and link to tracker
: Students can develop their code in Git repository. When projects are producing an independent plugin, a single repository can be used. For more complex integrations involving changes to Moodle core, [[User:Sam_Hemelryk/My_Moodle_Git_workflow|working with a branch of the Moodle repository]] will be necessary. Git commits will be related to tracker issues and should note the issue number at the beginning of the commit message. If you are new to Git development, have a look at this [https://docs.moodle.org/dev/Git_for_developers documentation].

; Advertise milestones in the forums
: Major milestones should be posted in the forums, to maintain community interest and draw in new testers and more feedback.

; Finish off projects
: Once the time is up, finished projects need to be assessed; Google need to be given access to the result of the project, as per their instructions. Hopefully the code is also good enough to be shared in the [http://moodle.org/plugins Plugins Directory] or possibly go into the next Moodle release, although neither is guaranteed.

== 2015 ==

Overview: [[GSOC/2015]] | [https://www.google-melange.com/gsoc/homepage/google/gsoc2015 Google Summer of Code 2015 site] | [https://moodle.org/auth/mnet/jump.php?hostwwwroot=http://dev.moodle.org&wantsurl=/course/view.php?id=18 GSOC 2015 course]
# [https://docs.moodle.org/dev/GSOC/2015 Meta Enrollment Plugin with Multiple Courses Selection]
# [https://docs.moodle.org/dev/GSOC/2015 Moorsp Plagiarism API Test Plugin]
# [https://docs.moodle.org/dev/GSOC/2015 SCORM 1.2 player in the Moodle app]

== 2014 ==

Overview: [[GSOC/2014]]
# New question types
# SCORM improvements

==2013==

Overview: [[GSOC/2013]]
# [[Self-assessment activity using the question bank]]
# [[SCORM player rewrite]]
# [[Global search]]
# [[Course search]]
# [[Pronunciation evaluation question type]]
# [[A Moodle plugin for determining Quiz authorship]]
# [[Portfolio plugin for Evernote]]

==2012==

Overview: [[GSOC/2012]]
# [[Improve SCORM 2004 Support]]
# [[Plagiarism API improvements]]
# [[Email reminders for calendar events]]
# [[Audio/Video Capture repository plugin]]

* [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 Google Summer of Code 2012]

==2011==

Overview: [[GSOC/2011]]
# [[SCORM reporting improvements]]
# [[Moodle flavours]]
# [[SCORM Test Harness]]

* [http://www.google-melange.com/gsoc/program/home/google/gsoc2011 Google Summer of Code 2011]

==2009==

Overview and results: [[GSOC/2009]]

# [[Record audio repository plugin|Record audio repository plugin]]
# [[Timeline course format|Timeline course format]]
# [[Usability/Improve Moodle User Experience Consistency|Improve Moodle user experience consistency]]
# [[Paint tool|What you paint is what you get]]
# [[Google Gears integration|Google Gears integration]]

* [http://www.google-melange.com/gsoc/program/home/google/gsoc2009 Google Summer of Code 2009]

==2008==

Overview and results: [[GSOC/2008]]

#[[Student projects/Usability issues|Usability issues]]
#[[Student projects/SQLite|SQLite]]
#[[Student projects/Animated grade statistics report|Animated grade statistics report]]
#[[Student projects/Language editing interface|Language editing interface]]
#[[Student projects/Feed aggregation library|Feed aggregation library]]
#[[Student projects/Customisable theme|Customisable theme]]
#[[Student projects/Blog improvements|Blog improvements]]
#[[Student projects/Further messaging improvements|Further messaging improvements]]
#[[Student projects/Automatic accessibility checking|Automatic accessibility checking]]
#[[Progress_tracking|Progress tracking]]
#[[Student projects/Secure RSS feeds|Secure RSS feeds]]
#[[Student projects/Moodle IDE|Moodle IDE]]

* [http://code.google.com/soc/2008/ Google Summer of Code 2008]

==2007==

Overview and results: [[GSOC/2007]]

#[[Student projects/New question types|New question types]]
#[[Student projects/Enterprise-level improvements|Enterprise-level improvements]]
#[[Student projects/Chat revamp|Chat revamp]]
#[[Student projects/Messaging improvements|Messaging improvements]]
#[[Student projects/Automated grading of programs|Automated grading of programs]]
#[[Student projects/User Management Improvements|User Management Improvements]]
#[[Student projects/Email interface|Email interface]]
#[[Student projects/Social Networking features|Social Networking features]]
#[[Voice|Voice]]

* [http://code.google.com/soc/2007/ Google Summer of Code 2007]

==2006==

#[[Student projects/Presets for Database module|Presets for Database module project notes]]
#[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]
#[[Student projects/AJAX course format|AJAX course format project notes]]
#[[Student projects/Admin page cleanup|Admin page cleanup project notes]]
#[[Student projects/Global search|Global search project notes]]

* [http://code.google.com/soc/2006/ Google Summer of Code 2006]

==See also==

* [[Projects for new developers]]

Talk:Main Page

2015-03-24T13:05:15Z

Joeythibault:

Hi,
Please edit the side Nav block in Moodle 2.0 docs so that the link goes to https://docs.moodle.org/dev/Developer_documentation, not this page. Alternatively, figure out which is the main page, or put a redirect here :) Thanks --[[User:chris collman|chris collman]] 19:46, 3 October 2011 (WST)

suggest adding the development calendar as a link on this page: https://www.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com%C2%A0

== Wiki/Files ==

Good morning, on one of my works in progress with the moodle environment must know where that is in the database of Moodle saves some reference people participating in a Wiki and also viewing the files to download. Thank you.

States of a quiz attempt

2014-08-04T13:16:20Z

Joeythibault:

This page relates to the problem of the following scenario:
# Student starts an attempt at a timed quiz.
# Student logs out and goes away.
# Quiz time limit expires.
# Student (or teacher) comes back. They now cannot continue (or review, or complete) the quiz attempt. They are stuck.
::That's not what actually happens. Actually on 4 student see a button to continue his attempt. He press it and goes to the attempt, which is instantly submitted, and he get returned to quiz intro. He could then start a new attempt ... if there is no time delay between attempts. If there is he is stuck.--[[User:Oleg Sychev|Oleg Sychev]] 19:55, 24 November 2009 (UTC)

Different people have different desires for how this is handled. The aim of this page is to collect together all the things that different people might want, so we can try to design a solution that makes everyone happy.

Currently this page is just a random dump of things Tim remembered, please feel free to add to, or edit it.

==What currently happens==

===The states a quiz attempt can be in===

* {before the attempt is started}. Not sure if this really exists. Before the attempt has been started, it does not exist!
* During the quiz attempt (Quiz attempt open). This is distinguished by $attempt->timefinish being 0.
* After the attempt is finished. This is distinguished by $attempt->timefinish being non-zero.

===Behaviour===

* A user can have at most one quiz attempt open at any time.
* If the user is attempting the quiz when the time expires, and if they have JavaScript on, then the quiz is automatically submitted for them.
* If the student is not attempting the quiz when the time expires, then their attempt is not submitted, and neither the student nor the teacher can submit it.
Actually the attempt will be graded 0, but individual questions may be regraded if page was saved.
Teachers could use it to calculate attempt grade manually, but they really don't like it.--[[User:Oleg Sychev|Oleg Sychev]] 19:55, 24 November 2009 (UTC)
* Time can expire either because of $quiz->timelimit, or $quiz->timeclose.
* There is a capability mod/quiz:ingoretimelimit for accessibility reasons. This causes $quiz->timelimit, but not $quiz->timeclose, to be ignored.
* After the attempt is submitted, students may, or may not be able to review, depending on the quiz review settings and whether $quiz->timeclose has passed.
* In addition to the only one open attempt rule, there may also be a delay between the end of one quiz attempt and the start of the next ($quiz->delay1/2).

==What we would like to happen==

===The states we need to distinguish===

* {before the attempt is started}
* Quiz attempt open, time has not expired.
* Quiz attempt open, time has expired.
* Quiz attempt submitted, some questions need manual grading.
* Quiz attempt submitted, all questions graded.
Actually these states makes quiz time delay more complicated.
The question is what state it should use as an end of previous attempt?
It should be submission for quizzes without time limit.
But for quizzes with time limit it should be min(time expiration, submission) otherwise we still may get
problem with time delay mentioned above.--[[User:Oleg Sychev|Oleg Sychev]] 19:55, 24 November 2009 (UTC)

Might we also want/need to distinguish the states 'results not visible yet', and 'results released to student', for a submitted quiz. These two are orthogonal to whether any questions need manual grading, so that actually leads to four sub-states under submitted.

===Behaviour===

* Teacher should have the option to submit an attempt when the student forgot.
* Student should have the option to submit an attempt late (but not answer any more questions) when they forgot. Probably the best way to do this is that after time has expired, if the student is still allowed to Submit all and finish, they can only go to the attempt summary page (in Moodle 2.0) and click the submit button.
* Some people like the current behaviour: the student must submit on time, and if they don't they don't get a grade, and it is tough luck. Therefore, if students are allowed to submit the quiz late, there should be a time limit for how much extra time they have in which to do so (which can be anything from 0 to infinity).
* There should be an option which, at the moment when time expires on an attempt, send an email to the student reminding them that they have not submitted it, and explaining to them how to do so, and how long in which they have to do so.
* Alternatively, the quiz may have an option set to automatically submit any quiz attempt the moment time has expired.
* May want an option where, if the student is allowed to submit late, we do process any updated answers, but a penalty is applied to their score.
* May want an option for a teacher to un-submit a quiz attempt, for those situations where a student has (claims to have) clicked Submit all and Finish too early, by mistake.
* Teachers can delete any quiz attempt (open or submitted) at any time (''this has been implemented for a long time'')
* Giving teacher the ability to decide, that particular student in particular attempt could bypass time delay (without deleting previous attempt) will resolve a great deal of the problems. (''this is implemented in Moodle 2.0'')

===Other ideas===

* Some people may want to count un-submitted attempts if quiz has a limit on a number of attempts, other may want to exclude them.

'' This is not really possible, given the assumption the quiz has that there is at most one open attempt, which can either be submitted or deleted, and once it is submitted, it counts. I also don't really see the point of this. If you are being that flexible, why have a limit on the number of attempts at all? ''

* May want an option for a teacher to extend time limit for particular attempt (if, for example, computer hangs during the attempt, or the student press submit near the finish and wait more than 60 seconds)

'' This is, as opposed to extending it for all attempts for a particular student. This would be a lot of work to implement, and only occasionally useful. For now, I think it is sufficient to have the option to change the time limit for one student. You can always extend it until they have submitted that one attempt, and then change it back. ''

* (I don't know whether it really possible, but it's a very good option to have) Save current attempt state with responses in a browser window if submitting request on server failed. Sometimes server go down during important attempts (exams and so no), that's quite bad for timed quizzes. At least we could send AJAX request to the server before submitting to verify it still working (should work in couple with teacher-defined time limit extension mentioned above to prevent abuse).

'' This is not possible. ''

* ... please add more ideas here ...

===Changes to the code===

''Note that this builds on top of Moodle 2.0. If you don't know what things like the summary page are, or how the quiz reports work in the latest version, this may not make any sense.''

* New capability mod/quiz:submitlateattempt - can apply to students, and/or teachers, but with slightly different meaning. (Teacher here is probably defined by mod/quiz:grade, or mod/quiz:viewreports. Or perhaps it is clearly to have separate capabilities mod/quiz:submitmylateattempt and mod/quiz:submitanylateattempt.) Or perhaps rather than a capability, a quiz setting saying how much extra time students have after their attempt becomes overdue, to go in and submit it.

* If a student has mod/quiz:submitlateattempt, and/or if they are still within the extra time allowed, then they can get at overdue quiz attempts, but they can only go to the summary page in order to click the Submit all and finish button.

* For teachers with mod/quiz:submitlateattempt, there will be a new button in the quiz reports (next to delete attempts and regrade attempts) to submit any overdue quiz attempts that have been selected using the check-boxes.

* New database column quiz_attempt.state, to make the current state of each attempt clear. (Not sure if this is really necessary.)

* Code on cron, or when the attempt is accessed, to update the attempt state if, for example, time has expired since it was last changed.

* A quiz option, and code on cron, to automatically submit overdue quiz attempts if that is what the teacher wants.

* A quiz option, and code on cron, to email a student when an attempt becomes overdue, telling them how long the still have to submit it, and how to do so.

* Possibly new column quiz_attempt.finishedby, to record the userid of the user who submitted the attempt, so we know if the teacher has submitted a later attempt for the student. Could be NULL, if late attempts are submitted automatically.

* Code in the question engine to correctly process incomplete attempts when an overdue attempt is submitted.

==See also==

===Discussion===

* Please discuss this in [http://moodle.org/mod/forum/discuss.php?d=138660 this Quiz forum thread].

===Relevant tracker issues===

* MDL-3030 Late quiz attempts should be closed automatically
* MDL-3452 Use saved answers when marking late submissions
* MDL-4309 Ability for late quizzes (with penalty)
* MDL-20956 Student can't start new attempt if a quiz has timle limit between attempts and time limit for a quiz, and he doesn't submit previous attempt closing browser window instead
* ... please add other relevant tracker issues here.

===See also===

* [[Goals_of_an_online_assessment_system|Goals of an online assessment system]]
* [http://moodle.org/mod/forum/discuss.php?d=118343 Closing unfinished attempts - possible solution for 1.9]
* [https://docs.moodle.org/23/en/User_talk:John_Rich Moodle Documents]

[[Category:Quiz]]

Talk:Mobile app

2010-07-13T13:58:56Z

Joeythibault: New page: I'd love to see the ability for students to take quizzes be included in a 1.0 mobile app. Comparative LMS (BB) have not yet achieved this with their own Mobile apps and it would be a boon...

I'd love to see the ability for students to take quizzes be included in a 1.0 mobile app. Comparative LMS (BB) have not yet achieved this with their own Mobile apps and it would be a boon for mobile learning (or learning utilizing tablet devices).