https://docs.moodle.org/2x/ca/api.php?action=feedcontributions&feedformat=atom&user=Hatshepsut 2026-04-15T12:14:57Z Contribucions de l'usuari MediaWiki 1.43.5 https://docs.moodle.org/2x/ca/index.php?title=Side_bar_block&diff=67708 2010-01-26T13:19:26Z

<p>Hatshepsut: /* See also */ corrected link</p> <hr /> <div>This contributed code module allows you to create separate activities and resources in a block. In the standard Moodle, these only appear in the center column. You can have multiple copies of this block in a course, each one unique.<br /> <br /> ==Features==<br /> It functions by creating course sections for each instance, starting at a number<br /> beyond what would normally be used by a course. This defaults to section 1000,<br /> but is configurable at the global level.<br /> <br /> All resources and activities within a block can be edited and moved around just<br /> like normal activities when editing is turned on. Adding label resources allows<br /> you to add text to the blocks as well.<br /> <br /> In a sense, this block combined the main menu block functions and HTML block<br /> functions into one block that can be used in a course.<br /> <br /> <br /> ==Tips and tricks==<br /> *Use with a Lesson dependency feature. When you create an activity a Side bar block (like a Quiz), you can then hide the block and the quiz is still accessible via an internal link. Thus you can force a student to go through a series of Lessons before taking the quiz. In the last lesson of the series, put the internal link to the quiz which is hidden from view but is technically open to students. This is not 100% foolproof, but will keep most of the students on the path you want. <br /> <br /> ==See also==<br /> *[http://moodle.org/mod/data/view.php?d=13&amp;rid=270&amp;filter=1 Side Bar Block] is a Modules and plugins database page for downloads and more information.<br /> *Discussions: please create or find a discussion topic in the [http://moodle.org/mod/forum/view.php?id=44 Contributed Code forum]<br /> <br /> [[Category:Contributed code]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Book_settings&diff=67658 2010-01-25T15:31:16Z

<p>Hatshepsut: clarified custom titles</p> <hr /> <div>{{Book}}<br /> __TOC__<br /> Turn on editing in your course and choose the book resource from the drop down resources menu:<br /> [[Image:moodlebook.png|frame|left|getting started]] &lt;br style=&quot;clear:both;&quot;&gt;<br /> <br /> <br /> <br /> == Give your book a name and a summary ==<br /> <br /> Tell your students what your book is called and provide a brief description of its content. Keep in mind that ''the name you give your book will become the text for the link to it'' on your main course page. This is true of all the activities you create in Moodle.<br /> <br /> [[Image:Book2.png|frame|none|add name and summary]]<br /> <br /> == Indicate how you want chapters numbered ==<br /> <br /> There are several predefined numbering types: <br /> <br /> * None - chapter and subchapter titles are not formatted at all, use if you want to define special numbering styles. For example letters: in chapter title type &quot;A First Chapter&quot;, &quot;A.1 Some Subchapter&quot;,...<br /> <br /> * Numbers - chapters and subchapters are numbered (1, 1.1, 1.2, 2, ...)<br /> <br /> * Bullets - subchapters are indented and displayed with bullets.<br /> <br /> * Indented - subchapters are indented.<br /> <br /> [[Image:Book3.png|frame|none|define numbering]]<br /> <br /> Note that the width of the table of contents is set by the administrator of your site.<br /> <br /> == Enable or disable printing ==<br /> <br /> ''Disabling printing'' means hiding the print icons. (The print option is one of this resource's most popular features, so you might not want to disable it.)<br /> <br /> [[Image:Book4.png|frame|none|allow printing?]]<br /> <br /> == Allow or disallow custom titles ==<br /> <br /> If you disallow custom titles, the chapter title (the one that appears on the table of contents) will appear as a header at the top of your content. If you enable custom titles, you will be able to create a title different from the one that appears in the ToC or display no title at all. If you enable custom titles, you will need to enter the chapter title as part of the page content.<br /> <br /> [[Image:Book5.png|frame|none|permit custom titles?]] <br /> <br /> [[Image:Custom_title.jpg|frame|none|Custom Titles Enabled: The custom title (red arrow) is different than the title in the table of contents (green arrow).]]<br /> <br /> [[Image:Custom_title2.jpg|frame|none|Custom Titles Disabled: The titles in the table of contents and in the chapter are the same.]]<br /> <br /> == Add a chapter ==<br /> <br /> Titles of chapters appear as links in the table of contents to the left of your content. Keep your titles short.<br /> <br /> [[Image:Book6.png|frame|none|add a chapter]]<br /> <br /> == View work to date ==<br /> <br /> So far, you see the table of contents on the left and the content on the right. Note the print icons near the top.<br /> <br /> To add another chapter, click on the red cross in the Table of Contents. The new chapter will be inserted directly after the chapter whose title is on the same line as the red cross you click.<br /> <br /> [[Image:Book7.png|frame|none|so far, so good]]<br /> <br /> == Add a sub chapter ==<br /> <br /> Note that the sub chapter box is checked. A chapter may have many sub chapters, but sub chapters cannot have subchapters. In order to keep this resource simple, you are limted to two levels.<br /> <br /> [[Image:Book8.png|frame|none|add a sub chapter]]<br /> <br /> == Using Book ==<br /> <br /> One may, of course, use book to present information in a well-structured, user-friendly format. But there are other possibilities. Because this module allows one to import individual web pages or folders of web pages, it is useful for group work. Example: Each student creates a simple web page about your school and the teacher, (that's you!) uploads the pages to the book. ''Viola!'' You and your students have created a useful, interesting resource for new students and their parents. You could do this to create a class cook book and nutrition guide, a resource about local civic organizations, ''triangles in our daily lives'', world leaders, you name it.<br /> <br /> [[Image:Book-import1.png|frame|none|click on the import link]]<br /> <br /> [[Image:Book-import2.png|frame|none|browse to the desired web page or folder of web pages and import them into your book]]<br /> <br /> Note: Relative file links are converted to absolute chapter links. Images, Flash and Java are relinked too. Remember to upload images and multimedia files as well as html files to your server, of course. Javascripts, SSI page includes, etc., will probably be lost, however, so keep your pages simple and static.<br /> <br /> [[Category:Teacher]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Attendance_module_requests&diff=67131 2010-01-11T06:47:25Z

<p>Hatshepsut: /* Description field */</p> <hr /> <div>Please remember, your developer speak english not good. Write more simply! :o)<br /> <br /> = Use wonderful voting tool! =<br /> <br /> '''Instead this page''', you can add your own ideas and vote for existing suggestions using wonderful tool '''UserVoice'''.<br /> <br /> Go and vote! [http://attendance.uservoice.com Attendance Module on UserVoice]<br /> <br /> = Suggestions =<br /> <br /> == Export photos in Excel or Open Office ==<br /> At present in version 1.9.1 at least, the images are not being sent along with the rest of the data.<br /> <br /> == Separate sessions for Group/Grouping == <br /> Need detailed description.<br /> <br /> == Extra Meta Data ==<br /> In addition to date, time, duration and description maybe have fields for:<br /> #Venue<br /> #Room<br /> #Teacher<br /> #End Time<br /> <br /> == Filter for 'Sessions' page ==<br /> The ability to find/filter sessions by description, date, time, duration (or other Meta Data as above if/when available) etc. A filtered list could then easily be selected with 'Select All'. The 'With Selected' feature can then be used on the filtered list.<br /> #Filter on field<br /> ##Description<br /> ##Date<br /> ##Time<br /> ##Duration<br /> ##Other Meta Data<br /> #With Selected<br /> ##Delete<br /> ##Change Duration<br /> <br /> == Extra Actions on 'With Selected' feature ==<br /> #Modify Description<br /> #Modify Start Time<br /> #Modify other Meta Data<br /> <br /> == Punch in and punch out ==<br /> Since we now have the start time of a session (and maybe duration) couldn't we use this to calculate whether a student is present, late, left early etc? Then we could just click &quot;In&quot; or &quot;Out&quot; and the status is calculated automatically. I would prefer that the students have to sign in/out themselves maybe with a password/barcode.<br /> <br /> ''I think it will be nice in teacher view of block (Dmitry)''<br /> <br /> I think there should be two options: <br /> # Teachers punch students in and out (using the start time and duration to calculate present, absent, late, left early etc). Some javascript to do the calculations without page refreshes would be nice if possible.<br /> # Students sign themselves in and out by either:<br /> ## Scanning a barcode card<br /> ## Scanning their fingerprints (so they can't sign in/out for their friends)<br /> ## Typing in a username and password<br /> <br /> I'm not sure how a Student Sign in/out view area would work. It should only be activated by a teacher in class - shouldn't be possible for students to login while they're at home for instance.<br /> [[User:Barry Oosthuizen|Barry Oosthuizen]] 12:29, 8 February 2009 (CST)<br /> <br /> == Increase the number of fields ==<br /> 'How about if we add more fields to the attendance_log table of the database as well? These extra fields could then be used to track other things such as a doctor's letter handed in. We would use it to track the status of &quot;make up notes&quot; we require for students who miss class.'<br /> <br /> == Integrate with ILP Module's Targets and Concerns ==<br /> <br /> The ILP module allows you to set individual targets for students with due dates. A target can have 3 statuses: 1. To be achieved, 2. Achieved or 3. Withdrawn and a due date can be entered against a target. It would be quite handy to use this system for attendance e.g. if a student is marked Absent an ILP Target entry is automatically created telling the student to hand in a doctor's letter within 1 week, come and see the teacher, write up the notes for the class from an audio recording (like we do) or something like that.<br /> <br /> '''Another idea for integrating with ILP module''':<br /> When a student has not achieved their target (i.e. failed to hand in a doctor's letter etc) by the due date the unachieved target entry becomes a 'Concern' in the ILP module.<br /> <br /> Students and teachers will then be able to see at a glance in the ILP module what is outstanding etc.<br /> <br /> Adding this kind of feature to the Attendance module without integrating with the ILP is another option I guess.<br /> <br /> More info about ILP here: [http://moodle.ulcc.ac.uk/course/view.php?id=107]<br /> <br /> ==Integrate with MRBS module==<br /> The Meeting Room Booking System module (https://docs.moodle.org/en/MRBS_block) has a database of place (room), time (session, slot), and possibly 2 other info like: course id, teacher (in name and description field of the booking) if desired so. <br /> <br /> I wonder if attendance module could have an option of pulling out the data in MRBS and automatically setup the sessions, so that we can avoid setting session manually (and eliminate risk of inconsistency between attendance data and room booking/timetable data).<br /> <br /> In a more general term, could the module automatically pull out data from general database that store timetable info?<br /> <br /> == Import and Export Sessions ==<br /> === Import ===<br /> It would be very useful to be able to import scheduled events from the Moodle Calendar, Google Calendar, Outlook, MRBS etc straight into the attendance_sessions table and not have to manually recreate them.<br /> <br /> === Export ===<br /> For those using the attendance module as the primary place of scheduling events/sessions the ability to export that into Outlook, Google Calendar etc would be great. --[[User:Barry Oosthuizen|Barry Oosthuizen]] 06:15, 10 February 2009 (CST)<br /> <br /> ==Email Absentees==<br /> It would be useful for an instructor to be able to set a threshold (70% attendance or 50% attendance, etc), click on &quot;send email&quot; and send an email (via quickmail perhaps) to all students whose attendance is below the threshold. [[User:Dennis Williams 3|Dennis Williams 3]]<br /> <br /> ==Negative Impact on Grade==<br /> Our program lowers the grades of students if they pass a preset threshold of unexcused absences. If a student would have received a B in the course, if they miss 3 classes their grade is lowered to a B-. If they miss 4 classes, it is lowered to a C+, etc. Being able to lower the grade based on these criteria automatically would be desirable. --[[User:N Hansen|N Hansen]] 06:46, 11 January 2010 (UTC)<br /> <br /> ==Description field==<br /> <br /> The module as a whole should have a description field as is normal with other modules. This would allow the teacher to enter an attendance policy that students could view. --[[User:N Hansen|N Hansen]] 06:47, 11 January 2010 (UTC)<br /> <br /> = Now in development =<br /> <br /> = Released =<br /> <br /> == Multiply sessions in day ==<br /> ''Are we need a duration for sessions? (Dmitry)''<br /> <br /> 'We can do with sessions having a duration. We need to calculate the number of hours a student was in class per week as International Students have to fulfill the minimum requirement of 15 hours per week.'<br /> <br /> == Increase the number of categories ==<br /> It would make Attendance more flexible if you could increase the number of categories from the default of 4 to a maximum of 9. This would allow Attendance to be used for daily points, for example. The categories could be set up once under &quot;Settings&quot; as a drop-down menu &quot;Number of categories 4-9&quot; when you are also setting up letters and descriptions, but before sessions. You could leave the default at 4 to keep Attendance easy to use.<br /> <br /> ''This feature will be in near future. You be able to use unlimited number of statuses (categories). (Dmitry)''<br /> <br /> ==Export days not yet used in Excel or Open Office ==<br /> It would be good if you were able to export the days for the future that had not yet been filled in.<br /> <br /> I am thinking of a situation where someone might be having a problem with Moodle and has to go back to taking the details manually.<br /> In this case, the extra days would be handy. A copy of this could be kept aside for the staff member should the need ever arise.<br /> <br /> == Reset the module/Multiple module instances ==<br /> If I remove the module and then add it again, old attendance data remains. It would be great to be able to reset the module so that we can start attendance fresh for a new unit of a course.<br /> Even better would be the option of multiple attendance instances, so that we could have one module for each unit in a course!<br /> <br /> ''Possibility of reset already implemented in developer's version. Deleting data not always good, so we have simple way for hide unused data - just change course's start date to actual for current course.''<br /> <br /> Actually this does not work for '''units''' within a course.<br /> We need to have a course of for example three units, and to reset the attendance data for each unit. <br /> We can't change the start date for the entire course after only the first unit is over.<br /> <br /> ''Reset feature implemented''<br /> <br /> = See also =<br /> * [[Attendance module]] official page<br /> <br /> [[Category:Contributed code]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Attendance_module_requests&diff=67130 2010-01-11T06:46:47Z

<p>Hatshepsut: /* Negative Impact on Grade */</p> <hr /> <div>Please remember, your developer speak english not good. Write more simply! :o)<br /> <br /> = Use wonderful voting tool! =<br /> <br /> '''Instead this page''', you can add your own ideas and vote for existing suggestions using wonderful tool '''UserVoice'''.<br /> <br /> Go and vote! [http://attendance.uservoice.com Attendance Module on UserVoice]<br /> <br /> = Suggestions =<br /> <br /> == Export photos in Excel or Open Office ==<br /> At present in version 1.9.1 at least, the images are not being sent along with the rest of the data.<br /> <br /> == Separate sessions for Group/Grouping == <br /> Need detailed description.<br /> <br /> == Extra Meta Data ==<br /> In addition to date, time, duration and description maybe have fields for:<br /> #Venue<br /> #Room<br /> #Teacher<br /> #End Time<br /> <br /> == Filter for 'Sessions' page ==<br /> The ability to find/filter sessions by description, date, time, duration (or other Meta Data as above if/when available) etc. A filtered list could then easily be selected with 'Select All'. The 'With Selected' feature can then be used on the filtered list.<br /> #Filter on field<br /> ##Description<br /> ##Date<br /> ##Time<br /> ##Duration<br /> ##Other Meta Data<br /> #With Selected<br /> ##Delete<br /> ##Change Duration<br /> <br /> == Extra Actions on 'With Selected' feature ==<br /> #Modify Description<br /> #Modify Start Time<br /> #Modify other Meta Data<br /> <br /> == Punch in and punch out ==<br /> Since we now have the start time of a session (and maybe duration) couldn't we use this to calculate whether a student is present, late, left early etc? Then we could just click &quot;In&quot; or &quot;Out&quot; and the status is calculated automatically. I would prefer that the students have to sign in/out themselves maybe with a password/barcode.<br /> <br /> ''I think it will be nice in teacher view of block (Dmitry)''<br /> <br /> I think there should be two options: <br /> # Teachers punch students in and out (using the start time and duration to calculate present, absent, late, left early etc). Some javascript to do the calculations without page refreshes would be nice if possible.<br /> # Students sign themselves in and out by either:<br /> ## Scanning a barcode card<br /> ## Scanning their fingerprints (so they can't sign in/out for their friends)<br /> ## Typing in a username and password<br /> <br /> I'm not sure how a Student Sign in/out view area would work. It should only be activated by a teacher in class - shouldn't be possible for students to login while they're at home for instance.<br /> [[User:Barry Oosthuizen|Barry Oosthuizen]] 12:29, 8 February 2009 (CST)<br /> <br /> == Increase the number of fields ==<br /> 'How about if we add more fields to the attendance_log table of the database as well? These extra fields could then be used to track other things such as a doctor's letter handed in. We would use it to track the status of &quot;make up notes&quot; we require for students who miss class.'<br /> <br /> == Integrate with ILP Module's Targets and Concerns ==<br /> <br /> The ILP module allows you to set individual targets for students with due dates. A target can have 3 statuses: 1. To be achieved, 2. Achieved or 3. Withdrawn and a due date can be entered against a target. It would be quite handy to use this system for attendance e.g. if a student is marked Absent an ILP Target entry is automatically created telling the student to hand in a doctor's letter within 1 week, come and see the teacher, write up the notes for the class from an audio recording (like we do) or something like that.<br /> <br /> '''Another idea for integrating with ILP module''':<br /> When a student has not achieved their target (i.e. failed to hand in a doctor's letter etc) by the due date the unachieved target entry becomes a 'Concern' in the ILP module.<br /> <br /> Students and teachers will then be able to see at a glance in the ILP module what is outstanding etc.<br /> <br /> Adding this kind of feature to the Attendance module without integrating with the ILP is another option I guess.<br /> <br /> More info about ILP here: [http://moodle.ulcc.ac.uk/course/view.php?id=107]<br /> <br /> ==Integrate with MRBS module==<br /> The Meeting Room Booking System module (https://docs.moodle.org/en/MRBS_block) has a database of place (room), time (session, slot), and possibly 2 other info like: course id, teacher (in name and description field of the booking) if desired so. <br /> <br /> I wonder if attendance module could have an option of pulling out the data in MRBS and automatically setup the sessions, so that we can avoid setting session manually (and eliminate risk of inconsistency between attendance data and room booking/timetable data).<br /> <br /> In a more general term, could the module automatically pull out data from general database that store timetable info?<br /> <br /> == Import and Export Sessions ==<br /> === Import ===<br /> It would be very useful to be able to import scheduled events from the Moodle Calendar, Google Calendar, Outlook, MRBS etc straight into the attendance_sessions table and not have to manually recreate them.<br /> <br /> === Export ===<br /> For those using the attendance module as the primary place of scheduling events/sessions the ability to export that into Outlook, Google Calendar etc would be great. --[[User:Barry Oosthuizen|Barry Oosthuizen]] 06:15, 10 February 2009 (CST)<br /> <br /> ==Email Absentees==<br /> It would be useful for an instructor to be able to set a threshold (70% attendance or 50% attendance, etc), click on &quot;send email&quot; and send an email (via quickmail perhaps) to all students whose attendance is below the threshold. [[User:Dennis Williams 3|Dennis Williams 3]]<br /> <br /> ==Negative Impact on Grade==<br /> Our program lowers the grades of students if they pass a preset threshold of unexcused absences. If a student would have received a B in the course, if they miss 3 classes their grade is lowered to a B-. If they miss 4 classes, it is lowered to a C+, etc. Being able to lower the grade based on these criteria automatically would be desirable. --[[User:N Hansen|N Hansen]] 06:46, 11 January 2010 (UTC)<br /> <br /> ==Description field==<br /> <br /> The module as a whole should have a description field as is normal with other modules. This would allow the teacher to enter an attendance policy that students could view.<br /> <br /> = Now in development =<br /> <br /> = Released =<br /> <br /> == Multiply sessions in day ==<br /> ''Are we need a duration for sessions? (Dmitry)''<br /> <br /> 'We can do with sessions having a duration. We need to calculate the number of hours a student was in class per week as International Students have to fulfill the minimum requirement of 15 hours per week.'<br /> <br /> == Increase the number of categories ==<br /> It would make Attendance more flexible if you could increase the number of categories from the default of 4 to a maximum of 9. This would allow Attendance to be used for daily points, for example. The categories could be set up once under &quot;Settings&quot; as a drop-down menu &quot;Number of categories 4-9&quot; when you are also setting up letters and descriptions, but before sessions. You could leave the default at 4 to keep Attendance easy to use.<br /> <br /> ''This feature will be in near future. You be able to use unlimited number of statuses (categories). (Dmitry)''<br /> <br /> ==Export days not yet used in Excel or Open Office ==<br /> It would be good if you were able to export the days for the future that had not yet been filled in.<br /> <br /> I am thinking of a situation where someone might be having a problem with Moodle and has to go back to taking the details manually.<br /> In this case, the extra days would be handy. A copy of this could be kept aside for the staff member should the need ever arise.<br /> <br /> == Reset the module/Multiple module instances ==<br /> If I remove the module and then add it again, old attendance data remains. It would be great to be able to reset the module so that we can start attendance fresh for a new unit of a course.<br /> Even better would be the option of multiple attendance instances, so that we could have one module for each unit in a course!<br /> <br /> ''Possibility of reset already implemented in developer's version. Deleting data not always good, so we have simple way for hide unused data - just change course's start date to actual for current course.''<br /> <br /> Actually this does not work for '''units''' within a course.<br /> We need to have a course of for example three units, and to reset the attendance data for each unit. <br /> We can't change the start date for the entire course after only the first unit is over.<br /> <br /> ''Reset feature implemented''<br /> <br /> = See also =<br /> * [[Attendance module]] official page<br /> <br /> [[Category:Contributed code]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Attendance_module_requests&diff=67129 2010-01-11T06:45:54Z

<p>Hatshepsut: </p> <hr /> <div>Please remember, your developer speak english not good. Write more simply! :o)<br /> <br /> = Use wonderful voting tool! =<br /> <br /> '''Instead this page''', you can add your own ideas and vote for existing suggestions using wonderful tool '''UserVoice'''.<br /> <br /> Go and vote! [http://attendance.uservoice.com Attendance Module on UserVoice]<br /> <br /> = Suggestions =<br /> <br /> == Export photos in Excel or Open Office ==<br /> At present in version 1.9.1 at least, the images are not being sent along with the rest of the data.<br /> <br /> == Separate sessions for Group/Grouping == <br /> Need detailed description.<br /> <br /> == Extra Meta Data ==<br /> In addition to date, time, duration and description maybe have fields for:<br /> #Venue<br /> #Room<br /> #Teacher<br /> #End Time<br /> <br /> == Filter for 'Sessions' page ==<br /> The ability to find/filter sessions by description, date, time, duration (or other Meta Data as above if/when available) etc. A filtered list could then easily be selected with 'Select All'. The 'With Selected' feature can then be used on the filtered list.<br /> #Filter on field<br /> ##Description<br /> ##Date<br /> ##Time<br /> ##Duration<br /> ##Other Meta Data<br /> #With Selected<br /> ##Delete<br /> ##Change Duration<br /> <br /> == Extra Actions on 'With Selected' feature ==<br /> #Modify Description<br /> #Modify Start Time<br /> #Modify other Meta Data<br /> <br /> == Punch in and punch out ==<br /> Since we now have the start time of a session (and maybe duration) couldn't we use this to calculate whether a student is present, late, left early etc? Then we could just click &quot;In&quot; or &quot;Out&quot; and the status is calculated automatically. I would prefer that the students have to sign in/out themselves maybe with a password/barcode.<br /> <br /> ''I think it will be nice in teacher view of block (Dmitry)''<br /> <br /> I think there should be two options: <br /> # Teachers punch students in and out (using the start time and duration to calculate present, absent, late, left early etc). Some javascript to do the calculations without page refreshes would be nice if possible.<br /> # Students sign themselves in and out by either:<br /> ## Scanning a barcode card<br /> ## Scanning their fingerprints (so they can't sign in/out for their friends)<br /> ## Typing in a username and password<br /> <br /> I'm not sure how a Student Sign in/out view area would work. It should only be activated by a teacher in class - shouldn't be possible for students to login while they're at home for instance.<br /> [[User:Barry Oosthuizen|Barry Oosthuizen]] 12:29, 8 February 2009 (CST)<br /> <br /> == Increase the number of fields ==<br /> 'How about if we add more fields to the attendance_log table of the database as well? These extra fields could then be used to track other things such as a doctor's letter handed in. We would use it to track the status of &quot;make up notes&quot; we require for students who miss class.'<br /> <br /> == Integrate with ILP Module's Targets and Concerns ==<br /> <br /> The ILP module allows you to set individual targets for students with due dates. A target can have 3 statuses: 1. To be achieved, 2. Achieved or 3. Withdrawn and a due date can be entered against a target. It would be quite handy to use this system for attendance e.g. if a student is marked Absent an ILP Target entry is automatically created telling the student to hand in a doctor's letter within 1 week, come and see the teacher, write up the notes for the class from an audio recording (like we do) or something like that.<br /> <br /> '''Another idea for integrating with ILP module''':<br /> When a student has not achieved their target (i.e. failed to hand in a doctor's letter etc) by the due date the unachieved target entry becomes a 'Concern' in the ILP module.<br /> <br /> Students and teachers will then be able to see at a glance in the ILP module what is outstanding etc.<br /> <br /> Adding this kind of feature to the Attendance module without integrating with the ILP is another option I guess.<br /> <br /> More info about ILP here: [http://moodle.ulcc.ac.uk/course/view.php?id=107]<br /> <br /> ==Integrate with MRBS module==<br /> The Meeting Room Booking System module (https://docs.moodle.org/en/MRBS_block) has a database of place (room), time (session, slot), and possibly 2 other info like: course id, teacher (in name and description field of the booking) if desired so. <br /> <br /> I wonder if attendance module could have an option of pulling out the data in MRBS and automatically setup the sessions, so that we can avoid setting session manually (and eliminate risk of inconsistency between attendance data and room booking/timetable data).<br /> <br /> In a more general term, could the module automatically pull out data from general database that store timetable info?<br /> <br /> == Import and Export Sessions ==<br /> === Import ===<br /> It would be very useful to be able to import scheduled events from the Moodle Calendar, Google Calendar, Outlook, MRBS etc straight into the attendance_sessions table and not have to manually recreate them.<br /> <br /> === Export ===<br /> For those using the attendance module as the primary place of scheduling events/sessions the ability to export that into Outlook, Google Calendar etc would be great. --[[User:Barry Oosthuizen|Barry Oosthuizen]] 06:15, 10 February 2009 (CST)<br /> <br /> ==Email Absentees==<br /> It would be useful for an instructor to be able to set a threshold (70% attendance or 50% attendance, etc), click on &quot;send email&quot; and send an email (via quickmail perhaps) to all students whose attendance is below the threshold. [[User:Dennis Williams 3|Dennis Williams 3]]<br /> <br /> ==Negative Impact on Grade==<br /> Our program lowers the grades of students if they pass a preset threshold of unexcused absences. If a student would have received a B in the course, if they miss 3 classes their grade is lowered to a B-. If they miss 4 classes, it is lowered to a C+, etc. Being able to lower the grade based on these criteria automatically would be desirable.<br /> <br /> ==Description field==<br /> <br /> The module as a whole should have a description field as is normal with other modules. This would allow the teacher to enter an attendance policy that students could view.<br /> <br /> = Now in development =<br /> <br /> = Released =<br /> <br /> == Multiply sessions in day ==<br /> ''Are we need a duration for sessions? (Dmitry)''<br /> <br /> 'We can do with sessions having a duration. We need to calculate the number of hours a student was in class per week as International Students have to fulfill the minimum requirement of 15 hours per week.'<br /> <br /> == Increase the number of categories ==<br /> It would make Attendance more flexible if you could increase the number of categories from the default of 4 to a maximum of 9. This would allow Attendance to be used for daily points, for example. The categories could be set up once under &quot;Settings&quot; as a drop-down menu &quot;Number of categories 4-9&quot; when you are also setting up letters and descriptions, but before sessions. You could leave the default at 4 to keep Attendance easy to use.<br /> <br /> ''This feature will be in near future. You be able to use unlimited number of statuses (categories). (Dmitry)''<br /> <br /> ==Export days not yet used in Excel or Open Office ==<br /> It would be good if you were able to export the days for the future that had not yet been filled in.<br /> <br /> I am thinking of a situation where someone might be having a problem with Moodle and has to go back to taking the details manually.<br /> In this case, the extra days would be handy. A copy of this could be kept aside for the staff member should the need ever arise.<br /> <br /> == Reset the module/Multiple module instances ==<br /> If I remove the module and then add it again, old attendance data remains. It would be great to be able to reset the module so that we can start attendance fresh for a new unit of a course.<br /> Even better would be the option of multiple attendance instances, so that we could have one module for each unit in a course!<br /> <br /> ''Possibility of reset already implemented in developer's version. Deleting data not always good, so we have simple way for hide unused data - just change course's start date to actual for current course.''<br /> <br /> Actually this does not work for '''units''' within a course.<br /> We need to have a course of for example three units, and to reset the attendance data for each unit. <br /> We can't change the start date for the entire course after only the first unit is over.<br /> <br /> ''Reset feature implemented''<br /> <br /> = See also =<br /> * [[Attendance module]] official page<br /> <br /> [[Category:Contributed code]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Attendance_module_requests&diff=67098 2010-01-10T17:28:28Z

<p>Hatshepsut: negative impact on grade added</p> <hr /> <div>Please remember, your developer speak english not good. Write more simply! :o)<br /> <br /> = Use wonderful voting tool! =<br /> <br /> '''Instead this page''', you can add your own ideas and vote for existing suggestions using wonderful tool '''UserVoice'''.<br /> <br /> Go and vote! [http://attendance.uservoice.com Attendance Module on UserVoice]<br /> <br /> = Suggestions =<br /> <br /> == Export photos in Excel or Open Office ==<br /> At present in version 1.9.1 at least, the images are not being sent along with the rest of the data.<br /> <br /> == Separate sessions for Group/Grouping == <br /> Need detailed description.<br /> <br /> == Extra Meta Data ==<br /> In addition to date, time, duration and description maybe have fields for:<br /> #Venue<br /> #Room<br /> #Teacher<br /> #End Time<br /> <br /> == Filter for 'Sessions' page ==<br /> The ability to find/filter sessions by description, date, time, duration (or other Meta Data as above if/when available) etc. A filtered list could then easily be selected with 'Select All'. The 'With Selected' feature can then be used on the filtered list.<br /> #Filter on field<br /> ##Description<br /> ##Date<br /> ##Time<br /> ##Duration<br /> ##Other Meta Data<br /> #With Selected<br /> ##Delete<br /> ##Change Duration<br /> <br /> == Extra Actions on 'With Selected' feature ==<br /> #Modify Description<br /> #Modify Start Time<br /> #Modify other Meta Data<br /> <br /> == Punch in and punch out ==<br /> Since we now have the start time of a session (and maybe duration) couldn't we use this to calculate whether a student is present, late, left early etc? Then we could just click &quot;In&quot; or &quot;Out&quot; and the status is calculated automatically. I would prefer that the students have to sign in/out themselves maybe with a password/barcode.<br /> <br /> ''I think it will be nice in teacher view of block (Dmitry)''<br /> <br /> I think there should be two options: <br /> # Teachers punch students in and out (using the start time and duration to calculate present, absent, late, left early etc). Some javascript to do the calculations without page refreshes would be nice if possible.<br /> # Students sign themselves in and out by either:<br /> ## Scanning a barcode card<br /> ## Scanning their fingerprints (so they can't sign in/out for their friends)<br /> ## Typing in a username and password<br /> <br /> I'm not sure how a Student Sign in/out view area would work. It should only be activated by a teacher in class - shouldn't be possible for students to login while they're at home for instance.<br /> [[User:Barry Oosthuizen|Barry Oosthuizen]] 12:29, 8 February 2009 (CST)<br /> <br /> == Increase the number of fields ==<br /> 'How about if we add more fields to the attendance_log table of the database as well? These extra fields could then be used to track other things such as a doctor's letter handed in. We would use it to track the status of &quot;make up notes&quot; we require for students who miss class.'<br /> <br /> == Integrate with ILP Module's Targets and Concerns ==<br /> <br /> The ILP module allows you to set individual targets for students with due dates. A target can have 3 statuses: 1. To be achieved, 2. Achieved or 3. Withdrawn and a due date can be entered against a target. It would be quite handy to use this system for attendance e.g. if a student is marked Absent an ILP Target entry is automatically created telling the student to hand in a doctor's letter within 1 week, come and see the teacher, write up the notes for the class from an audio recording (like we do) or something like that.<br /> <br /> '''Another idea for integrating with ILP module''':<br /> When a student has not achieved their target (i.e. failed to hand in a doctor's letter etc) by the due date the unachieved target entry becomes a 'Concern' in the ILP module.<br /> <br /> Students and teachers will then be able to see at a glance in the ILP module what is outstanding etc.<br /> <br /> Adding this kind of feature to the Attendance module without integrating with the ILP is another option I guess.<br /> <br /> More info about ILP here: [http://moodle.ulcc.ac.uk/course/view.php?id=107]<br /> <br /> ==Integrate with MRBS module==<br /> The Meeting Room Booking System module (https://docs.moodle.org/en/MRBS_block) has a database of place (room), time (session, slot), and possibly 2 other info like: course id, teacher (in name and description field of the booking) if desired so. <br /> <br /> I wonder if attendance module could have an option of pulling out the data in MRBS and automatically setup the sessions, so that we can avoid setting session manually (and eliminate risk of inconsistency between attendance data and room booking/timetable data).<br /> <br /> In a more general term, could the module automatically pull out data from general database that store timetable info?<br /> <br /> == Import and Export Sessions ==<br /> === Import ===<br /> It would be very useful to be able to import scheduled events from the Moodle Calendar, Google Calendar, Outlook, MRBS etc straight into the attendance_sessions table and not have to manually recreate them.<br /> <br /> === Export ===<br /> For those using the attendance module as the primary place of scheduling events/sessions the ability to export that into Outlook, Google Calendar etc would be great. --[[User:Barry Oosthuizen|Barry Oosthuizen]] 06:15, 10 February 2009 (CST)<br /> <br /> ==Email Absentees==<br /> It would be useful for an instructor to be able to set a threshold (70% attendance or 50% attendance, etc), click on &quot;send email&quot; and send an email (via quickmail perhaps) to all students whose attendance is below the threshold. [[User:Dennis Williams 3|Dennis Williams 3]]<br /> <br /> ==Negative Impact on Grade==<br /> Our program lowers the grades of students if they pass a preset threshold of unexcused absences. If a student would have received a B in the course, if they miss 3 classes their grade is lowered to a B-. If they miss 4 classes, it is lowered to a C+, etc. Being able to lower the grade based on these criteria automatically would be desirable.<br /> <br /> = Now in development =<br /> <br /> = Released =<br /> <br /> == Multiply sessions in day ==<br /> ''Are we need a duration for sessions? (Dmitry)''<br /> <br /> 'We can do with sessions having a duration. We need to calculate the number of hours a student was in class per week as International Students have to fulfill the minimum requirement of 15 hours per week.'<br /> <br /> == Increase the number of categories ==<br /> It would make Attendance more flexible if you could increase the number of categories from the default of 4 to a maximum of 9. This would allow Attendance to be used for daily points, for example. The categories could be set up once under &quot;Settings&quot; as a drop-down menu &quot;Number of categories 4-9&quot; when you are also setting up letters and descriptions, but before sessions. You could leave the default at 4 to keep Attendance easy to use.<br /> <br /> ''This feature will be in near future. You be able to use unlimited number of statuses (categories). (Dmitry)''<br /> <br /> ==Export days not yet used in Excel or Open Office ==<br /> It would be good if you were able to export the days for the future that had not yet been filled in.<br /> <br /> I am thinking of a situation where someone might be having a problem with Moodle and has to go back to taking the details manually.<br /> In this case, the extra days would be handy. A copy of this could be kept aside for the staff member should the need ever arise.<br /> <br /> == Reset the module/Multiple module instances ==<br /> If I remove the module and then add it again, old attendance data remains. It would be great to be able to reset the module so that we can start attendance fresh for a new unit of a course.<br /> Even better would be the option of multiple attendance instances, so that we could have one module for each unit in a course!<br /> <br /> ''Possibility of reset already implemented in developer's version. Deleting data not always good, so we have simple way for hide unused data - just change course's start date to actual for current course.''<br /> <br /> Actually this does not work for '''units''' within a course.<br /> We need to have a course of for example three units, and to reset the attendance data for each unit. <br /> We can't change the start date for the entire course after only the first unit is over.<br /> <br /> ''Reset feature implemented''<br /> <br /> = See also =<br /> * [[Attendance module]] official page<br /> <br /> [[Category:Contributed code]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Calendar_settings&diff=45642 2008-10-21T17:46:45Z

<p>Hatshepsut: /* List format */</p> <hr /> <div>Location: ''Administration &gt; Appearance &gt; Calendar''<br /> <br /> <br /> The days and events to lookahead settings are for displaying events in the [[Upcoming Events block]]. If the Upcoming Events block becomes too long you can reduce the number of days and events to lookahead.<br /> <br /> <br /> ==Importing multiple events==<br /> <br /> Currently there is no way to import data to create multiple events. All events must be individually entered through the New Event button. Because the New Event data entry screen only allows drop down selection rather than typed entries, it is very difficult to design a macro for quick repeated input of New Events.<br /> <br /> The only other option is to directly connect to the central moodle [SQL] database and directly enter data into the events table. ''Great care'' needs to be taken with this approach as alterations to the data structure may cause your moodle site to crash!<br /> To convert MS Excel dates to moodle Unix dates use: Unix date integer =((Excel date integer)-25569)*86400<br /> <br /> ==List format==<br /> The calendar displays event lists one day at a time. There is no capacity to display a list of all site or course events over an extended period. To obtain date lists for publications, the only option is to link directly to the SQL database, select by the &quot;courseid&quot; and perform calculations to convert the UNIX &quot;timestart&quot; to a publishable date format:<br /> <br /> Using a Microsoft Access query, collect data from the '''mdl_event''' table and create 2 calculated fields:<br /> <br /> *'''calcdate''': DateValue(&quot;1/1/1970&quot;)+[timestart]/60/60/24+10/24<br /> *'''daysavdate''': IIf([calcdate] Between #2/04/2006# And #29/10/2006#,[calcdate],[calcdate]+1/24)<br /> <br /> Then, use additional calculated fields to separate the date, day of week and time (if needing to be formatted separately:<br /> <br /> *Dte: Format([daysavdate],&quot;mmm dd&quot;)<br /> *DayName: Format([daysavdate],&quot;ddd&quot;)<br /> *Tme: Format([daysavdate],&quot;hh:nn am/pm&quot;)<br /> <br /> PS: The dates for daylight saving need to be changed each year to match your location.<br /> PS: Very brief summary process for creating connection to moodle database in Windows environment: Install MySQL OBDC Driver 3.51 / Start settings control panel / admin tools/ Data Sources/ ODBC / add new service/ select MySQL ODBC driver/ follow prompts for User &amp; password/ open access/ get external data/ point to MySQL ODBC connection<br /> <br /> ==Navigating months==<br /> There is no easy way to jump to a specific month in the year other than to directly edit the URL variable for month &quot;m=&quot; : calendar/view.php?view=month&amp;cal_d=1&amp;cal_'''m=02'''&amp;cal_y=2006<br /> <br /> ==Display Current Day Events==<br /> <br /> Use link: http://moodle.org/calendar/view.php?view=day<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=52320 URL to show today's calendar] forum discussion<br /> <br /> [[Category:Administrator]]<br /> [[Category:Calendar]]<br /> <br /> [[fr:Calendrier (administrateur)]]<br /> [[ja:カレンダー ( 管理者 )]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Capabilities/moodle/site:accessallgroups&diff=45641 2008-10-21T17:23:57Z

<p>Hatshepsut: </p> <hr /> <div>*This allows a user to access all [[Groups|groups]] in the given context (system, front page, course category or course context), irrespective of what group the user is in or whether they are in a group at all. For example, a user with this capability set to allow can browse forum postings of users in other groups when the forum is set to separate groups. <br /> *The default teacher and non-editing teacher roles have this capability set to allow.<br /> <br /> Note: Users with a role in which [[Capabilities/moodle/course:managegroups|moodle/course:managegroups]] is allowed and moodle/site:accessallgroups is not set are able to add/delete/update groups (and groupings, if enabled) in a course.<br /> <br /> <br /> [[Category:Capabilities|Site]]<br /> [[Category:Groups]]<br /> <br /> [[zh:能力/moodle/site:accessallgroups]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Groupings&diff=45510 2008-10-20T09:13:45Z

<p>Hatshepsut: /* See also */ removed link to video because video is no longer publicly available</p> <hr /> <div>{{Moodle 1.9}}In Moodle 1.9 onwards, [[Groups|groups]] may be organised into a grouping, in other words, a collection of groups within a course.<br /> <br /> <br /> ==Enabling the use of groupings==<br /> To use groupings, the feature must be enabled by checking the enablegroupings box in ''Administration &gt; Miscellaneous &gt; [[Experimental]]''. This will result in a groupings tab appearing on the [[Groups]] page.<br /> <br /> ==Adding groups to a grouping==<br /> [[Image:Groupings.png|thumb|Groupings]]<br /> To add groups to a grouping: <br /> #Follow the groups link in the course administration block.<br /> #Click the groupings tab on the groups page.<br /> #If necessary, create a new grouping by clicking the &quot;[[Create grouping]]&quot; button on the groupings page.<br /> #Click the &quot;Show groups in grouping&quot; people icon in the edit column opposite the grouping which groups are to be added to.<br /> #On the add/remove groups page, select the group(s) you want to add to the grouping from the &quot;Potential members&quot; list.<br /> #Click the arrow button that points towards the &quot;Existing members&quot; list.<br /> #Click the &quot;Back to groupings&quot; button. The group(s) you added to the grouping will now be listed in the table on the groupings page.<br /> <br /> Existing groupings can be edited and/or deleted using the appropriate icons in the edit column of the table on the groupings page.<br /> <br /> ==Setting the default grouping==<br /> <br /> Once some groupings have been created, a default grouping for course activities and resources may be set.<br /> <br /> #Follow the settings link in the course administration block.<br /> #In the groups section in the [[Course settings|course settings]], select the default grouping.<br /> <br /> ==Assigning an activity to a grouping==<br /> [[Image:Restricting an activity to a grouping.png|thumb|Assigning an activity to a particular grouping only]]<br /> To assign an activity to a particular grouping:<br /> #On the edit activity page, click the &quot;Show advanced&quot; button in the common module settings section.<br /> #Ensure that the group mode is set to separate or visible groups.<br /> #Select the grouping from the grouping dropdown menu.<br /> #Click the &quot;Save changes&quot; button at the bottom of the page.<br /> <br /> The name of the grouping will then appear in brackets after the activity name on the course page.<br /> A count of activities assigned to each grouping is kept on the groupings page.<br /> <br /> To assign an activity to a particular grouping ONLY, in addition to the above, before clicking the the &quot;Save changes&quot; button, check the &quot;Available for group members only&quot; checkbox. This will result in only users assigned to the groups within the grouping being able to see the activity (or resource) on the course page.<br /> <br /> :''Note'': If a graded activity is assigned to a particular grouping only, it will still appear in the gradebook for all users. (See MDL-13868 for further details.)<br /> <br /> ==See also==<br /> *Curious about where 'groupings' came from? There is some discussion here: [[Development:Groupings OU]]<br /> <br /> [[Category:Groups]]<br /> <br /> [[fr:Groupements]]<br /> [[ja:グルーピング]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=News_forum&diff=45342 2008-10-14T19:09:06Z

<p>Hatshepsut: </p> <hr /> <div>{{Forums}}<br /> The News forum is a special forum for general announcements. A course may only have one News forum unless it has been imported from another system which supports more than one news forum.<br /> <br /> This forum is automatically created for each course and for the [[Front Page|front page]] of the Moodle site. By default, it is placed in the top of the center section and only teachers and administrators may add posts or reply to posts. Also the [[Adding/editing a forum|default settings]] forces every enroled person to be subscribed to the News forum.<br /> <br /> The [[Latest News block]] displays a [[Course_settings#News_items_to_show|specific number]] of recent discussions from the News forum. <br /> <br /> As with any forum, emails can be sent to subscribed members of a News forum.<br /> <br /> ==Removing the news forum==<br /> <br /> The news forum may be removed from a course as follows:<br /> #Delete the news forum from the course homepage<br /> #In [[Course settings]] set &quot;News items to show&quot; to 0<br /> #Delete the Latest news block<br /> #Alternatively - hide the news forum<br /> <br /> ==See also==<br /> <br /> *[[Upgrading to Moodle 1.8]] for steps to enable logged-in users to read the site news<br /> <br /> [[fr:Forum des nouvelles]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Outcomes&diff=45047 2008-10-10T09:12:42Z

<p>Hatshepsut: /* See also */ removed dead link</p> <hr /> <div>{{Grades}}Outcomes are specific descriptions of what a student is expected to be able to do or understand at the completion of an activity or course. An activity might have more than one outcome, and each may have a grade against it (usually on a scale). Other terms for Outcomes are ''Competencies'' and ''Goals''. In simple terms an Outcome is like any other grade except that it can be applied to multiple activities. When the activity is marked, a mark should be given for the submission itself '''and''' for the outcome. <br /> <br /> <br /> ==Enabling outcomes==<br /> <br /> To use outcomes, the feature must be enabled by an administrator by checking the enableoutcomes box in ''Administration &gt; Grades &gt; [[General grade settings|General settings]]''.<br /> <br /> ==Using outcomes==<br /> <br /> # Choose or define some outcomes for your course (see below).<br /> # For each activity, choose which of these outcomes apply using the tickbox in the activity's settings page.<br /> # When grading that activity, grade each student using the Outcome scales. Note: You can also edit the grades in the [[Grader report]] (useful for modules that don't feature inbuilt grading).<br /> # Use the outcomes as part of the assessment for students, or look at the [[Outcomes report]] for some useful feedback on how students in the class in general are performing.<br /> <br /> ==Outcomes used in course==<br /> <br /> Outcomes may be set at site and/or course level. To choose outcomes for use in your course:<br /> <br /> # Follow the outcomes link in the course administration block. (Alternatively, select outcomes from the gradebook view dropdown menu.)<br /> # Select standard outcomes from the right list, and use the left-facing arrow button to add them to the left list. Multiple outcomes may be selected by holding down the Apple or Ctrl key whilst clicking on the individual outcomes.<br /> <br /> ==Adding course-level outcomes==<br /> <br /> [[Image:Adding an outcome.png|thumb|Adding an outcome]]To add a course-level outcome:<br /> <br /> # Follow the outcomes link in the course administration block. (Alternatively, select outcomes from the gradebook view dropdown menu.)<br /> # Click the &quot;Edit outcomes&quot; tab in the middle of the page.<br /> # Click the &quot;Add a new outcome&quot; button.<br /> # Complete the form then click the &quot;Save changes&quot; button. <br /> <br /> ==Adding standard outcomes==<br /> <br /> To add standard outcomes, which are available site-wide:<br /> <br /> # Login as an administrator.<br /> # Access ''Site administration &gt; Grades &gt; Outcomes''.<br /> # Click the &quot;Add a new outcome&quot; button.<br /> # Complete the form then click the &quot;Save changes&quot; button. <br /> <br /> ==Import/export of outcomes==<br /> <br /> Outcomes (and their associated scales) can be exported by clicking the &quot;Export all outcomes&quot; button. This will send a file (in .csv format) that can be read by Excel, OpenOffice.org or by any text editor.<br /> <br /> It's possible to import outcomes (and associated scales) by submitting a csv file. The format of the file should be copied from the file obtained by the export function. Note that while importing: <br /> *Existing outcomes and scale will be used if available (no overwriting is done by the script)<br /> *The script will stop if it detects that the file contains invalid data.<br /> <br /> ==Removing selected outcomes for activities==<br /> <br /> Previously selected outcomes are greyed out on the update activity page, however they can be removed via the gradebook edit categories and items page. This results in the outcomes being deselected on the update activity page.<br /> <br /> ==See also==<br /> *[[Outcomes report]]<br /> *[[Development:Outcomes]]<br /> *[[Development:Outcomes examples]]<br /> *[http://www.youtube.com/watch?v=PmkEGfvjj9U Video on how to use outcomes in Moodle]<br /> *[http://youtube.com/watch?v=sUslTuZPu6A Video on &quot;Grade Category Settings&quot; and &quot;Outcomes&quot;]<br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=78074 Outcomes in 1.9] forum discussion<br /> *[[General grade settings]]<br /> <br /> <br /> [[ca:grade/edit/outcome/course]]<br /> [[fr:Objectifs]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Release_Nots&diff=22024 2007-04-01T22:57:13Z

<p>Hatshepsut: /* Moodle 1.1 */</p> <hr /> <div>==Moodle 1.1==<br /> <br /> Moodle 1.1 is our most stable release. Free of all the features that plagued subsequent versions it is the one to use if you demand stability. Our patent application for this wonderful product has also been approved by the US Patent Office so you do not have to worry about any commercial companies ever taking over the LMS market and suing you for using Moodle.<br /> <br /> Features include:<br /> <br /> * Cool new forum module<br /> * Users no longer have to all share one account<br /> * you can now enter your own resources<br /> * &quot;graphics&quot; allow display of information via non-textual means<br /> * Finally working over http<br /> * ActiveX controls have all been replaced by much more reliable and secure Java applets<br /> * New &quot;Video&quot; course format allows you to expand your Moodle experience by interacting with modern Beta VCRs.<br /> * Takes care of your children while your at work.<br /> <br /> Please add more features here if I forgot any!<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> More information can be found here: [http://en.wikipedia.org/wiki/April_fools April Fools].</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Edita_par%C3%A0metres&diff=18097 2006-11-21T21:36:27Z

<p>Hatshepsut: /* Course start date */</p> <hr /> <div>{{Help files}}<br /> {{Course admin}}<br /> <br /> Course settings control how the things appear to the participants in a course. It is the first page viewed after creating a course. It can be edited throught the '''settings''' link in the [[Administration block]] menu. This page has links to other pages that may describe a setting in more detail. Different versions of Moodle may not have all the settings listed below.<br /> <br /> ==Category==<br /> A Moodle administrator or course creator may have set up several course categories.<br /> <br /> For example, &quot;Science&quot;, &quot;Humanities&quot;, &quot;Public Health&quot; etc<br /> <br /> Choose the one most applicable for your course. This choice will affect where your course is displayed on the course listing and may make it easier for students to find your course.<br /> <br /> ==Full name==<br /> The full name of the course is displayed at the top of the screen and in the course listings.<br /> <br /> ==Short name==<br /> Many institutions have a shorthand way of referring to a course, such as BP102 or COMMS. Even you don't already have such a name for your course, make one up here. It will be used in several places where the long name isn't appropriate. The most common use is in the navigation bar that is at the top of most pages.<br /> <br /> [[Image:Assignment nav trail.jpg|The underlined part is the course Short name.]]<br /> <br /> The the above example has the short course name, &quot;Features&quot;. The short name also appears in the subject line of email messages that are part of the course.<br /> <br /> ==ID number==<br /> The ID number is an alpha numeric field. It has several potential uses. Generally it is not displayed to students. However, it can be used to match this course against an external system's ID, as your course catalog ID or can be used in the certificate module as a printed field.<br /> <br /> ==Summary==<br /> The summary of the course is displayed in the course listings.<br /> <br /> ==Format==<br /> A Moodle course may use one of the following three formats:<br /> <br /> '''Weekly format'''<br /> <br /> The course is organised week by week, with a clear start date and a finish date. Each week consists of activities. Some of them, like journals, may have &quot;open windows&quot; of, say, two weeks after which they become unavailable.<br /> <br /> '''Topics format'''<br /> <br /> Very similar to the weekly format, except that each &quot;week&quot; is called a topic. A &quot;topic&quot; is not restricted to any time limit. You don't need to specify any dates.<br /> <br /> '''Social format'''<br /> <br /> This format is oriented around one main forum, the Social forum, which appears listed on the main page. It is useful for situations that are more freeform. They may not even be courses. For example, it could be used as a departmental notice board.<br /> <br /> In Moodle 1.6 this is increased by:<br /> <br /> '''LAMS course format''' [[LAMS]]<br /> <br /> '''SCORM format''' [[SCORM]]<br /> <br /> '''Weekly format, CSS/no tables'''<br /> Just an educated guess: This version of the weekly format uses the more modern web layout system CSS (cascading style sheets) to place things on the web page in a more flexible way than the old method with tables.<br /> <br /> '''non-standard formats'''<br /> <br /> such as a patch to allow javascript-based [[layout course editing]]<br /> <br /> ==Course start date==<br /> This is where you specify the starting time of the course (in your own timezone).<br /> <br /> If you are using a 'weekly' course format, this will affect the display of the weeks. The first week will start on the date you set here.<br /> <br /> This setting will not affect courses using the 'social' or 'topics' formats.<br /> <br /> However, one place this setting will have an effect is the display of logs, which use this date as the earliest possible date you can display.<br /> <br /> In general, if your course does have a real starting date then it makes sense to set this date to that, no matter what course formats you are using.<br /> <br /> ==Enrolment plugins==<br /> {{Moodle 1.7}}<br /> <br /> ==Default role==<br /> {{Moodle 1.7}}<br /> <br /> ==Course enrollable==<br /> Yes, No or give start and end date range.<br /> <br /> ==Enrolment duration==<br /> This setting specifies the number of days a student can be enrolled in this course (starting from the moment they enroll).<br /> <br /> If this is set, then students are automatically unenrolled after the specified time has elapsed. This is most useful for rolling courses without a specific start or end time.<br /> <br /> If you don't set this then the student will remain in this course until they are manually unenrolled or the clean-up function to remove defunct students takes effect.<br /> <br /> If you have selected to manage this course as a meta course, your enrolment period will not be used.<br /> <br /> ==Expired enrolment notification==<br /> Options to notify teacher, student and define threshold for notification.<br /> <br /> ==Number of weeks/topics==<br /> This setting is only used by the 'weekly' and 'topics' course formats.<br /> <br /> In the 'weekly' format, it specifies the number of weeks that the course will run for, starting from the course starting date.<br /> <br /> In the 'topics' format, it specifies the number of topics in the course.<br /> <br /> Both of these translate to the number of &quot;boxes&quot; down the middle of the course page.<br /> <br /> ==Group mode==<br /> Here you can define the group mode at the course level. This will be the default group mode for all activities defined within that course. Learn more about [[Groups]]<br /> <br /> Note that you don't '''need''' to change this setting to enable groups. The default setting of this and 'Force' enables each activity to have its group mode set individually.<br /> <br /> ===Force===<br /> If the group mode is &quot;forced&quot; at a course-level, then this particular group mode will be applied to every activity in that course. Individual group settings in each activity are then ignored.<br /> <br /> This is useful when, for example, one wants to set up a course for a number of completely separate cohorts.<br /> <br /> ==Availability==<br /> <br /> This option allows you to &quot;hide&quot; your course completely. It will not appear on any course listings, except to teachers of the course and administrators. Even if students try to access the course URL directly, they will not be allowed to enter.<br /> <br /> ==Enrolment key==<br /> A course enrolment key enables access to courses to be restricted to those who know the key.<br /> <br /> If left blank, then anyone who has created a Moodle username on the site will be able to enrol in the course.<br /> <br /> If a key is specified, then students who are trying to enter will be asked to supply the key. Once enrolled, Students are not required to enter an enrollment key to gain access.<br /> <br /> The idea is that Teachers supply the key to authorised people using another means like private email, snail mail, on the phone or even verbally in a face to face class.<br /> <br /> If this password &quot;gets out&quot; and you have unwanted people enrolling, you can unenrol them (see their user profile page) and change this key. Any legitimate students who have already enrolled will not be affected, but the unwanted people won't be able to get back in.<br /> <br /> ==Guest access==<br /> You have the choice of allowing [[Guest access | &quot;guests&quot;]] into your course or not, and if they need an enrolment key or enter without one. <br /> <br /> People can attempt to log in as guests using the &quot;Login as a guest&quot; button on the course login screen.<br /> <br /> Guests ALWAYS have &quot;read-only&quot; access - meaning they can't leave any posts or otherwise mess up the course for real students. No use information is stored for a guest.<br /> <br /> This can be handy when you want to let a colleague in to look around at your work, or to let students see a course before they have decided to enrol.<br /> <br /> Note that you have a choice between two types of guest access: with the enrolment key or without. If you choose to allow guests who have the key, then the guest will need to provide the current enrolment key EVERY TIME they log in (unlike students who only need to do it once). This lets you restrict your guests. If you choose to allow guests without a key, then anyone can get straight into your course.<br /> <br /> ==Cost==<br /> The course cost will be shown if you have selected another enrolment method except internal.<br /> <br /> ==Hidden sections==<br /> This option allows you to decide how the hidden sections in your course are displayed to students. By default, a small area is shown (in collapsed form, usually gray) to indicate where the hidden section is, though they still can not actually see the hidden activities and texts. This is particularly useful in the Weekly format, so that non-class weeks are clear.<br /> <br /> If you choose, these can be completely hidden, so that students don't even know sections of the course are hidden.<br /> <br /> ==News items to show==<br /> A special forum called &quot;News&quot; appears in the &quot;weekly&quot; and &quot;topics&quot; course formats. It's a good place to post notices for all students to see. (By default, all students are subscribed to this forum, and will receive your notices by email.)<br /> <br /> This setting determines how many recent items appear on your course home page, in a news box down the right-hand side.<br /> <br /> If you set it to &quot;0 news items&quot; then the news box won't even appear.<br /> <br /> ==Show grades==<br /> Many of the activities allow grades to be set. By default, the results of all grades within the course can be seen in the Grades page, available from the main course page.<br /> <br /> If a teacher is not interested in using grades in a course, or just wants to hide grades from students, then they can disable the display of grades with this option. This does not prevent individual activities from using or setting grades, it just disables the results being displayed to students.<br /> <br /> ==Show activity reports==<br /> Activity reports are available for each participant that show their activity in the current course. As well as listings of their contributions, these reports include detailed access logs.<br /> <br /> Teachers always have access to these reports, using the button or tab visible on each persons's profile page.<br /> <br /> Student access to their own reports is controlled by the teacher via this course setting. For some courses these reports can be a useful tool for a student to reflect on their involvement and appearance within the online environment, but for some courses this may not be necessary.<br /> <br /> Another reason for turning it off is that the report can place a bit of load on the server while being generated. For large or long classes it may be more efficient to keep it off.<br /> <br /> ==Maximum upload size==<br /> This setting defines the largest size of file that can be uploaded by students in this course, limited by the site wide setting created by the administrator.<br /> <br /> It is possible to further restrict this size through settings within each activity module.<br /> <br /> ==Your word for Teacher/Teachers/Student/Students==<br /> You can change the words for teacher and student for a particular course.<br /> <br /> ==Force language==<br /> If you force a language in a course, the interface of Moodle in this course will be in this particular language, even if a student has selected a different preferred language in his/her personal profile.<br /> <br /> ==Is this a meta course?==<br /> A [[Metacourses|metacourse]] automatically enrols its participants from other courses. For example, for every course that is a &quot;child&quot; of the metacourse, all students in the child course are enroled in the metacourse.<br /> <br /> <br /> [[Category:Teacher|Course/edit]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=You_Might_Be_a_Moodler&diff=16540 2006-10-01T14:28:18Z

<p>Hatshepsut: </p> <hr /> <div>In the spirit of Jeff Foxworthy's ''You Might be a Redneck'' - http://www.jefffoxworthy.com/comedy/jod/index.shtml <br /> <br /> *If you have ever turned on a football game and and the orange uniforms of one team caused you to leap up from the sofa and check out moodle.org, you might be a Moodler.<br /> <br /> *If you type &quot;moodle.org&quot; in your browser when you intend to type &quot;google.com.&quot;<br /> <br /> *If you look up recipes in moodle.org.<br /> <br /> *If you look up recipes in moodle.org... and [http://moodle.org/mod/forum/discuss.php?d=5395&amp;parent=30227 find them]!<br /> <br /> *If you can spell '''Dougiamas''' without having to look it up.<br /> <br /> *If you can ''pronounce'' '''Dougiamas''' without having to look it up.<br /> <br /> *If you check the Moodle forums at 8:30 on a Saturday night.<br /> <br /> *If you find yourself heading to the bugtracker when the dishwasher is broken.<br /> <br /> *If you start seeing double square brackets around words you don't know the translation of.<br /> <br /> *If your neighbours wonder why you named your cats Helen and Howard.<br /> <br /> *Your spouse wants you to take up golf again because they hate being a 'moodle widow(er)' more.<br /> <br /> *You describe the color of something as &quot;Moodle&quot; orange.<br /> <br /> *If you find yourself logging in to moodle.org during your summer holiday in Italy instead of enjoying the beautiful view or going to the beach. (Hi from Italy, Sigi)<br /> <br /> *If you come all the way from Germany to the US during your summer holiday and in addition to visiting lots of places you must absolutely go to a small town in South Carolina to find out about the latest Moodle tricks<br /> <br /> *You try to figure out how to grade e-mails from your friends without a drop down box<br /> <br /> *You find moodle.org is down for some reason and the first thing you want to do is post on moodle.org about it.<br /> <br /> *Every verb you use is 'to moodle'.<br /> <br /> *You go into a Chinese restaurant and ask for a side order of Moodles with your Egg Foo Young.<br /> <br /> *You talk about Moodle so much that your non-Moodling, non-native English speaking husband asks if the noodles on the plate in front of him are moodles and when you ask him if that is what he meant to say he replies, &quot;Yes, aren't they moodles?&quot; (based on a true story)<br /> <br /> *You know that the course id for '''Using Moodle''' is 5.<br /> <br /> *And even if you drive a car, you always drive it in '''5'''th gear.<br /> <br /> *You throw away all but the orange M&amp;amp;M's.<br /> <br /> *You eat all but the orange M&amp;amp;M's (and keep it for good ''feng shui'' in your desktop).<br /> <br /> *You try to convince your wife and kids that there is a Disney Park in Perth.<br /> <br /> *The homepage of your computer is http://www.moodle.org.<br /> <br /> *The homepage of every computer you have ever laid hands on is http://www.moodle.org.<br /> <br /> *You only recently discovered that typing an address in your browser takes you to a page outside Moodle.org<br /> <br /> *You sometimes refer to your third child as '''1.3'''<br /> <br /> *Your default response to a rerun on TV is to fire up the laptop and check out moodle.org.<br /> <br /> *If you put little labels on your TV's remote control that say... view.php?id=1, view.php?id=2, etc ...<br /> <br /> *You have five browser windows open right now, four of which are Moodle sites.<br /> <br /> *Reading the moodle.org forums is part of the morning routine: coffee, newspaper, wake up the children. . .<br /> <br /> *You find yourself adding items to a list that only the Moodle clique will understand.<br /> <br /> *You tell people to &quot;Keep Moodling&quot; and that they have been &quot;Moodlised&quot;<br /> <br /> *If instead of saying ''Have a good day'' you begin greeting folks by saying ''Happy Moodling!'' and even worse when you actually believe that the two statements mean the same thing. {Based on a true story}<br /> <br /> *If normal words start being morphed into ''Moodle-isms''. For example, when someone asks ''How are you?'' you begin to reply with words like Moodle-rrific and Moodle-tastic. Subsequently, you get confused when someone gives you a quizzical look because they do not understand what have just said. {Based on a true story}<br /> <br /> *If your students start showing up to the Friday night football games wanting to know when the Moodle chant is going to begin and students begin painting ''MOODLE'' on their chests! {Based on a true story}<br /> <br /> *You get custom plates for your new car... [http://moodle.org/mod/forum/discuss.php?d=54899 Moodle Plate]<br /> <br /> *You get a quote on a custom paint job for your new car [http://classroomrevolution.com/jeff/moodleorange.jpg Moodle Orange Car]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=You_Might_Be_a_Moodler&diff=16539 2006-10-01T14:27:47Z

<p>Hatshepsut: </p> <hr /> <div>In the spirit of Jeff Foxworthy's ''You Might be a Redneck'' - http://www.jefffoxworthy.com/comedy/jod/index.shtml <br /> <br /> *If you have ever turned on a football game and and the orange uniforms of one team caused you to leap up from the sofa and check out moodle.org, you might be a Moodler.<br /> <br /> *If you type &quot;moodle.org&quot; in your browser when you intend to type &quot;google.com.&quot;<br /> <br /> *If you look up recipes in moodle.org.<br /> <br /> *If you look up recipes in moodle.org... and [http://moodle.org/mod/forum/discuss.php?d=5395&amp;parent=30227 find them]!<br /> <br /> *If you can spell '''Dougiamas''' without having to look it up.<br /> <br /> *If you can ''pronounce'' '''Dougiamas''' without having to look it up.<br /> <br /> *If you check the Moodle forums at 8:30 on a Saturday night.<br /> <br /> *If you find yourself heading to the bugtracker when the dishwasher is broken.<br /> <br /> *If you start seeing double square brackets around words you don't know the translation of.<br /> <br /> *If your neighbours wonder why you named your cats Helen and Howard.<br /> <br /> *Your spouse wants you to take up golf again because they hate being a 'moodle widow(er)' more.<br /> <br /> *You describe the color of something as &quot;Moodle&quot; orange.<br /> <br /> *If you find yourself logging in to moodle.org during your summer holiday in Italy instead of enjoying the beautiful view or going to the beach. (Hi from Italy, Sigi)<br /> <br /> *If you come all the way from Germany to the US during your summer holiday and in addition to visiting lots of places you must absolutely go to a small town in South Carolina to find out about the latest Moodle tricks<br /> <br /> *You try to figure out how to grade e-mails from your friends without a drop down box<br /> <br /> *You find moodle.org is down for some reason and the first thing you want to do is post on moodle.org about it.<br /> <br /> *Every verb you use is 'to moodle'.<br /> <br /> *You go into a Chinese restaurant and ask for a side order of Moodles with your Egg Foo Young.<br /> <br /> *You talk about Moodle so much that your non-Moodling, non-native English speaking husband asks if the noodles on the plate in front of him is moodles and when you ask him if that is what he meant to say he replies, &quot;Yes, aren't they moodles?&quot; (based on a true story)<br /> <br /> *You know that the course id for '''Using Moodle''' is 5.<br /> <br /> *And even if you drive a car, you always drive it in '''5'''th gear.<br /> <br /> *You throw away all but the orange M&amp;amp;M's.<br /> <br /> *You eat all but the orange M&amp;amp;M's (and keep it for good ''feng shui'' in your desktop).<br /> <br /> *You try to convince your wife and kids that there is a Disney Park in Perth.<br /> <br /> *The homepage of your computer is http://www.moodle.org.<br /> <br /> *The homepage of every computer you have ever laid hands on is http://www.moodle.org.<br /> <br /> *You only recently discovered that typing an address in your browser takes you to a page outside Moodle.org<br /> <br /> *You sometimes refer to your third child as '''1.3'''<br /> <br /> *Your default response to a rerun on TV is to fire up the laptop and check out moodle.org.<br /> <br /> *If you put little labels on your TV's remote control that say... view.php?id=1, view.php?id=2, etc ...<br /> <br /> *You have five browser windows open right now, four of which are Moodle sites.<br /> <br /> *Reading the moodle.org forums is part of the morning routine: coffee, newspaper, wake up the children. . .<br /> <br /> *You find yourself adding items to a list that only the Moodle clique will understand.<br /> <br /> *You tell people to &quot;Keep Moodling&quot; and that they have been &quot;Moodlised&quot;<br /> <br /> *If instead of saying ''Have a good day'' you begin greeting folks by saying ''Happy Moodling!'' and even worse when you actually believe that the two statements mean the same thing. {Based on a true story}<br /> <br /> *If normal words start being morphed into ''Moodle-isms''. For example, when someone asks ''How are you?'' you begin to reply with words like Moodle-rrific and Moodle-tastic. Subsequently, you get confused when someone gives you a quizzical look because they do not understand what have just said. {Based on a true story}<br /> <br /> *If your students start showing up to the Friday night football games wanting to know when the Moodle chant is going to begin and students begin painting ''MOODLE'' on their chests! {Based on a true story}<br /> <br /> *You get custom plates for your new car... [http://moodle.org/mod/forum/discuss.php?d=54899 Moodle Plate]<br /> <br /> *You get a quote on a custom paint job for your new car [http://classroomrevolution.com/jeff/moodleorange.jpg Moodle Orange Car]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Tracker&diff=16171 2006-09-22T12:54:16Z

<p>Hatshepsut: /* See also */</p> <hr /> <div>[[Image:MoodleTracker_logo.JPG]] <br /> <br /> Bug tracking is a very important part of a continous quality control process. Unlike most proprietary software programs, Moodle bug reporting and bug tracking information is open to everyone. Moodle's bug tracking system is called '''[http://tracker.moodle.org Tracker]'''. Tracker is a slightly customised version of Atlassian's product [http://www.atlassian.com/software/jira/ Jira]. <br /> <br /> If you're a new Tracker user create a user account [http://tracker.moodle.org here]. It is strongly suggested your Tracker username is the same name you use at Moodle.org. If your Tracker login account doesn't work, try recovering the password. <br /> <br /> &quot;Bugs&quot; not only include software problems with current versions of Moodle, but requests for new features (enhancements), changes in functionality, even constructive criticism of existing features is welcome.<br /> <br /> The beauty of open source is that anyone can participate and help to create a better product for all of us to enjoy. In this project, your input is very welcome!<br /> <br /> == General reporting guidelines ==<br /> <br /> The best bug reports contain these elements in the form:<br /> <br /> #'''Steps to reproduce'''. That is, a detailed sequence of steps a developer can follow to see the problem. It is very hard to fix a bug that is not reproducible. If possible, provide a URL so we can see the problem with one click.<br /> #'''What I expected to happen'''. Again, provide as much detail as possible. Your expectation might mean that our instructions need to be improved or our interface should be changed.<br /> #'''What actually happened''' (with detail).<br /> <br /> Here is an example of a [http://tracker.moodle.org/browse/MDL-6030 good bug report] in browse view, [http://tracker.moodle.org/browse/MDL-5688 and here is another].<br /> <br /> *If you have an error message, or information in your PHP or web server logs, copy and paste it into the bug report. If you can, turn on &quot;debug&quot; in your Admin configuration page and reproduce the problem to get the best possible error message.<br /> *Screen shots are very helpful for some bugs, but please write a textual description of the problem too.<br /> *Make sure we know everything we need to know about your setup including operating system, database, etc. If you run out of room in the environment section, add more detail in the description. The full set of information that might be relevant is:<br /> **Server operating system type and version number<br /> **Web server type and version number<br /> **PHP version number (and whether you are using an accelerator)<br /> **Database type and version number<br /> **Moodle version (there is a dropdown menu on the top of the form, if that does not have what you want, add it in the description)<br /> **Client-side operating system type and version number<br /> **Web browser type and version number<br /> <br /> You don't need to give all those details all the time. For example, for a layout rendering problem, you need to give only the client-side OS and browser info, and if it is a server-side problem you only need to describe the setup there. Use your judgment. Here are some examples:<br /> <br /> ::I see this bug with the latest Moodle HEAD running on PHP5.1.2/Apache 2.2.3 on Linux. My database is Postgres 8.1.<br /> <br /> ::This rendering problem happens using Internet Explorer 6.0 on Windows XP.<br /> <br /> In summary stick with facts and present enough facts so someone else can duplicate the problem.<br /> <br /> == Report a bug ==<br /> *Login to the [http://tracker.moodle.org Tracker]<br /> *Select &quot;Create New Issue&quot; from the menu under the Moodle Tracker logo<br /> *Step 1, from the dropdown menu select the &quot;Issue type&quot;: Bug, New Feature, Task or Improvement<br /> *Step 2, you will see a series of dropdown and blank content areas<br /> **Summary: A headline summary of the problem. Try to make it as precise as possible without making it too long. &quot;It doesn't work&quot; is completely useless. Think about keywords people might type into the search box if looking for this issue, and try to include them.<br /> **Components: Use the Ctrl key with a mouse click to select one or more areas in Moodle. For example, you might have found an issue with a question that impacts: Lesson, Quiz and Question components<br /> **Select the Version but if it is not listed, put it in the description<br /> **Environment is for Operating Systems and other stuff. See general guidelines below<br /> **Description tells what is the issue. See general guidelines below for the best description<br /> **Database, if it is not listed put it in environment with its version number<br /> <br /> ==Tracker process for fixing bugs==<br /> *Bugs are assigned by developers or Component Leads.<br /> *Developers modify or add code and check into CVS.<br /> *Appropriate comments are added in Tracker. The bug's status is changed to '''Resolved''' by using the &quot;Resolve Issue&quot; button. <br /> *You must indicate the version of Moodle in which the change has been made. Do this by selecting the appropriate Moodle version in '''Fix Version/s'''. <br /> *The only exception to not moving a bug to Resolved is if a developer believes there is no value in testing the issue, in which case the bug status can be changed to Closed.<br /> <br /> ==Tracker process for testing bugs==<br /> If you are interested in becoming a member of the Moodle Testing team send a request to &lt;tba&gt;.<br /> *Testers test bugs with Status=Resolved. Global filters have been created based on upcoming releases (eg 1.7 Resolved) to make idendification simple. <br /> *Use the '''QA Assignee''' field to identify yourself as the tester of a particular bug. Obviously you should have the skills and knowledge to sufficiently test the issue. Experience is important, but doen't forget there are others in the community that may be able to help you. <br /> *It's a good idea to add your name to the watch list for all bugs you test. (see &quot;Tracking watch list&quot;, below.) <br /> *If the bug passes testing, close the bug using the &quot;Close Issue&quot; button. You must add appropriate '''comments''' describing your testing methods, any issues that were found, etc.<br /> *If the bug fails testing or if you feel the fix is incomplete, '''reopen''' the bug using the &quot;Reopen Issue&quot; button. Ensure the bug is assigned to the correct developer. Work with the developer to find a mutually agreeable resolution to the bug. <br /> *A release will be deemed ready when all bugs fixed for a particular version have been closed.<br /> <br /> ==More about Tracker functionality==<br /> *The Tracker &quot;Dashboard&quot; is flexible and customisable depending on your area of interest. For instructions on configuring the Tracker dashboard click [http://www.atlassian.com/software/jira/docs/v3.6.3/dashboard.html here].<br /> *The Tracker Issue Navigator is used to find and filter bugs. For instructions on configuring the Issue Navigator click [http://www.atlassian.com/software/jira/docs/v3.6.4/navigatorcolumns.html here].<br /> *Tracker's &quot;Quick Search&quot; capability is explained [http://www.atlassian.com/software/jira/docs/v3.6.4/quicksearch.html here]<br /> <br /> == Tracker groups and permissions ==<br /> '''Standard Users''' [groupname=jira-user] - This is the default group. New user accounts are placed in this group at the time of creation, and users must be a member of this group in order to log into Tracker. Members of this group can browse bugs, create new bugs, comment on bugs, create attachments, create sub-tasks, create filters, watch bugs, and vote for bugs. Members of this group can also resolve bugs, which is primarily a way of closing bugs that are no longer relevant (eg duplicates, or logged in error). Standard Users can configure their Tracker workspace by using the &quot;Configure your Issue Navigator&quot; button. This feature allows users to view watch and voting lists and to manage preferences, profile, and password.<br /> <br /> '''Developers''' [groupname=jira-developer] - Developers can do everything Standard Users can do. In addition they can clone bugs, close bugs, edit bugs, link bugs, and assign bugs. Members of this group can also use the Bulk Edit function which allows bulk updated to multiple bugs. <br /> <br /> '''Testers''' [groupname=moodle-testers] - Testers can do everything a Developer can do.<br /> <br /> == Tracker priority levels ==<br /> <br /> Bugs can be assigned to one of five priority levels. Here is some guidance as to which one to use:<br /> <br /> ;Blocker<br /> :This bug completely breaks Moodle, and the next release must be considered &quot;blocked&quot; until this is done.<br /> ;Critical<br /> :This bug is causing data loss, serious visible errors for uses, or major parts of Moodle to cease to function.<br /> ;Major<br /> :Something is broken and there is no way round it, although it is not a serious as a Critical bug, we can't live with it for long. <br /> ;Minor<br /> :Something is wrong, but it is possible to live with it for a while, maybe because there is a workaround.<br /> ;Trivial<br /> :Something is wrong, and should be fixed eventually when someone has the time, but it is not a big deal to live with it.<br /> <br /> == Tracker versions ==<br /> <br /> There are 2 version fields in Tracker:<br /> <br /> *'''Affects version''' - this is the version in which the bug has been found. It is entered by the person logging the bug, and normally only 1 version is specified.. This information will help developers and testers identify where the problem is occuring. <br /> *'''Fix for version''' - this is the version the bug was or will be fixed in. This field is completed by the developer when the bug has been resolved. Normally only one version is specified in this field. It identifies the ''first'' version of Moodle where the change will be seen. For instance, the bug affecting 1.6 and 1.6.1 might be fixed in 1.7.<br /> <br /> <br /> ==Tracking progress of bugs you have reported==<br /> <br /> You will receive email reports of updates to bugs you report.<br /> <br /> ==Tracker watch lists==<br /> <br /> You can monitor, or &quot;watch&quot; bugs reported by others. To do this, open the bug, then select &quot;Watch it&quot; from the left hand navigation panel.<br /> To add others to the watchlist for your bug, open the bug, select the option &quot;Watching&quot; from the left hand navigation panel. These people will receive email notification when updates are made to this bug.<br /> <br /> == Developer comments ==<br /> <br /> &quot;What’s the hardest thing about a bug report?&quot; Most of the time fixing the problem is the easy part, the hard part is reproducing the bug. The developer needs to see how it is broke to be able to fix it. If they can't reproduce the error you can be sure they won't be able to fix it!<br /> <br /> Good bug reports contain as much detail as possible and are specific. Don't generalise or leap to conclusions.<br /> <br /> For example, a bug report that only says &quot;The RSS feed doesn’t support UTF-8&quot; is not helpful. The developer knows that UTF-8 and RSS feeds are compatible. The developer has no idea of what the person sees and why they reported this bug. In this case more time and effort needs to be expended to determine the problem.<br /> <br /> Consider a bug report which says that the descriptions for the specific RSS feed XYZ@abc shows unrecognisable characters rather than expected characters.<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=43952 How to manipulate Moodle developers] forum discussion<br /> *Wikipedia [http://en.wikipedia.org/wiki/Software_bug Definition of a bug]<br /> *[[Tracker development]]<br /> *[[Getting Started with the Tracker]]<br /> [[Category:Teacher]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]<br /> [[Category:Developer tools]]<br /> <br /> [[es:Sistema de bugs]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=You_Might_Be_a_Moodler&diff=15244 2006-09-02T18:29:47Z

<p>Hatshepsut: </p> <hr /> <div>In the spirit of Jeff Foxworthy's ''You Might be a Redneck'' - http://www.jefffoxworthy.com/comedy/jod/index.shtml <br /> <br /> *If you have ever turned on a football game and and the orange uniforms of one team caused you to leap up from the sofa and check out moodle.org, you might be a Moodler.<br /> <br /> *If you type &quot;moodle.org&quot; in your browser when you intend to type &quot;google.com.&quot;</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=You_Might_Be_a_Moodler&diff=15243 2006-09-02T18:29:22Z

<p>Hatshepsut: </p> <hr /> <div>In the spirit of Jeff Foxworthy's ''You Might be a Reneck'' - http://www.jefffoxworthy.com/comedy/jod/index.shtml <br /> <br /> *If you have ever turned on a football game and and the orange uniforms of one team caused you to leap up from the sofa and check out moodle.org, you might be a Moodler.<br /> <br /> *If you type &quot;moodle.org&quot; in your browser when you intend to type &quot;google.com.&quot;</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=You_Might_Be_a_Moodler&diff=15242 2006-09-02T18:28:49Z

<p>Hatshepsut: </p> <hr /> <div>In the spirit of Jeff Foxworthy's ''You Might be a Reneck'' - http://www.jefffoxworthy.com/comedy/jod/index.shtml <br /> <br /> *If you have ever turned on a football game and and the orange uniforms of one team caused you to leap up from the sofa and check out moodle.org, you might be a Moodler.<br /> <br /> *If you type moodle.org in your browser when you intend to type google.com.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=14420 2006-08-14T12:15:08Z

<p>Hatshepsut: /* Enrolment-level Capabilities */</p> <hr /> <div>'''Roles and permissions''' will be in Moodle 1.7 and are available in the developer version of Moodle.<br /> <br /> <br /> ==Definitions==<br /> <br /> A role is an identifier of the user's status in some context, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a description of some particular Moodle feature. Capabilities are associated with roles. For example, ''mod/forum:replypost'' is a capability.<br /> <br /> A permission is some value that is assigned for a capability for a particular role. For example, allow or prevent.<br /> <br /> A context is a &quot;space&quot; in the Moodle, such as courses, activity modules, blocks etc.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> <br /> {{Moodle 1.7}}The new system will allow authorized users to define an arbitrary number of roles (eg a teacher) <br /> <br /> A role consists of a list of permissions for different possible actions within Moodle (eg delete discussions, add activities etc)<br /> <br /> Roles can be applied to users in a context (eg assign Fred as a teacher in a particular course)<br /> <br /> Here are the possible contexts, listed from the most general to the most specific. <br /> <br /> #CONTEXT_SYSTEM<br /> #CONTEXT_PERSONAL<br /> #CONTEXT_USERID<br /> #CONTEXT_COURSECAT<br /> #CONTEXT_COURSE<br /> #CONTEXT_GROUP<br /> #CONTEXT_MODULE<br /> #CONTEXT_BLOCK<br /> <br /> An authorized user will be able to assign an arbitrary number of roles to each user in any context.<br /> <br /> Capabilities can have the following permissions:<br /> <br /> #CAP_INHERIT<br /> #CAP_ALLOW<br /> #CAP_PREVENT<br /> #CAP_PROHIBIT<br /> <br /> If no permission is defined, then the capability permission is inherited from a context that is more general than the current context. If we define different permission values for the same capability in different contexts, we say that we are overriding the capability in the more specific context.<br /> <br /> Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by enforcing the rule that the capability defined for a more specific context will win, unless a prohibit is encountered in a less specific context.<br /> <br /> For example, Mark has a student role at course level, which allows him to write into a wiki. But Mark also got assigned a Visitor role at a module context level (for a particular wiki) which prevents him from writing to the wiki (read only). Therefore, for this particular wiki, Mark will not be able to write to the wiki since the more specific context wins.<br /> <br /> If we set a prohibit on a capability, it means that the capability cannot be overridden and will always have a permission of prevent (deny). Prohibit always wins. For example, Jeff has a naughty student role that prohibits him from postings in any forums (for the whole site), but he's also assigned a facilitator role in &quot;Science forum&quot; in the course Science and Math 101. Since prohibit always wins, Jeff is unable to post in &quot;Science forum&quot;.<br /> <br /> Allow and prevent will cancel each other out if set for the same capability at the same context level. If this happens, we refer to the previous context level to determine the permission for the capability.<br /> <br /> This may sound more complex than it really is in practice. The upshot is that the system can be flexible enough to allow any combination of permissions.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the existing capabilities will be automatically retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, mirroring what we have in 1.6. With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> <br /> ==Capabilities==<br /> <br /> This will be a comprehensive list of capabilities (it's not complete yet). It is important that capability names are unique.<br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capability names start with 'moodle/'. The next word indicates what type of core capability it is, and the last word is the actual capability itself. The capabilities for the Moodle core are defined in lib/db/access.php<br /> <br /> <br /> #moodle/legacy:guest - legacy capabilities are used to transition existing users to the new roles system during the upgrade to Moodle 1.7<br /> #moodle/legacy:student<br /> #moodle/legacy:teacher<br /> #moodle/legacy:editingteacher<br /> #moodle/legacy:coursecreator<br /> #moodle/legacy:admin<br /> #moodle/site:doanything - special capability, meant for admins, if is set, overrides all other capability settings<br /> #moodle/site:config - applicable in admin/index.php and config.php (might break down later) : 1)admin/config.php 2)admin/configure.php 3)blocks/admin/block_admin.php load_content_for_site()<br /> #moodle/site:manageblocks - adding/removing/editing blocks (site, course contexts only for now) : 1)_add_edit_controls moodleblock.class.php <br /> #moodle/site:backup - can create a course backup : 1)course/category.php 2)block_admin.php<br /> #moodle/site:restore - can restore into this context : 1)course/category.php 2)block_admin.php<br /> #moodle/site:import - can import other courses into this context : 1)block_admin.php<br /> #moodle/site:accessallgroups - able to access all groups irrespective of what group the user is in<br /> #moodle/blog:view - read blogs<br /> #moodle/blog:create - write new blog posts<br /> #moodle/blog:manageofficialtags - create/delete official blog tags that others can use<br /> #moodle/blog:managepersonaltags - create/delete official blog tags that others can use<br /> #moodle/blog:manageentries - edit/delete all blog entries<br /> #moodle/course:create - create courses : 1)course/edit.php 2)course/category.php 3)course/index.php<br /> #moodle/course:delete - create courses : 1)course/category.php<br /> #moodle/course:update - update course settings<br /> #moodle/course:view - can use this to find participants<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:viewscales - view scales (i.e. in a help window?) : 1)course/scales.php<br /> #moodle/course:manageactivities - adding/removing/editing activities and resources (don't think it makes any sense to split these)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down : 1)blocks/block_admin.php 2)course/scales.php<br /> #moodle/course:managegroups - managing groups, add, edit, delete : 1)course/groups.php 2)course/group.php<br /> #moodle/course:visibility - hide/show courses : 1)course/category.php<br /> #moodle/course:activityvisibility - hide/show activities within a course<br /> #moodle/course:viewhiddenactivities - able to see activities that have been hidden<br /> #moodle/category:create - create category : 1)course/index.php<br /> #moodle/category:delete - delete category : 1)course/index.php<br /> #moodle/category:update - update category settings : 1)course/category.php<br /> #moodle/category:visibility - hide/show categories : 1)course/index.php<br /> #moodle/user:create - create user : 1) user/edit.php<br /> #moodle/user:delete - delete user : 1) admin/user.php<br /> #moodle/user:update - update user settings : 1) user/edit.php<br /> #moodle/user:viewdetails - view personally-identifying user details (e.g. name, photo). This ties in with the &quot;visitor&quot; scenario described below.<br /> #moodle/calendar:manageownentries - create/edit/delete <br /> #moodle/calendar:manageentries - create/edit/delete<br /> #moodle/role:assign - assign roles to users<br /> #moodle/role:manage - create/edit/delete roles, set capability permissions for each role<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The part before the colon is the full path to the module in the Moodle code. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:view- reading the assignment description<br /> ##mod/assignment:submit - turn assignment in<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entries<br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:viewhiddentimedposts<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:viewrating<br /> ##mod/forum:viewanyrating<br /> ##mod/forum:rate<br /> ##mod/forum:createattachment<br /> ##mod/forum:deleteownpost<br /> ##mod/forum:deleteanypost<br /> ##mod/forum:splitdiscussions<br /> ##mod/forum:movediscussions<br /> ##mod/forum:editanypost<br /> ##mod/forum:viewqandawithoutposting<br /> ##mod/forum:viewsubscribers<br /> ##mod/forum:managesubscriptions<br /> ##mod/forum:throttlingapplies<br /> #Glossary<br /> ##mod/glossary:view - read entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:viewrating - view ratings<br /> #Hotpot<br /> ##mod/hotpot:view<br /> #Label<br /> ##none<br /> #Lams<br /> ##TBD<br /> #Lesson<br /> ##TBD<br /> #Quiz<br /> ##TBD<br /> #Resource<br /> ##mod/resource:view<br /> #Scorm<br /> ##mod/scorm:view<br /> ##mod/scorm:viewgrades<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> ##Waiting on new wiki<br /> #Workshop<br /> ##Waiting on new Workshop<br /> <br /> ===Enrolment-level Capabilities===<br /> <br /> The naming convention for capabilities that are specific to enrolment is 'enrol/enrol_name:capability'. The enrolment capabilities are defined in enrol/enrol_name/db/access.php.<br /> <br /> #Authorize.net Payment Gateway <br /> ##enrol/authorize:managepayments - manage user payments, capture, void, refund, delete etc.<br /> <br /> Will it be possible to enroll people into different roles in a course as part of the enrollment process itself? I mean could you have an option to self-enroll (either involving payment or not) into multiple roles? In fact, will there be any possibility of a student self-selecting a role for themselves, but no one else but themselves?--[[User:N Hansen|N Hansen]] 02:00, 14 August 2006 (WST)<br /> <br /> ===Blocks===<br /> <br /> ===Questions===<br /> I am adding question categories here because they seem to have been forgotten in the whole scheme of things since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in [http://www.moodle.org/bugs/bug.php?op=show&amp;bugid=6118&amp;pos= bug 6118].<br /> <br /> See [http://moodle.org/mod/forum/discuss.php?d=51143 this forum thread] for a discussion about the current problems wth publishing question categories.[[User:Tim Hunt|Tim Hunt]] 18:50, 8 August 2006 (WST)<br /> <br /> <br /> ==Programming Interface==<br /> <br /> Although the Roles system may look complicated at first glance, implementing it in Moodle code is fairly simple.<br /> <br /> * You need to define each capability once, so that Moodle can upgrade existing roles to take advantage of it. You do this in an access.php inside the db folder of any module (eg see mod/forum/db/access.php). The array contains entries like this (note the descriptions for the legacy roles which provides forward compatibility):<br /> 'mod/forum:viewforum' =&gt; array(<br /> 'captype' =&gt; 'read',<br /> 'contextlevel' =&gt; CONTEXT_MODULE,<br /> 'legacy' =&gt; array(<br /> 'guest' =&gt; CAP_PREVENT,<br /> 'student' =&gt; CAP_ALLOW,<br /> 'teacher' =&gt; CAP_ALLOW,<br /> 'editingteacher' =&gt; CAP_ALLOW,<br /> 'coursecreator' =&gt; CAP_ALLOW,<br /> 'admin' =&gt; CAP_ALLOW<br /> )<br /> ),<br /> * To load/change these capabilities you need to bump the module version. There's no need to provide changes or differences as Moodle will scan the whole array and sort it out.<br /> * On each page you need to find the context the user is working in, using the get_context_instance() function. For example, in the forum module:<br /> <br /> $context = get_context_instance(CONTEXT_MODULE, $cm-&gt;id);<br /> * Then, whenever you want to check that the current user has rights to do something, call has_capability() like this:<br /> if (!has_capability('mod/forum:viewforum', $context)) {<br /> print_error('nopermissiontoviewforum');<br /> }<br /> * If you just want to assert a capability and then finish with an error message if it's not met (as we did above), then a shorter way it to use require_capability() like this:<br /> <br /> require_capability('mod/forum:viewforum', $context);<br /> <br /> * Note that there are extra parameters you can specify to get a custom error message, otherwise users get an automated &quot;No permissions&quot; message that lists the permission they were missing.<br /> <br /> <br /> As a result of the new Roles System, all calls to isadmin(), iscoursecreator, isteacheredit(), isteacher(), isstudent(), and isguest() will have to be replaced with calls to has_capability() or require_capability(). However, these functions will be retained for some backward compatibility with old code, using the legacy capabilities to try and work out what to do.<br /> <br /> ==Scenario brainstorming==<br /> <br /> This section is for brainstorming some example roles that we would like to support. Note some of these *may* not be possible in 1.7.<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===Peer observer of teaching===<br /> Many institutions encourage peer observation of teaching, to encourage reflection on practice. In online environments this will be similar to moderation or inspection. The peer observer would need to be able to experience the course &quot;as a student&quot;, but also to be able to view summaries of usage, transcripts of interactions (forums/surveys/polls etc), grades assigned (e.g. in assignments).<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY=3+4 yr olds) and Key Stage 1 (KS1=5+6 yr olds) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary. In Key Stage 2 (KS2=7-11 yr olds) parents would be more monitoring but may join in as well.<br /> <br /> In Key stages 3 (KS3=12-14 yr olds) and 4 (KS4=15+16 yr olds) this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments. Also in all Key Satges there may be a home-school agreement which may be signed up to. Could this form part of a site policy system that incorporates a tickable list of activities the parent agrees to the child using (blogs/wikis/forums etc.)?<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> Again in the UK, parents have their own independent right of access to a child's educational records. Obviously, children's records must not be made available to other parties, including the parents of other children in the same class. Thus it would be necessary to associate parent accounts with their own child's accounts in such a way that they could, if so desired, have read access to their child's grades, answers and contributions, but generally not those of other children - this may be problematic in the case of wiki activities or forum posts.<br /> <br /> There is some concern that children's forum contributions etc may be constrained if their parents are able to read all that they write; this may be particularly problematic in areas such as Personal, Social and Health Education (PSHE), where some schools may choose to use obfuscated usernames.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===Alumnus=== An ALUMNUS should be able to search for all other ALUMNI of the school, interact with them and be enrolled in a seperate course - which is like a META course with all the content of his learning and interaction - as well as capabilities to be a part of this ALUMNI only course. All the teachers of courses during school years should automatically be a part of the ALUMNI course .. which means when an ALUMNUS is enrolled in a course, the original teachers of all his courses get enrolled ? --[[User:Anil Sharma|Anil Sharma]] 20:54, 15 July 2006 (WST)<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> In schools there is often a book review system. This may be covered by the lending system database but may not in which case a librarian may neeed to have a course area they can create a database template to handle the reviews in which case they may have a normal teacher style role? Off topic but course an integration with common schools database systems would be great.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Student - FERPA rights===<br /> <br /> A student that has asserted their FERPA rights to non-disclosure. Typically includes not publishing their name<br /> in any public place. Could include this student only being seen with an &quot;alias&quot; within course spaces. Is this an attribute rather<br /> than a role?<br /> <br /> ===Help Desk===<br /> <br /> Help desk agents that have read access for the purposes of trouble shooting. Some care in placing this role within a hierarchy<br /> of inheritance is needed, full access will be problematic with FERPA.<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> [[Category:Roles]]<br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Wikindx&diff=14359 2006-08-13T18:05:36Z

<p>Hatshepsut: </p> <hr /> <div>'''Notes on the possible integration of [http://wikindx.sourceforge.net/index2.html WIKINDX] with Moodle.'''<br /> <br /> [http://wikindx.sourceforge.net/index2.html WIKINDX]is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.<br /> <br /> Please also see the Moodle Discussion at http://moodle.org/mod/forum/discuss.php?d=23022<br /> <br /> ==Wikindx filter for Moodle==<br /> <br /> Dan Stowell has created a &quot;Wikindx filter&quot; for Moodle which allows you to cross-link to a wikindx entry by typing (for example) wikindx:646. The filter is in contrib CVS, named &quot;filter_wikindx&quot; or can be downloaded at http://download.moodle.org/download.php/modules/filter_wikindx.zip<br /> <br /> From MG:<br /> Some design considerations for a moodle filter that enables a wikindx to be searched, a reference to be selected, page number(s) to be added and the in-text or footnote citation and full reference to be returned formatted to the user's requirements.<br /> <br /> NB With everything else I have going on (PhD, Wikindx, life) I have no intention of setting up Moodle for testing this (no prior experience in Moodle let alone moodle filters) but, if someone is willing to a) write the moodle filter code and b) be prepared to run beta wikindx code to test the interface, then I would be more than happy to do whatever needs to be done in the wikindx code. The wikindx code will be easy: I can't speak for the moodle code (but, see below, imagine that quite a bit of it could be pulled from wikindx). I also have no idea if moodle filters alone can accomplish what I've suggested below or if the code needs greater integration in the moodle core code.<br /> <br /> 1/ The Moodle filter needs to provide 3 basic functions:<br /> :a) an icon in the HTML text editor that opens a pop-up,<br /> :b) the pop up should provide a simple search/select interface to wikindx resources,<br /> :c) once the selected wikindx resource has been inserted into the text, the moodle HTML editor text is saved and the filter sends the reference (and style and page number(s)) to wikindx for formatting and insertion into the moodle text.<br /> <br /> 2/ Because what is supplied to the pop-up (see below) requires a connection to wikindx, the filter should have a config file for the wikindx database connection details. wikindx 3.4 now allows admins to lock out read-only users so this config file may also have the option to add a wikindx username::password pair (I would not favour this though).<br /> <br /> 3/ The search interface could be similar to the wikindx Quick Search interface less the ordering options (to save on space). [WIKINDX code (filling the pop-up)]<br /> <br /> 4/ The results of a search should be displayed with multiple resources next to radio buttons, a select box to choose the formatting style and text boxes to enter page number(s). Each radio button has a value that is the unique resource ID in the wikindx. [WIKINDX code]<br /> <br /> 5/ Once the appropriate resource has been selected and other details added, clicking on a 'process' button will add the appropriate filter mark-up which may be something like:<br /> :wikindx:34:12[APA]<br /> :wikindx:56:34-35[CHICAGO]<br /> <br /> where the first number is the wikindx resource ID, the second number(s) is the page and [...] is the bibliographic style chosen. [WIKINDX code]<br /> <br /> 6/ On saving the moodle text, that markup is extracted and sent to the wikindx server (something like http://....index.php&amp;externalResourceGrab&amp;id=56&amp;pages=34-35&amp;style=CHICAGO) which then formats the requested resource and provides a string in return which would consist of a serialized/base64_encoded PHP multi-dimensional array which, when unpacked, would have something like the following (if APA for example):<br /> :array(<br /> ::[styleType] = array(<br /> :::[0] =&gt; &quot;inText&quot;<br /> ::),<br /> ::[citation] = array(<br /> :::[0] =&gt; &quot;(Martin et al. 1978, pp.34--35)&quot;<br /> ::),<br /> ::[reference] = array(<br /> :::[0] =&gt; &quot;Martin, R. L., Thrift, N. J., &amp; Bennett, R. J. (Eds.). (1978). ''Towards the dynamic analysis of spatial systems''. London: Pion.&quot;<br /> ::)<br /> :);<br /> <br /> for a footnote-type citation (e.g. Chicago), it might be:<br /> :array(<br /> ::[styleType] = array(<br /> :::[0] =&gt; &quot;footnote&quot;<br /> ::),<br /> ::[citation] = array(<br /> :::[0] =&gt; &quot;''Towards the Dynamic Analysis of Spatial Systems''. 1978. Edited by R. L. Martin, N. J. Thrift and R. J. Bennett. London: Pion. pp.34--35&quot;<br /> ::),<br /> ::[reference] = array(<br /> :::[0] =&gt; &quot;''Towards the Dynamic Analysis of Spatial Systems''. 1978. Edited by R. L. Martin, N. J. Thrift and R. J. Bennett. London: Pion.&quot;<br /> ::)<br /> :);<br /> <br /> NB The italics (and any underline, bold etc.) would be returned as HTML markup. [WIKINDX code]<br /> <br /> 7/ Moodle would take this array and, if [styleType] == 'footnote', insert something like '[1]' in the body of the text, [citation] as a footnote and, if required, append [reference] to a bibliography (perhaps this is just future-proofing in this case). However, if [styleType] == 'inText', [citation] would be inserted in the body of the text and [reference] appended.<br /> <br /> 8/ In the case of multiple citations, wikindx should be able to provide the second element of the array correctly ordered as per the style requirements. So you might have something like:<br /> <br /> :array(<br /> ::[styleType] = array(<br /> :::[0] =&gt; &quot;inText&quot;<br /> ::),<br /> ::[citation] = array(<br /> :::[0] =&gt; &quot;(Martin et al. 1978, pp.34--35)&quot;,<br /> :::[1] =&gt; &quot;(Aarseth et al. 2003)&quot;<br /> ::),<br /> ::[reference] = array(<br /> :::[0] =&gt; &quot;Aarseth, E., Smedstad, S. M., &amp; Sunnanå, L. (2003, November 4—6). ''A multi-dimensional typology of games''. Paper presented at Level Up, Utrecht Universiteit.&quot;,<br /> :::[1] =&gt; &quot;Martin, R. L., Thrift, N. J., &amp; Bennett, R. J. (Eds.). (1978). ''Towards the dynamic analysis of spatial systems''. London: Pion.&quot;<br /> ::)<br /> :);<br /> <br /> In this way separate orders are maintained for the citation and the appended bibliography. [WIKINDX code]<br /> <br /> Perhaps the above is not do-able as a simple moodle filter?<br /> <br /> ==Outline thoughts on integration...==<br /> <br /> 1. Do we need to allowing a user already logged into a Moodle site to be seamlessly logged in to a wikindx? Or maybe just use the same login details between the two (like the way that Moodle.org and MoodleDocs works). If necessary, something could be added to wikindx to enable this. In most cases though, with the right config settings, wikindx will allow any read only request without requiring login.<br /> <br /> 2. Another issue is how to integrate the paper writing function of Wikindx into Moodle. What about use of the HTML editor? Could it be integrated some way with the Netpublish module? Imagine students or professors being able to use it to write academic papers and then publish those on the Moodle site. Currently wikindx publishes papers solely to RTF. It should be simple to publish to HTML since that's what the raw document is anyway (a matter of adding HTML header/footer, formatting citations and appending bibliographies -- most of this code is already in wikindx but not (yet) made available to the word processor). Compared to other HTML editors, the only additional options wikindx offers in its version are buttons to import citations, metadata and insert footnotes. All the rest (barring stats, timestamps, save etc.) are font/text formatting.<br /> <br /> 3. For the filter above, how do you decide what bibliographic style to present in (APA, Chicago, IEEE etc.)? Presumably, this is something that could be set in the filter config file. (Although I haven't seen the filter in operation, I'm assuming it picks up a properly formatted reference for insert. Either short (Grimshaw, 2006) or long (Grimshaw, Mark N. 2006, WIKINDX [OSS].) for example. Is the only method of citation available parenthetical? Is it possible to use endnotes (or footnotes) as well? Yes, endnote/footnote styles are available as well.<br /> <br /> :''Note from DS: No, at present the Wikindx filter simply displays the text &quot;wikindx:646&quot; (for example). It's a very simple start and I hope that people with more knowledge of Wikindx will be able to modify it to extract the properly-formatted reference direct from Wikindx. If wikindx had a system whereby a certain URL call would supply the reference text in whatever style was configured for wikindx, this would be a good way to display the citation nicely within Moodle. Does such a call exist? I don't think so. Something like mywikindx.com/index.php?'''action=resourceGrabCitation'''&amp;id=501 would be required.''<br /> <br /> :''Note from JB: As the wikindx admin can set the default bibliographic style in the config, the filter will just present that style. The filter is simple but oh so useful! So when I type '''wikindx:1''' into my moodle installation, it creates an automatic link to http://www.baillie.org.uk/wikindx//index.php?action=resourceView&amp;id=1<br /> <br /> :''Note from MG: action=resourceGrabCitation can be added and the default citation formatting applied. A possible gotcha in that there may be a problem with footnote/endnote style citation is that not only would you need the footnote marker (e.g. [1]) but you would also need the full reference to be appended to the text as a footnote (I'm assuming this is required rather than just using [1] as a hyperlink to the wikindx resource -- presumably you would want to use the same strict referencing that students are required to use). Hence, in this case, the returned values would consist of two values -- one the citation to be hyperlinked and the other the full reference to be appended.'' <br /> <br /> :''Note from MG: In wikindx, inserting a citation into metadata or the word processor involves clicking on an icon which opens a popup. In this, there is a select box listing short entries of all available resources and some text fields for users to enter cited page numbers. Perhaps something similar could be used in the moodle wikindx filter to avoid the hassle of having to look up the wikindx resource id before entering it into moodle. This pop-up could also list the available citation/bibliographic styles on the wikindx allowing the user to select the style with which the citation should be formatted prior to insertion into moodle.''<br /> <br /> 4. Mark, your remarks in 2 have gotten me thinking. Although not everyone likes the Moodle HTML area editor that much, it still is the standard way of creating text in Moodle and perhaps a way of integrating Wikindx would be to add buttons for Wikindx to it, just like the kind described above in Wikindx's native editor. I needed to integrate a hieroglyph editor into my site and Janne Mikkonen helped me to add it through a button in the html editor that pops up a window, in which the student type the hieroglyphs they need, and then click a button to have them inserted back into the editor-similar to the way the insert image popup works. I would imagine something similar could be done with Wikindx. The advantage of this is that it would make Wikindx accessible anywhere within Moodle, rather than just as a separate module. You might also want a standalone module option whereby students could collaborate on creating bibliographies together.<br /> <br /> :''Note from MG: Adding the appropriate buttons would be my suggestion. In wikindx, citations are added by the popup automatically adding something like''<br /> :''[cite]146:22-23[/cite]''<br /> :''where 146 is the resource ID in the database and 22-23 are the page nos. This can be added via a cite button or will be appended to an inserted quotation/paraphrase via the wikindx 'insert metadata' button. Footnotes (i.e. parenthetical thoughts as opposed to citation footnotes - WIKINDX does handle those footnotes/endnotes as well) are inserted via a button which encloses the inserted footnote in:''<br /> :''[footnote]....[/footnote]''<br /> <br /> :''Exporting to RTF, the cite tags are substituted with the formatted citation marker (in-text or footnote/endnote), bibliographic information is extracted and appended to a bibliography and footnote tags are converted to RTF footnotes. Of course, all HTML code (font/text formatting, tables, lists, images etc.) are converted to their appropriate RTF code too.''<br /> <br /> 5. Re the citation/bibliographic formatting, the PHP code for this has been extracted from wikindx and made available to other OSS apps at http://bibliophile.sourceforge.net (I think Aigaion and Bibliograph use it or are about to) so it may be easy enough for Moodle to use this too. In fact doubly easy if moodle interfaces with a wikindx because the quickest way to set up the formatting engine is to provide data to it in exactly the same PHP associative array that wikindx natively expects.<br /> <br /> 6. What capabilities are there in Wikindx at this time for different capabilities in using bibliographies? Can bibliographies be shared by a predefined group/all users? Can some people be given the ability to add to a bibliography while others can only use the bibilography? Can bibliography entries be required to have approval by some person before they are displayed to all? These would be nice features to have.<br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=14358 2006-08-13T18:00:51Z

<p>Hatshepsut: /* Enrolment-level Capabilities */</p> <hr /> <div>'''Roles and permissions''' will be in Moodle 1.7 and are available in the developer version of Moodle.<br /> <br /> <br /> ==Definitions==<br /> <br /> A role is an identifier of the user's status in some context, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a description of some particular Moodle feature. Capabilities are associated with roles. For example, ''mod/forum:replypost'' is a capability.<br /> <br /> A permission is some value that is assigned for a capability for a particular role. For example, allow or prevent.<br /> <br /> A context is a &quot;space&quot; in the Moodle, such as courses, activity modules, blocks etc.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> <br /> {{Moodle 1.7}}The new system will allow authorized users to define an arbitrary number of roles (eg a teacher) <br /> <br /> A role consists of a list of permissions for different possible actions within Moodle (eg delete discussions, add activities etc)<br /> <br /> Roles can be applied to users in a context (eg assign Fred as a teacher in a particular course)<br /> <br /> Here are the possible contexts, listed from the most general to the most specific. <br /> <br /> #CONTEXT_SYSTEM<br /> #CONTEXT_PERSONAL<br /> #CONTEXT_USERID<br /> #CONTEXT_COURSECAT<br /> #CONTEXT_COURSE<br /> #CONTEXT_GROUP<br /> #CONTEXT_MODULE<br /> #CONTEXT_BLOCK<br /> <br /> An authorized user will be able to assign an arbitrary number of roles to each user in any context.<br /> <br /> Capabilities can have the following permissions:<br /> <br /> #CAP_INHERIT<br /> #CAP_ALLOW<br /> #CAP_PREVENT<br /> #CAP_PROHIBIT<br /> <br /> If no permission is defined, then the capability permission is inherited from a context that is more general than the current context. If we define different permission values for the same capability in different contexts, we say that we are overriding the capability in the more specific context.<br /> <br /> Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by enforcing the rule that the capability defined for a more specific context will win, unless a prohibit is encountered in a less specific context.<br /> <br /> For example, Mark has a student role at course level, which allows him to write into a wiki. But Mark also got assigned a Visitor role at a module context level (for a particular wiki) which prevents him from writing to the wiki (read only). Therefore, for this particular wiki, Mark will not be able to write to the wiki since the more specific context wins.<br /> <br /> If we set a prohibit on a capability, it means that the capability cannot be overridden and will always have a permission of prevent (deny). Prohibit always wins. For example, Jeff has a naughty student role that prohibits him from postings in any forums (for the whole site), but he's also assigned a facilitator role in &quot;Science forum&quot; in the course Science and Math 101. Since prohibit always wins, Jeff is unable to post in &quot;Science forum&quot;.<br /> <br /> Allow and prevent will cancel each other out if set for the same capability at the same context level. If this happens, we refer to the previous context level to determine the permission for the capability.<br /> <br /> This may sound more complex than it really is in practice. The upshot is that the system can be flexible enough to allow any combination of permissions.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the existing capabilities will be automatically retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, mirroring what we have in 1.6. With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> <br /> ==Capabilities==<br /> <br /> This will be a comprehensive list of capabilities (it's not complete yet). It is important that capability names are unique.<br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capability names start with 'moodle/'. The next word indicates what type of core capability it is, and the last word is the actual capability itself. The capabilities for the Moodle core are defined in lib/db/access.php<br /> <br /> <br /> #moodle/legacy:guest - legacy capabilities are used to transition existing users to the new roles system during the upgrade to Moodle 1.7<br /> #moodle/legacy:student<br /> #moodle/legacy:teacher<br /> #moodle/legacy:editingteacher<br /> #moodle/legacy:coursecreator<br /> #moodle/legacy:admin<br /> #moodle/site:doanything - special capability, meant for admins, if is set, overrides all other capability settings<br /> #moodle/site:config - applicable in admin/index.php and config.php (might break down later) : 1)admin/config.php 2)admin/configure.php 3)blocks/admin/block_admin.php load_content_for_site()<br /> #moodle/site:manageblocks - adding/removing/editing blocks (site, course contexts only for now) : 1)_add_edit_controls moodleblock.class.php <br /> #moodle/site:backup - can create a course backup : 1)course/category.php 2)block_admin.php<br /> #moodle/site:restore - can restore into this context : 1)course/category.php 2)block_admin.php<br /> #moodle/site:import - can import other courses into this context : 1)block_admin.php<br /> #moodle/site:accessallgroups - able to access all groups irrespective of what group the user is in<br /> #moodle/blog:view - read blogs<br /> #moodle/blog:create - write new blog posts<br /> #moodle/blog:manageofficialtags - create/delete official blog tags that others can use<br /> #moodle/blog:managepersonaltags - create/delete official blog tags that others can use<br /> #moodle/blog:manageentries - edit/delete all blog entries<br /> #moodle/course:create - create courses : 1)course/edit.php 2)course/category.php 3)course/index.php<br /> #moodle/course:delete - create courses : 1)course/category.php<br /> #moodle/course:update - update course settings<br /> #moodle/course:view - can use this to find participants<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:viewscales - view scales (i.e. in a help window?) : 1)course/scales.php<br /> #moodle/course:manageactivities - adding/removing/editing activities and resources (don't think it makes any sense to split these)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down : 1)blocks/block_admin.php 2)course/scales.php<br /> #moodle/course:managegroups - managing groups, add, edit, delete : 1)course/groups.php 2)course/group.php<br /> #moodle/course:visibility - hide/show courses : 1)course/category.php<br /> #moodle/course:activityvisibility - hide/show activities within a course<br /> #moodle/course:viewhiddenactivities - able to see activities that have been hidden<br /> #moodle/category:create - create category : 1)course/index.php<br /> #moodle/category:delete - delete category : 1)course/index.php<br /> #moodle/category:update - update category settings : 1)course/category.php<br /> #moodle/category:visibility - hide/show categories : 1)course/index.php<br /> #moodle/user:create - create user : 1) user/edit.php<br /> #moodle/user:delete - delete user : 1) admin/user.php<br /> #moodle/user:update - update user settings : 1) user/edit.php<br /> #moodle/user:viewdetails - view personally-identifying user details (e.g. name, photo). This ties in with the &quot;visitor&quot; scenario described below.<br /> #moodle/calendar:manageownentries - create/edit/delete <br /> #moodle/calendar:manageentries - create/edit/delete<br /> #moodle/role:assign - assign roles to users<br /> #moodle/role:manage - create/edit/delete roles, set capability permissions for each role<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The part before the colon is the full path to the module in the Moodle code. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:view- reading the assignment description<br /> ##mod/assignment:submit - turn assignment in<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entries<br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:viewhiddentimedposts<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:viewrating<br /> ##mod/forum:viewanyrating<br /> ##mod/forum:rate<br /> ##mod/forum:createattachment<br /> ##mod/forum:deleteownpost<br /> ##mod/forum:deleteanypost<br /> ##mod/forum:splitdiscussions<br /> ##mod/forum:movediscussions<br /> ##mod/forum:editanypost<br /> ##mod/forum:viewqandawithoutposting<br /> ##mod/forum:viewsubscribers<br /> ##mod/forum:managesubscriptions<br /> ##mod/forum:throttlingapplies<br /> #Glossary<br /> ##mod/glossary:view - read entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:viewrating - view ratings<br /> #Hotpot<br /> ##mod/hotpot:view<br /> #Label<br /> ##none<br /> #Lams<br /> ##TBD<br /> #Lesson<br /> ##TBD<br /> #Quiz<br /> ##TBD<br /> #Resource<br /> ##mod/resource:view<br /> #Scorm<br /> ##mod/scorm:view<br /> ##mod/scorm:viewgrades<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> ##Waiting on new wiki<br /> #Workshop<br /> ##Waiting on new Workshop<br /> <br /> ===Enrolment-level Capabilities===<br /> <br /> The naming convention for capabilities that are specific to enrolment is 'enrol/enrol_name:capability'. The enrolment capabilities are defined in enrol/enrol_name/db/access.php.<br /> <br /> #Authorize.net Payment Gateway <br /> ##enrol/authorize:managepayments - manage user payments, capture, void, refund, delete etc.<br /> <br /> Will it be possible to enroll people into different roles in a course as part of the enrollment process itself? I mean could you have an option to self-enroll (either involving payment or not) into multiple roles?--[[User:N Hansen|N Hansen]] 02:00, 14 August 2006 (WST)<br /> <br /> ===Blocks===<br /> <br /> ===Questions===<br /> I am adding question categories here because they seem to have been forgotten in the whole scheme of things since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in [http://www.moodle.org/bugs/bug.php?op=show&amp;bugid=6118&amp;pos= bug 6118].<br /> <br /> See [http://moodle.org/mod/forum/discuss.php?d=51143 this forum thread] for a discussion about the current problems wth publishing question categories.[[User:Tim Hunt|Tim Hunt]] 18:50, 8 August 2006 (WST)<br /> <br /> <br /> ==Programming Interface==<br /> <br /> Although the Roles system may look complicated at first glance, implementing it in Moodle code is fairly simple.<br /> <br /> # You need to define each capability once, so that Moodle can upgrade existing roles to take advantage of it. You do this in an access.php inside the db folder of any module (eg see mod/forum/db/access.php). The array contains entries like this (note the descriptions for the legacy roles which provides forward compatibility):<br /> <br /> 'mod/forum:viewforum' =&gt; array(<br /> 'captype' =&gt; 'read',<br /> 'contextlevel' =&gt; CONTEXT_MODULE,<br /> 'legacy' =&gt; array(<br /> 'guest' =&gt; CAP_PREVENT,<br /> 'student' =&gt; CAP_ALLOW,<br /> 'teacher' =&gt; CAP_ALLOW,<br /> 'editingteacher' =&gt; CAP_ALLOW,<br /> 'coursecreator' =&gt; CAP_ALLOW,<br /> 'admin' =&gt; CAP_ALLOW<br /> )<br /> ),<br /> <br /> # To load/change these capabilities you need to bump the module version. There's no need to provide changes or differences as Moodle will scan the whole array and sort it out.<br /> # On each page you need to define the context the user is working in. For example, in the forum module:<br /> <br /> $context = get_context_instance(CONTEXT_MODULE, $cm-&gt;id);<br /> <br /> # Then, whenever you want to check that the current user has rights to do something, call has_capability() like this:<br /> <br /> if (!has_capability('mod/forum:viewforum', $context-&gt;id)) {<br /> print_error('nopermissiontoviewforum);<br /> }<br /> <br /> <br /> <br /> ==Scenario brainstorming==<br /> <br /> This section is for brainstorming some example roles that we would like to support. Note some of these *may* not be possible in 1.7.<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===Peer observer of teaching===<br /> Many institutions encourage peer observation of teaching, to encourage reflection on practice. In online environments this will be similar to moderation or inspection. The peer observer would need to be able to experience the course &quot;as a student&quot;, but also to be able to view summaries of usage, transcripts of interactions (forums/surveys/polls etc), grades assigned (e.g. in assignments).<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY=3+4 yr olds) and Key Stage 1 (KS1=5+6 yr olds) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary. In Key Stage 2 (KS2=7-11 yr olds) parents would be more monitoring but may join in as well.<br /> <br /> In Key stages 3 (KS3=12-14 yr olds) and 4 (KS4=15+16 yr olds) this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments. Also in all Key Satges there may be a home-school agreement which may be signed up to. Could this form part of a site policy system that incorporates a tickable list of activities the parent agrees to the child using (blogs/wikis/forums etc.)?<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> Again in the UK, parents have their own independent right of access to a child's educational records. Obviously, children's records must not be made available to other parties, including the parents of other children in the same class. Thus it would be necessary to associate parent accounts with their own child's accounts in such a way that they could, if so desired, have read access to their child's grades, answers and contributions, but generally not those of other children - this may be problematic in the case of wiki activities or forum posts.<br /> <br /> There is some concern that children's forum contributions etc may be constrained if their parents are able to read all that they write; this may be particularly problematic in areas such as Personal, Social and Health Education (PSHE), where some schools may choose to use obfuscated usernames.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===Alumnus=== An ALUMNUS should be able to search for all other ALUMNI of the school, interact with them and be enrolled in a seperate course - which is like a META course with all the content of his learning and interaction - as well as capabilities to be a part of this ALUMNI only course. All the teachers of courses during school years should automatically be a part of the ALUMNI course .. which means when an ALUMNUS is enrolled in a course, the original teachers of all his courses get enrolled ? --[[User:Anil Sharma|Anil Sharma]] 20:54, 15 July 2006 (WST)<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> In schools there is often a book review system. This may be covered by the lending system database but may not in which case a librarian may neeed to have a course area they can create a database template to handle the reviews in which case they may have a normal teacher style role? Off topic but course an integration with common schools database systems would be great.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Student - FERPA rights===<br /> <br /> A student that has asserted their FERPA rights to non-disclosure. Typically includes not publishing their name<br /> in any public place. Could include this student only being seen with an &quot;alias&quot; within course spaces. Is this an attribute rather<br /> than a role?<br /> <br /> ===Help Desk===<br /> <br /> Help desk agents that have read access for the purposes of trouble shooting. Some care in placing this role within a hierarchy<br /> of inheritance is needed, full access will be problematic with FERPA.<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> [[Category:Roles]]<br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=14356 2006-08-13T17:57:18Z

<p>Hatshepsut: /* ALUMNUS */</p> <hr /> <div>'''Roles and permissions''' will be in Moodle 1.7 and are available in the developer version of Moodle.<br /> <br /> <br /> ==Definitions==<br /> <br /> A role is an identifier of the user's status in some context, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a description of some particular Moodle feature. Capabilities are associated with roles. For example, ''mod/forum:replypost'' is a capability.<br /> <br /> A permission is some value that is assigned for a capability for a particular role. For example, allow or prevent.<br /> <br /> A context is a &quot;space&quot; in the Moodle, such as courses, activity modules, blocks etc.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> <br /> {{Moodle 1.7}}The new system will allow authorized users to define an arbitrary number of roles (eg a teacher) <br /> <br /> A role consists of a list of permissions for different possible actions within Moodle (eg delete discussions, add activities etc)<br /> <br /> Roles can be applied to users in a context (eg assign Fred as a teacher in a particular course)<br /> <br /> Here are the possible contexts, listed from the most general to the most specific. <br /> <br /> #CONTEXT_SYSTEM<br /> #CONTEXT_PERSONAL<br /> #CONTEXT_USERID<br /> #CONTEXT_COURSECAT<br /> #CONTEXT_COURSE<br /> #CONTEXT_GROUP<br /> #CONTEXT_MODULE<br /> #CONTEXT_BLOCK<br /> <br /> An authorized user will be able to assign an arbitrary number of roles to each user in any context.<br /> <br /> Capabilities can have the following permissions:<br /> <br /> #CAP_INHERIT<br /> #CAP_ALLOW<br /> #CAP_PREVENT<br /> #CAP_PROHIBIT<br /> <br /> If no permission is defined, then the capability permission is inherited from a context that is more general than the current context. If we define different permission values for the same capability in different contexts, we say that we are overriding the capability in the more specific context.<br /> <br /> Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by enforcing the rule that the capability defined for a more specific context will win, unless a prohibit is encountered in a less specific context.<br /> <br /> For example, Mark has a student role at course level, which allows him to write into a wiki. But Mark also got assigned a Visitor role at a module context level (for a particular wiki) which prevents him from writing to the wiki (read only). Therefore, for this particular wiki, Mark will not be able to write to the wiki since the more specific context wins.<br /> <br /> If we set a prohibit on a capability, it means that the capability cannot be overridden and will always have a permission of prevent (deny). Prohibit always wins. For example, Jeff has a naughty student role that prohibits him from postings in any forums (for the whole site), but he's also assigned a facilitator role in &quot;Science forum&quot; in the course Science and Math 101. Since prohibit always wins, Jeff is unable to post in &quot;Science forum&quot;.<br /> <br /> Allow and prevent will cancel each other out if set for the same capability at the same context level. If this happens, we refer to the previous context level to determine the permission for the capability.<br /> <br /> This may sound more complex than it really is in practice. The upshot is that the system can be flexible enough to allow any combination of permissions.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the existing capabilities will be automatically retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, mirroring what we have in 1.6. With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> <br /> ==Capabilities==<br /> <br /> This will be a comprehensive list of capabilities (it's not complete yet). It is important that capability names are unique.<br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capability names start with 'moodle/'. The next word indicates what type of core capability it is, and the last word is the actual capability itself. The capabilities for the Moodle core are defined in lib/db/access.php<br /> <br /> <br /> #moodle/legacy:guest - legacy capabilities are used to transition existing users to the new roles system during the upgrade to Moodle 1.7<br /> #moodle/legacy:student<br /> #moodle/legacy:teacher<br /> #moodle/legacy:editingteacher<br /> #moodle/legacy:coursecreator<br /> #moodle/legacy:admin<br /> #moodle/site:doanything - special capability, meant for admins, if is set, overrides all other capability settings<br /> #moodle/site:config - applicable in admin/index.php and config.php (might break down later) : 1)admin/config.php 2)admin/configure.php 3)blocks/admin/block_admin.php load_content_for_site()<br /> #moodle/site:manageblocks - adding/removing/editing blocks (site, course contexts only for now) : 1)_add_edit_controls moodleblock.class.php <br /> #moodle/site:backup - can create a course backup : 1)course/category.php 2)block_admin.php<br /> #moodle/site:restore - can restore into this context : 1)course/category.php 2)block_admin.php<br /> #moodle/site:import - can import other courses into this context : 1)block_admin.php<br /> #moodle/site:accessallgroups - able to access all groups irrespective of what group the user is in<br /> #moodle/blog:view - read blogs<br /> #moodle/blog:create - write new blog posts<br /> #moodle/blog:manageofficialtags - create/delete official blog tags that others can use<br /> #moodle/blog:managepersonaltags - create/delete official blog tags that others can use<br /> #moodle/blog:manageentries - edit/delete all blog entries<br /> #moodle/course:create - create courses : 1)course/edit.php 2)course/category.php 3)course/index.php<br /> #moodle/course:delete - create courses : 1)course/category.php<br /> #moodle/course:update - update course settings<br /> #moodle/course:view - can use this to find participants<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:viewscales - view scales (i.e. in a help window?) : 1)course/scales.php<br /> #moodle/course:manageactivities - adding/removing/editing activities and resources (don't think it makes any sense to split these)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down : 1)blocks/block_admin.php 2)course/scales.php<br /> #moodle/course:managegroups - managing groups, add, edit, delete : 1)course/groups.php 2)course/group.php<br /> #moodle/course:visibility - hide/show courses : 1)course/category.php<br /> #moodle/course:activityvisibility - hide/show activities within a course<br /> #moodle/course:viewhiddenactivities - able to see activities that have been hidden<br /> #moodle/category:create - create category : 1)course/index.php<br /> #moodle/category:delete - delete category : 1)course/index.php<br /> #moodle/category:update - update category settings : 1)course/category.php<br /> #moodle/category:visibility - hide/show categories : 1)course/index.php<br /> #moodle/user:create - create user : 1) user/edit.php<br /> #moodle/user:delete - delete user : 1) admin/user.php<br /> #moodle/user:update - update user settings : 1) user/edit.php<br /> #moodle/user:viewdetails - view personally-identifying user details (e.g. name, photo). This ties in with the &quot;visitor&quot; scenario described below.<br /> #moodle/calendar:manageownentries - create/edit/delete <br /> #moodle/calendar:manageentries - create/edit/delete<br /> #moodle/role:assign - assign roles to users<br /> #moodle/role:manage - create/edit/delete roles, set capability permissions for each role<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The part before the colon is the full path to the module in the Moodle code. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:view- reading the assignment description<br /> ##mod/assignment:submit - turn assignment in<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entries<br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:viewhiddentimedposts<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:viewrating<br /> ##mod/forum:viewanyrating<br /> ##mod/forum:rate<br /> ##mod/forum:createattachment<br /> ##mod/forum:deleteownpost<br /> ##mod/forum:deleteanypost<br /> ##mod/forum:splitdiscussions<br /> ##mod/forum:movediscussions<br /> ##mod/forum:editanypost<br /> ##mod/forum:viewqandawithoutposting<br /> ##mod/forum:viewsubscribers<br /> ##mod/forum:managesubscriptions<br /> ##mod/forum:throttlingapplies<br /> #Glossary<br /> ##mod/glossary:view - read entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:viewrating - view ratings<br /> #Hotpot<br /> ##mod/hotpot:view<br /> #Label<br /> ##none<br /> #Lams<br /> ##TBD<br /> #Lesson<br /> ##TBD<br /> #Quiz<br /> ##TBD<br /> #Resource<br /> ##mod/resource:view<br /> #Scorm<br /> ##mod/scorm:view<br /> ##mod/scorm:viewgrades<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> ##Waiting on new wiki<br /> #Workshop<br /> ##Waiting on new Workshop<br /> <br /> ===Enrolment-level Capabilities===<br /> <br /> The naming convention for capabilities that are specific to enrolment is 'enrol/enrol_name:capability'. The enrolment capabilities are defined in enrol/enrol_name/db/access.php.<br /> <br /> #Authorize.net Payment Gateway <br /> ##enrol/authorize:managepayments - manage user payments, capture, void, refund, delete etc.<br /> <br /> <br /> ===Blocks===<br /> <br /> ===Questions===<br /> I am adding question categories here because they seem to have been forgotten in the whole scheme of things since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in [http://www.moodle.org/bugs/bug.php?op=show&amp;bugid=6118&amp;pos= bug 6118].<br /> <br /> See [http://moodle.org/mod/forum/discuss.php?d=51143 this forum thread] for a discussion about the current problems wth publishing question categories.[[User:Tim Hunt|Tim Hunt]] 18:50, 8 August 2006 (WST)<br /> <br /> <br /> ==Programming Interface==<br /> <br /> Although the Roles system may look complicated at first glance, implementing it in Moodle code is fairly simple.<br /> <br /> # You need to define each capability once, so that Moodle can upgrade existing roles to take advantage of it. You do this in an access.php inside the db folder of any module (eg see mod/forum/db/access.php). The array contains entries like this (note the descriptions for the legacy roles which provides forward compatibility):<br /> <br /> 'mod/forum:viewforum' =&gt; array(<br /> 'captype' =&gt; 'read',<br /> 'contextlevel' =&gt; CONTEXT_MODULE,<br /> 'legacy' =&gt; array(<br /> 'guest' =&gt; CAP_PREVENT,<br /> 'student' =&gt; CAP_ALLOW,<br /> 'teacher' =&gt; CAP_ALLOW,<br /> 'editingteacher' =&gt; CAP_ALLOW,<br /> 'coursecreator' =&gt; CAP_ALLOW,<br /> 'admin' =&gt; CAP_ALLOW<br /> )<br /> ),<br /> <br /> # To load/change these capabilities you need to bump the module version. There's no need to provide changes or differences as Moodle will scan the whole array and sort it out.<br /> # On each page you need to define the context the user is working in. For example, in the forum module:<br /> <br /> $context = get_context_instance(CONTEXT_MODULE, $cm-&gt;id);<br /> <br /> # Then, whenever you want to check that the current user has rights to do something, call has_capability() like this:<br /> <br /> if (!has_capability('mod/forum:viewforum', $context-&gt;id)) {<br /> print_error('nopermissiontoviewforum);<br /> }<br /> <br /> <br /> <br /> ==Scenario brainstorming==<br /> <br /> This section is for brainstorming some example roles that we would like to support. Note some of these *may* not be possible in 1.7.<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===Peer observer of teaching===<br /> Many institutions encourage peer observation of teaching, to encourage reflection on practice. In online environments this will be similar to moderation or inspection. The peer observer would need to be able to experience the course &quot;as a student&quot;, but also to be able to view summaries of usage, transcripts of interactions (forums/surveys/polls etc), grades assigned (e.g. in assignments).<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY=3+4 yr olds) and Key Stage 1 (KS1=5+6 yr olds) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary. In Key Stage 2 (KS2=7-11 yr olds) parents would be more monitoring but may join in as well.<br /> <br /> In Key stages 3 (KS3=12-14 yr olds) and 4 (KS4=15+16 yr olds) this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments. Also in all Key Satges there may be a home-school agreement which may be signed up to. Could this form part of a site policy system that incorporates a tickable list of activities the parent agrees to the child using (blogs/wikis/forums etc.)?<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> Again in the UK, parents have their own independent right of access to a child's educational records. Obviously, children's records must not be made available to other parties, including the parents of other children in the same class. Thus it would be necessary to associate parent accounts with their own child's accounts in such a way that they could, if so desired, have read access to their child's grades, answers and contributions, but generally not those of other children - this may be problematic in the case of wiki activities or forum posts.<br /> <br /> There is some concern that children's forum contributions etc may be constrained if their parents are able to read all that they write; this may be particularly problematic in areas such as Personal, Social and Health Education (PSHE), where some schools may choose to use obfuscated usernames.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===Alumnus=== An ALUMNUS should be able to search for all other ALUMNI of the school, interact with them and be enrolled in a seperate course - which is like a META course with all the content of his learning and interaction - as well as capabilities to be a part of this ALUMNI only course. All the teachers of courses during school years should automatically be a part of the ALUMNI course .. which means when an ALUMNUS is enrolled in a course, the original teachers of all his courses get enrolled ? --[[User:Anil Sharma|Anil Sharma]] 20:54, 15 July 2006 (WST)<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> In schools there is often a book review system. This may be covered by the lending system database but may not in which case a librarian may neeed to have a course area they can create a database template to handle the reviews in which case they may have a normal teacher style role? Off topic but course an integration with common schools database systems would be great.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Student - FERPA rights===<br /> <br /> A student that has asserted their FERPA rights to non-disclosure. Typically includes not publishing their name<br /> in any public place. Could include this student only being seen with an &quot;alias&quot; within course spaces. Is this an attribute rather<br /> than a role?<br /> <br /> ===Help Desk===<br /> <br /> Help desk agents that have read access for the purposes of trouble shooting. Some care in placing this role within a hierarchy<br /> of inheritance is needed, full access will be problematic with FERPA.<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> [[Category:Roles]]<br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=14355 2006-08-13T17:57:01Z

<p>Hatshepsut: /* Former Student */</p> <hr /> <div>'''Roles and permissions''' will be in Moodle 1.7 and are available in the developer version of Moodle.<br /> <br /> <br /> ==Definitions==<br /> <br /> A role is an identifier of the user's status in some context, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a description of some particular Moodle feature. Capabilities are associated with roles. For example, ''mod/forum:replypost'' is a capability.<br /> <br /> A permission is some value that is assigned for a capability for a particular role. For example, allow or prevent.<br /> <br /> A context is a &quot;space&quot; in the Moodle, such as courses, activity modules, blocks etc.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> <br /> {{Moodle 1.7}}The new system will allow authorized users to define an arbitrary number of roles (eg a teacher) <br /> <br /> A role consists of a list of permissions for different possible actions within Moodle (eg delete discussions, add activities etc)<br /> <br /> Roles can be applied to users in a context (eg assign Fred as a teacher in a particular course)<br /> <br /> Here are the possible contexts, listed from the most general to the most specific. <br /> <br /> #CONTEXT_SYSTEM<br /> #CONTEXT_PERSONAL<br /> #CONTEXT_USERID<br /> #CONTEXT_COURSECAT<br /> #CONTEXT_COURSE<br /> #CONTEXT_GROUP<br /> #CONTEXT_MODULE<br /> #CONTEXT_BLOCK<br /> <br /> An authorized user will be able to assign an arbitrary number of roles to each user in any context.<br /> <br /> Capabilities can have the following permissions:<br /> <br /> #CAP_INHERIT<br /> #CAP_ALLOW<br /> #CAP_PREVENT<br /> #CAP_PROHIBIT<br /> <br /> If no permission is defined, then the capability permission is inherited from a context that is more general than the current context. If we define different permission values for the same capability in different contexts, we say that we are overriding the capability in the more specific context.<br /> <br /> Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by enforcing the rule that the capability defined for a more specific context will win, unless a prohibit is encountered in a less specific context.<br /> <br /> For example, Mark has a student role at course level, which allows him to write into a wiki. But Mark also got assigned a Visitor role at a module context level (for a particular wiki) which prevents him from writing to the wiki (read only). Therefore, for this particular wiki, Mark will not be able to write to the wiki since the more specific context wins.<br /> <br /> If we set a prohibit on a capability, it means that the capability cannot be overridden and will always have a permission of prevent (deny). Prohibit always wins. For example, Jeff has a naughty student role that prohibits him from postings in any forums (for the whole site), but he's also assigned a facilitator role in &quot;Science forum&quot; in the course Science and Math 101. Since prohibit always wins, Jeff is unable to post in &quot;Science forum&quot;.<br /> <br /> Allow and prevent will cancel each other out if set for the same capability at the same context level. If this happens, we refer to the previous context level to determine the permission for the capability.<br /> <br /> This may sound more complex than it really is in practice. The upshot is that the system can be flexible enough to allow any combination of permissions.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the existing capabilities will be automatically retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, mirroring what we have in 1.6. With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> <br /> ==Capabilities==<br /> <br /> This will be a comprehensive list of capabilities (it's not complete yet). It is important that capability names are unique.<br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capability names start with 'moodle/'. The next word indicates what type of core capability it is, and the last word is the actual capability itself. The capabilities for the Moodle core are defined in lib/db/access.php<br /> <br /> <br /> #moodle/legacy:guest - legacy capabilities are used to transition existing users to the new roles system during the upgrade to Moodle 1.7<br /> #moodle/legacy:student<br /> #moodle/legacy:teacher<br /> #moodle/legacy:editingteacher<br /> #moodle/legacy:coursecreator<br /> #moodle/legacy:admin<br /> #moodle/site:doanything - special capability, meant for admins, if is set, overrides all other capability settings<br /> #moodle/site:config - applicable in admin/index.php and config.php (might break down later) : 1)admin/config.php 2)admin/configure.php 3)blocks/admin/block_admin.php load_content_for_site()<br /> #moodle/site:manageblocks - adding/removing/editing blocks (site, course contexts only for now) : 1)_add_edit_controls moodleblock.class.php <br /> #moodle/site:backup - can create a course backup : 1)course/category.php 2)block_admin.php<br /> #moodle/site:restore - can restore into this context : 1)course/category.php 2)block_admin.php<br /> #moodle/site:import - can import other courses into this context : 1)block_admin.php<br /> #moodle/site:accessallgroups - able to access all groups irrespective of what group the user is in<br /> #moodle/blog:view - read blogs<br /> #moodle/blog:create - write new blog posts<br /> #moodle/blog:manageofficialtags - create/delete official blog tags that others can use<br /> #moodle/blog:managepersonaltags - create/delete official blog tags that others can use<br /> #moodle/blog:manageentries - edit/delete all blog entries<br /> #moodle/course:create - create courses : 1)course/edit.php 2)course/category.php 3)course/index.php<br /> #moodle/course:delete - create courses : 1)course/category.php<br /> #moodle/course:update - update course settings<br /> #moodle/course:view - can use this to find participants<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:viewscales - view scales (i.e. in a help window?) : 1)course/scales.php<br /> #moodle/course:manageactivities - adding/removing/editing activities and resources (don't think it makes any sense to split these)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down : 1)blocks/block_admin.php 2)course/scales.php<br /> #moodle/course:managegroups - managing groups, add, edit, delete : 1)course/groups.php 2)course/group.php<br /> #moodle/course:visibility - hide/show courses : 1)course/category.php<br /> #moodle/course:activityvisibility - hide/show activities within a course<br /> #moodle/course:viewhiddenactivities - able to see activities that have been hidden<br /> #moodle/category:create - create category : 1)course/index.php<br /> #moodle/category:delete - delete category : 1)course/index.php<br /> #moodle/category:update - update category settings : 1)course/category.php<br /> #moodle/category:visibility - hide/show categories : 1)course/index.php<br /> #moodle/user:create - create user : 1) user/edit.php<br /> #moodle/user:delete - delete user : 1) admin/user.php<br /> #moodle/user:update - update user settings : 1) user/edit.php<br /> #moodle/user:viewdetails - view personally-identifying user details (e.g. name, photo). This ties in with the &quot;visitor&quot; scenario described below.<br /> #moodle/calendar:manageownentries - create/edit/delete <br /> #moodle/calendar:manageentries - create/edit/delete<br /> #moodle/role:assign - assign roles to users<br /> #moodle/role:manage - create/edit/delete roles, set capability permissions for each role<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The part before the colon is the full path to the module in the Moodle code. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:view- reading the assignment description<br /> ##mod/assignment:submit - turn assignment in<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entries<br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:viewhiddentimedposts<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:viewrating<br /> ##mod/forum:viewanyrating<br /> ##mod/forum:rate<br /> ##mod/forum:createattachment<br /> ##mod/forum:deleteownpost<br /> ##mod/forum:deleteanypost<br /> ##mod/forum:splitdiscussions<br /> ##mod/forum:movediscussions<br /> ##mod/forum:editanypost<br /> ##mod/forum:viewqandawithoutposting<br /> ##mod/forum:viewsubscribers<br /> ##mod/forum:managesubscriptions<br /> ##mod/forum:throttlingapplies<br /> #Glossary<br /> ##mod/glossary:view - read entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:viewrating - view ratings<br /> #Hotpot<br /> ##mod/hotpot:view<br /> #Label<br /> ##none<br /> #Lams<br /> ##TBD<br /> #Lesson<br /> ##TBD<br /> #Quiz<br /> ##TBD<br /> #Resource<br /> ##mod/resource:view<br /> #Scorm<br /> ##mod/scorm:view<br /> ##mod/scorm:viewgrades<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> ##Waiting on new wiki<br /> #Workshop<br /> ##Waiting on new Workshop<br /> <br /> ===Enrolment-level Capabilities===<br /> <br /> The naming convention for capabilities that are specific to enrolment is 'enrol/enrol_name:capability'. The enrolment capabilities are defined in enrol/enrol_name/db/access.php.<br /> <br /> #Authorize.net Payment Gateway <br /> ##enrol/authorize:managepayments - manage user payments, capture, void, refund, delete etc.<br /> <br /> <br /> ===Blocks===<br /> <br /> ===Questions===<br /> I am adding question categories here because they seem to have been forgotten in the whole scheme of things since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in [http://www.moodle.org/bugs/bug.php?op=show&amp;bugid=6118&amp;pos= bug 6118].<br /> <br /> See [http://moodle.org/mod/forum/discuss.php?d=51143 this forum thread] for a discussion about the current problems wth publishing question categories.[[User:Tim Hunt|Tim Hunt]] 18:50, 8 August 2006 (WST)<br /> <br /> <br /> ==Programming Interface==<br /> <br /> Although the Roles system may look complicated at first glance, implementing it in Moodle code is fairly simple.<br /> <br /> # You need to define each capability once, so that Moodle can upgrade existing roles to take advantage of it. You do this in an access.php inside the db folder of any module (eg see mod/forum/db/access.php). The array contains entries like this (note the descriptions for the legacy roles which provides forward compatibility):<br /> <br /> 'mod/forum:viewforum' =&gt; array(<br /> 'captype' =&gt; 'read',<br /> 'contextlevel' =&gt; CONTEXT_MODULE,<br /> 'legacy' =&gt; array(<br /> 'guest' =&gt; CAP_PREVENT,<br /> 'student' =&gt; CAP_ALLOW,<br /> 'teacher' =&gt; CAP_ALLOW,<br /> 'editingteacher' =&gt; CAP_ALLOW,<br /> 'coursecreator' =&gt; CAP_ALLOW,<br /> 'admin' =&gt; CAP_ALLOW<br /> )<br /> ),<br /> <br /> # To load/change these capabilities you need to bump the module version. There's no need to provide changes or differences as Moodle will scan the whole array and sort it out.<br /> # On each page you need to define the context the user is working in. For example, in the forum module:<br /> <br /> $context = get_context_instance(CONTEXT_MODULE, $cm-&gt;id);<br /> <br /> # Then, whenever you want to check that the current user has rights to do something, call has_capability() like this:<br /> <br /> if (!has_capability('mod/forum:viewforum', $context-&gt;id)) {<br /> print_error('nopermissiontoviewforum);<br /> }<br /> <br /> <br /> <br /> ==Scenario brainstorming==<br /> <br /> This section is for brainstorming some example roles that we would like to support. Note some of these *may* not be possible in 1.7.<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===Peer observer of teaching===<br /> Many institutions encourage peer observation of teaching, to encourage reflection on practice. In online environments this will be similar to moderation or inspection. The peer observer would need to be able to experience the course &quot;as a student&quot;, but also to be able to view summaries of usage, transcripts of interactions (forums/surveys/polls etc), grades assigned (e.g. in assignments).<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY=3+4 yr olds) and Key Stage 1 (KS1=5+6 yr olds) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary. In Key Stage 2 (KS2=7-11 yr olds) parents would be more monitoring but may join in as well.<br /> <br /> In Key stages 3 (KS3=12-14 yr olds) and 4 (KS4=15+16 yr olds) this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments. Also in all Key Satges there may be a home-school agreement which may be signed up to. Could this form part of a site policy system that incorporates a tickable list of activities the parent agrees to the child using (blogs/wikis/forums etc.)?<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> Again in the UK, parents have their own independent right of access to a child's educational records. Obviously, children's records must not be made available to other parties, including the parents of other children in the same class. Thus it would be necessary to associate parent accounts with their own child's accounts in such a way that they could, if so desired, have read access to their child's grades, answers and contributions, but generally not those of other children - this may be problematic in the case of wiki activities or forum posts.<br /> <br /> There is some concern that children's forum contributions etc may be constrained if their parents are able to read all that they write; this may be particularly problematic in areas such as Personal, Social and Health Education (PSHE), where some schools may choose to use obfuscated usernames.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===ALUMNUS=== An ALUMNUS should be able to search for all other ALUMNI of the school, interact with them and be enrolled in a seperate course - which is like a META course with all the content of his learning and interaction - as well as capabilities to be a part of this ALUMNI only course. All the teachers of courses during school years should automatically be a part of the ALUMNI course .. which means when an ALUMNUS is enrolled in a course, the original teachers of all his courses get enrolled ? --[[User:Anil Sharma|Anil Sharma]] 20:54, 15 July 2006 (WST)<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> In schools there is often a book review system. This may be covered by the lending system database but may not in which case a librarian may neeed to have a course area they can create a database template to handle the reviews in which case they may have a normal teacher style role? Off topic but course an integration with common schools database systems would be great.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Student - FERPA rights===<br /> <br /> A student that has asserted their FERPA rights to non-disclosure. Typically includes not publishing their name<br /> in any public place. Could include this student only being seen with an &quot;alias&quot; within course spaces. Is this an attribute rather<br /> than a role?<br /> <br /> ===Help Desk===<br /> <br /> Help desk agents that have read access for the purposes of trouble shooting. Some care in placing this role within a hierarchy<br /> of inheritance is needed, full access will be problematic with FERPA.<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> [[Category:Roles]]<br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Wikindx&diff=14075 2006-08-08T22:53:52Z

<p>Hatshepsut: changes to 3, added 4</p> <hr /> <div>'''Notes on the possible integration of [http://wikindx.sourceforge.net/index2.html WIKINDX] with Moodle.'''<br /> <br /> [http://wikindx.sourceforge.net/index2.html WIKINDX]is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.<br /> <br /> Please also see the Moodle Discussion at http://moodle.org/mod/forum/discuss.php?d=23022<br /> <br /> Dan Stowell has created a &quot;Wikindx filter&quot; for Moodle which allows you to cross-link to a wikindx entry by typing (for example) wikindx:646. The filter is in contrib CVS, named &quot;filter_wikindx&quot; or can be downloaded at http://download.moodle.org/download.php/modules/filter_wikindx.zip<br /> <br /> '''Outline thoughts on integration...'''<br /> <br /> 1. Do we need to allowing a user already logged into a Moodle site to be seamlessly logged in to a wikindx? Or maybe just use the same login details between the two (like the way that Moodle.org and MoodleDocs works). If necessary, something could be added to wikindx to enable this. In most cases though, with the right config settings, wikindx will allow any read only request without requiring login.<br /> <br /> 2. Another issue is how to integrate the paper writing function of Wikindx into Moodle. What about use of the HTML editor? Could it be integrated some way with the Netpublish module? Imagine students or professors being able to use it to write academic papers and then publish those on the Moodle site. Currently wikindx publishes papers solely to RTF. It should be simple to publish to HTML since that's what the raw document is anyway (a matter of adding HTML header/footer, formatting citations and appending bibliographies -- most of this code is already in wikindx but not (yet) made available to the word processor). Compared to other HTML editors, the only additional options wikindx offers in its version are buttons to import citations, metadata and insert footnotes. All the rest (barring stats, timestamps, save etc.) are font/text formatting.<br /> <br /> 3. For the filter above, how do you decide what bibliographic style to present in (APA, Chicago, IEEE etc.)? Presumably, this is something that could be set in the filter config file. (Although I haven't seen the filter in operation, I'm assuming it picks up a properly formatted reference for insert. Either short (Grimshaw, 2006) or long (Grimshaw, Mark N. 2006, WIKINDX [OSS].) for example. Is the only method of citation available parenthetical? Is it possible to use endnotes (or footnotes) as well?<br /> <br /> 4. Mark, your remarks in 2 have gotten me thinking. Although not everyone likes the Moodle HTML area editor that much, it still is the standard way of creating text in Moodle and perhaps a way of integrating Wikindx would be to add buttons for Wikindx to it, just like the kind described above in Wikindx's native editor. I needed to integrate a hieroglyph editor into my site and Janne Mikkonen helped me to add it through a button in the html editor that pops up a window, in which the student type the hieroglyphs they need, and then click a button to have them inserted back into the editor-similar to the way the insert image popup works. I would imagine something similar could be done with Wikindx. The advantage of this is that it would make Wikindx accessible anywhere within Moodle, rather than just as a separate module. You might also want a standalone module option whereby students could collaborate on creating bibliographies together.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Wikindx&diff=14065 2006-08-08T17:49:57Z

<p>Hatshepsut: </p> <hr /> <div>'''Notes on the possible integration of [http://wikindx.sourceforge.net/index2.html WIKINDX] with Moodle.'''<br /> <br /> [http://wikindx.sourceforge.net/index2.html WIKINDX]is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.<br /> <br /> Please also see the Moodle Discussion at http://moodle.org/mod/forum/discuss.php?d=23022<br /> <br /> Dan Stowell has created a &quot;Wikindx filter&quot; for Moodle which allows you to cross-link to a wikindx entry by typing (for example) wikindx:646. The filter is in contrib CVS, named &quot;filter_wikindx&quot; or can be downloaded at http://download.moodle.org/download.php/modules/filter_wikindx.zip<br /> <br /> '''Outline thoughts on integration...'''<br /> <br /> 1. Do we need to allowing a user already logged into a Moodle site to be seamlessly logged in to a wikindx? Or maybe just use the same login details between the two (like the way that Moodle.org and MoodleDocs works).<br /> <br /> 2. Another issue is how to integrate the paper writing function of Wikindx into Moodle. What about use of the HTML editor? Could it be integrated some way with the Netpublish module? Imagine students or professors being able to use it to write academic papers and then publish those on the Moodle site.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Wikindx&diff=14064 2006-08-08T17:44:19Z

<p>Hatshepsut: </p> <hr /> <div>'''Notes on the possible integration of [http://wikindx.sourceforge.net/index2.html WIKINDX] with Moodle.'''<br /> <br /> [http://wikindx.sourceforge.net/index2.html WIKINDX]is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.<br /> <br /> Please also see the Moodle Discussion at http://moodle.org/mod/forum/discuss.php?d=23022<br /> <br /> Dan Stowell has created a &quot;Wikindx filter&quot; for Moodle which allows you to cross-link to a wikindx entry by typing (for example) wikindx:646. The filter is in contrib CVS, named &quot;filter_wikindx&quot; or can be downloaded at http://download.moodle.org/download.php/modules/filter_wikindx.zip<br /> <br /> '''Outline thoughts on integration...'''<br /> <br /> 1. Do we need to allowing a user already logged into a Moodle site to be seamlessly logged in to a wikindx? Or maybe just use the same login details between the two (like the way that Moodle.org and MoodleDocs works).<br /> <br /> 2. To really make this useful it would be helpful if it could be integrated in a way that allowed it to be used to author papers with footnotes and/or endnotes directly within Moodle. It think the Wikindx developer was working toward this at some point, but I havent' been following it.<br /> <br /> 3. Related to number 2 above, I'd love to see it integrated in some way with the new wiki. It would make a great tool for collaborative writing of academic papers.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Bug_tracker&diff=13478 2006-07-28T20:02:44Z

<p>Hatshepsut: /* Tracking progress of bugs you have reported */</p> <hr /> <div>Bug tracking is a very important part of a continous quality control process. Unlike most proprietary software programs, Moodle bug reporting and bug tracking information is open to everyone. <br /> <br /> Please register on the [http://moodle.org/bugs Moodle bug tracker] so you can file any bugs that you find and perhaps participate in discussing and fixing them.<br /> <br /> &quot;Bugs&quot; not only includes software problems with current versions of Moodle, but also new ideas, feature requests and even constructive criticism of existing features.<br /> <br /> The beauty of open source is that anyone can participate in some way and help to create a better product for all of us to enjoy. In this project, your input is very welcome!<br /> <br /> == General guidelines ==<br /> <br /> The best bug reports follow this form:<br /> <br /> #'''Steps to reproduce'''. That is, a detailed sequence of steps the developer canfollow to see the problem on their own server. It is very hard to fix a bug that is not reproducable. If possible, give us a URL so we can see the problem with one click.<br /> #'''What I expected to happen'''. Again, with detail. You expectation might mean that our instructions need to improve or our interface should be changed.<br /> #'''What actually happened''' (with detail).<br /> <br /> Here is an example of [http://moodle.org/bugs/bug.php?op=show&amp;bugid=6030 a good bug report], [http://moodle.org/bugs/bug.php?op=show&amp;bugid=5688 and another].<br /> <br /> *If you have an error message, or information in your PHP or web server logs, copy and paste it exactly into the bug report. If you can, turn on &quot;debug&quot; in your Admin configuration page and reprodoce the problem to get the best possible error message.<br /> *Screen shots are very helpful for some bugs, but please write a textual description of the problem too.<br /> *Make sure we know everything we need to know about your setup. The OS, Database, etc. fields at the top right of the form give some of the information, but if in doubt add more in the description. The full set of information that might be relevant is:<br /> **Server operating system type and version number<br /> **Web server type and version number<br /> **PHP version number (and whether you are using an accellerator)<br /> **Database type and version number<br /> **Moodle version (this is probably covered by the dropdown at the top of the form.)<br /> **Client-side operating system type and version number<br /> **Web browser type and version number<br /> <br /> You don't need to give all those details all the time. For example, for a layout rendering problem, you need to give only the client-side OS and browser info, and if it is a server-side problem you only need to describe the setup there. Use your judgement. Here are some examples:<br /> <br /> ::I see this bug with the latest Moodle HEAD running on PHP5.1.2/Apache 2.2.3 on Linux. My database is Postgres 8.1.<br /> <br /> ::This rendering problem happens on IE5.0 on Windows 98.<br /> <br /> In summary stick with facts and present enough facts so someone else can try to duplicate the problem.<br /> <br /> ==Tracking progress of bugs you have reported==<br /> You will receive email reports of updates to bugs you report unless you un-tick &quot;Receive notifications of issue changes via email&quot; on your personal page in the Bug Tracker. However, because it is very likely that the person who sits down to fix the bug will need to contact you for more information, you will probably want to keep this ticked.<br /> <br /> ==Tracking bugs reported by others==<br /> Enter your Bug Tracker user name (this may be different to your Moodle.org user name) in the &quot;Add CC&quot; field for the bug you wish to track and click the &quot;Save changes&quot; button. You will receive email updates on the bug.<br /> <br /> == Developer comments ==<br /> <br /> &quot;What’s the hardest thing about a bug report?&quot; Most of the time fixing the bug is the easiest part. Usually the hard part is reproducing the bug. The developer or problem solver needs to see how it is broke to be able to fix it. And if they can not duplicate the error, then they can not be sure that it is fixed.<br /> <br /> Good bug reports contain as much detail as possible and are specific. Generalizing and leaping to conclusions in a bug report is not helpful and often incorrect.<br /> <br /> For example, a bug report that only says &quot;The RSS feed doesn’t support UTF-8&quot; is not helpful. The developer knows that UTF-8 and RSS feeds are compatible. The problem solver has no idea of what the person sees and why they reported this bug. Now there has to be more communication (which is time) to determine what happened.<br /> <br /> Consider a bug report which says that the descriptions for the specific RSS feed XYZ@abc shows as garbage characters rather than the expected characters.<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=43952 How to manipulate Moodle developers] forum discussion<br /> <br /> *Here is one [http://en.wikipedia.org/wiki/Software_bug definition of a bug.]<br /> <br /> [[Category:Teacher]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]<br /> [[Category:Developer tools]]<br /> <br /> [[es:Sistema de bugs]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=13139 2006-07-15T12:24:22Z

<p>Hatshepsut: /* Questions */</p> <hr /> <div>'''Roles and capabilities''' are planned to be included in Moodle 1.7. For now, we have some basic ideas of how to implement such a structure in Moodle.<br /> <br /> ''Please note that none of the following is finalised.''<br /> <br /> ==Definitions==<br /> <br /> By roles, we mean an identifier of the user's status, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a permission to access some particular Moodle feature. Capabilities are associated with roles. For example, ''forum_canreadpost'' is a capability.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> The new system will allow authorized users to define an arbitrary number of roles. Each role can have a customizable set of capabilities in every context. A context can be the whole Moodle site, a course, or a module instance, e.g. quiz 5 in 'Introduction to Photography'. An authorized user will be able to assign an arbitrary number of roles to each user. Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by giving roles different 'priorities'. For example, to prevent a naughty student from posting, one could assign him a 'naughty student' role that does not allow him to post. This role should have a priority higher than that of a normal 'student' role. <br /> <br /> To facilitate exceptional cases in roles and capabilities, we can use exception rules. For example, we can specify a rule saying that all students are able to mark/read other students' assignment in this particular course. Note that such rules need to have a priority as well. The capability of a user, in any context is then resolved by finding the highest priority role/rule.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the exisiting capabilities will be retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, which pretty much is what we have in 1.6. The whole process is automatic so there's nothing to worry about =). With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> ==The plan==<br /> <br /> There are a few major things that need to be done. Here's a list (in no particular order):<br /> <br /> #Identify permissions required for site/course/each module.<br /> #Define the database structure for storing roles and capabilities.<br /> #Recode the whole of Moodle, including all modules to support the new structure. Instead of using &lt;code&gt;isteacher()&lt;/code&gt; or &lt;code&gt;isstudent()&lt;/code&gt; we should be using &lt;code&gt;has_capability($capability, $instanceid)&lt;/code&gt; etc. A new API for handling roles and capabilities will be implemented (accesslib.php).<br /> #Add storage of capabilities for each module. Can be done either in a file, e.g. db/capability.xml, or as a sql file that gets installed to a central db whenever this module is installed. Either way, what do we do when we need to upgrade these capabilities? Some capabilities might need refining/splitting later on. How do we control the 'version' of a capability?<br /> #Consider interface issues, especially how to manage conflicting role/exception rules.<br /> #Upon logging in, we should use a cache to store capability, down to module level. How should that be structured?<br /> #Consider the impact on backup/restore.<br /> #Upgrade path for current users. The user information in table user_coursecreators, user_admins, user_teachers, and user_students will most likely be migrated to the new roles and capabilities tables. The users will most likely be assigned default roles that comes with default capabilities (e.g. teachers, admins, students, etc). The old tables themselves could possibly be dropped at the end of the upgrade.<br /> <br /> ==Capabilities==<br /> <br /> This is a comprehensive list of capabilities, well, in the making. It is important that capability names are unique. Please edit. Should we distinguish canedit and candelete?<br /> <br /> What about a canview capability? Like for choice, where a person is allowed to see the choice question but not participate in it? --[[User:N Hansen|N Hansen]] 19:29, 16 May 2006 (WST)<br /> <br /> Certainly need a canview or cansee capability for parents as linked to their child's data/contributions.<br /> <br /> Do we need to add canview and cansearch logs at site/course/user/group level?<br /> <br /> I could use a canview at a course level, if I understand what that means exactly.--[[User:N Hansen|N Hansen]] 19:43, 12 June 2006 (WST)<br /> <br /> <br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capabilitie names start with 'moodle/'. The capabilities for the Moodle core are defined in lib/db/access.php<br /> Do we still keep student view? What is a student view?<br /> <br /> #moodle/site:config - applicialbe in admin/index.php and config.php (might break down later)<br /> #moodle/course:create - create courses<br /> #moodle/course:view - possibly a capability used for checking student role<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:update - updates a course, i.e. adding/removing/editting activities <br /> #moodle/course:viewscales - view scales (i.e. in a help window?)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down<br /> #moodle/course:managegroups - managing groups, add, delete, add user in etc<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:read - reading the assignment description<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entry <br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:managediscussions<br /> ##mod/forum:viewrating<br /> ##mod/forum:rate<br /> #Glossary<br /> ##mod/glossary:read - view entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:readrate - view rating?<br /> #Hotpot<br /> #Label<br /> #Lams<br /> #Lesson<br /> #Quiz<br /> #Resource<br /> #Scorm<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> #Workshop<br /> <br /> ==OU Desired Capabilities==<br /> <br /> We will use this page to detail the specific capabilities needed to create the roles for the OU. Each capability has three parts:<br /> <br /> # the name itself which can be anything and should be simple and short<br /> # the name of the module it belongs to (&quot;moodle&quot;, &quot;blog&quot;, &quot;course&quot;, &quot;forum&quot; etc)<br /> # the name of the &quot;class&quot; it belongs to, currently &quot;read&quot; or &quot;write&quot;. We can change <br /> this in future if we can work out a sensible scheme. This is purely used for the <br /> GUI to &quot;clump&quot; similar capabilties together<br /> <br /> I would recommend we create a table for each module with the name, module and class of the capability<br /> <br /> ==Moodle Site==<br /> <br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Catagory&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;View Courses&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add User&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move course to another category&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Make course visible to students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;new features? Site wide subscription default/setting&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;optional/forced etc&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;recommended default optional for all OU forums&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;used to ban individuals from Moodle?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Course - home page ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add Blocks&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;On/Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT &amp; Staff = Off, Admins = On&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add/View users ALs/Staff/Students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = Read (this should be managed through circe or the administrator). Admins = Write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Course settings&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course teams = Read, Staff = no access. Admins = write&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move blocks?&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = off, Admin = on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete resource/page/activity/block &lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff= off, Admin = on. As we have no recovery process would it be best to prevent course teams from deleting resource pages &amp; other items on the home page?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;hide items&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, staff=off, admin=on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add resource&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which resource types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add activity&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which activity types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;upload calendar (OU feature?)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write. CTs should not be able to upload a calendar (admin will add this &amp; need to ensure the CT don't overwrite it with an alternative) &lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit calendar&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=write, Staff=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;admin functions, e.g. back up, restore, import&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit groups&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admins = write CT/Moderators=on staff=read?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Course - resource page (OU version) ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add authid&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admin=Write, CT=Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add placeholder&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT=Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add RSS feed&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, ct=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/noaccess&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;use to restrict access to pages by role?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Forum==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;move discussion to (archive/move feature)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;update this forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=write, CT/Moderator=off? it would be good to break this down further and or premote some defaults for use. e.g subscription I think there should be a server wide default of optional for all OU forums which can't be oevrriden at the course level.&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;delete message/thread&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off? some course teams won't want students/als to be able to delete their own posts&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;split&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;post to forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;attach file to message&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Blog==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Quiz==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Wiki==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Resources==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Questions==<br /> I am adding question categories here because they seem to have been forgotten in the whole scheme of things since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in [http://www.moodle.org/bugs/bug.php?op=show&amp;bugid=6118&amp;pos= bug 6118].<br /> <br /> ==Scenarios==<br /> <br /> This section is for brainstorming some example roles that we would like to support:<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY) and Key Stage 1 (KS1) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary.<br /> <br /> In Key stages 3 and 4 this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments.<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> <br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=13138 2006-07-15T12:23:54Z

<p>Hatshepsut: /* Questions */</p> <hr /> <div>'''Roles and capabilities''' are planned to be included in Moodle 1.7. For now, we have some basic ideas of how to implement such a structure in Moodle.<br /> <br /> ''Please note that none of the following is finalised.''<br /> <br /> ==Definitions==<br /> <br /> By roles, we mean an identifier of the user's status, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a permission to access some particular Moodle feature. Capabilities are associated with roles. For example, ''forum_canreadpost'' is a capability.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> The new system will allow authorized users to define an arbitrary number of roles. Each role can have a customizable set of capabilities in every context. A context can be the whole Moodle site, a course, or a module instance, e.g. quiz 5 in 'Introduction to Photography'. An authorized user will be able to assign an arbitrary number of roles to each user. Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by giving roles different 'priorities'. For example, to prevent a naughty student from posting, one could assign him a 'naughty student' role that does not allow him to post. This role should have a priority higher than that of a normal 'student' role. <br /> <br /> To facilitate exceptional cases in roles and capabilities, we can use exception rules. For example, we can specify a rule saying that all students are able to mark/read other students' assignment in this particular course. Note that such rules need to have a priority as well. The capability of a user, in any context is then resolved by finding the highest priority role/rule.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the exisiting capabilities will be retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, which pretty much is what we have in 1.6. The whole process is automatic so there's nothing to worry about =). With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> ==The plan==<br /> <br /> There are a few major things that need to be done. Here's a list (in no particular order):<br /> <br /> #Identify permissions required for site/course/each module.<br /> #Define the database structure for storing roles and capabilities.<br /> #Recode the whole of Moodle, including all modules to support the new structure. Instead of using &lt;code&gt;isteacher()&lt;/code&gt; or &lt;code&gt;isstudent()&lt;/code&gt; we should be using &lt;code&gt;has_capability($capability, $instanceid)&lt;/code&gt; etc. A new API for handling roles and capabilities will be implemented (accesslib.php).<br /> #Add storage of capabilities for each module. Can be done either in a file, e.g. db/capability.xml, or as a sql file that gets installed to a central db whenever this module is installed. Either way, what do we do when we need to upgrade these capabilities? Some capabilities might need refining/splitting later on. How do we control the 'version' of a capability?<br /> #Consider interface issues, especially how to manage conflicting role/exception rules.<br /> #Upon logging in, we should use a cache to store capability, down to module level. How should that be structured?<br /> #Consider the impact on backup/restore.<br /> #Upgrade path for current users. The user information in table user_coursecreators, user_admins, user_teachers, and user_students will most likely be migrated to the new roles and capabilities tables. The users will most likely be assigned default roles that comes with default capabilities (e.g. teachers, admins, students, etc). The old tables themselves could possibly be dropped at the end of the upgrade.<br /> <br /> ==Capabilities==<br /> <br /> This is a comprehensive list of capabilities, well, in the making. It is important that capability names are unique. Please edit. Should we distinguish canedit and candelete?<br /> <br /> What about a canview capability? Like for choice, where a person is allowed to see the choice question but not participate in it? --[[User:N Hansen|N Hansen]] 19:29, 16 May 2006 (WST)<br /> <br /> Certainly need a canview or cansee capability for parents as linked to their child's data/contributions.<br /> <br /> Do we need to add canview and cansearch logs at site/course/user/group level?<br /> <br /> I could use a canview at a course level, if I understand what that means exactly.--[[User:N Hansen|N Hansen]] 19:43, 12 June 2006 (WST)<br /> <br /> <br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capabilitie names start with 'moodle/'. The capabilities for the Moodle core are defined in lib/db/access.php<br /> Do we still keep student view? What is a student view?<br /> <br /> #moodle/site:config - applicialbe in admin/index.php and config.php (might break down later)<br /> #moodle/course:create - create courses<br /> #moodle/course:view - possibly a capability used for checking student role<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:update - updates a course, i.e. adding/removing/editting activities <br /> #moodle/course:viewscales - view scales (i.e. in a help window?)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down<br /> #moodle/course:managegroups - managing groups, add, delete, add user in etc<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:read - reading the assignment description<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entry <br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:managediscussions<br /> ##mod/forum:viewrating<br /> ##mod/forum:rate<br /> #Glossary<br /> ##mod/glossary:read - view entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:readrate - view rating?<br /> #Hotpot<br /> #Label<br /> #Lams<br /> #Lesson<br /> #Quiz<br /> #Resource<br /> #Scorm<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> #Workshop<br /> <br /> ==OU Desired Capabilities==<br /> <br /> We will use this page to detail the specific capabilities needed to create the roles for the OU. Each capability has three parts:<br /> <br /> # the name itself which can be anything and should be simple and short<br /> # the name of the module it belongs to (&quot;moodle&quot;, &quot;blog&quot;, &quot;course&quot;, &quot;forum&quot; etc)<br /> # the name of the &quot;class&quot; it belongs to, currently &quot;read&quot; or &quot;write&quot;. We can change <br /> this in future if we can work out a sensible scheme. This is purely used for the <br /> GUI to &quot;clump&quot; similar capabilties together<br /> <br /> I would recommend we create a table for each module with the name, module and class of the capability<br /> <br /> ==Moodle Site==<br /> <br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Catagory&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;View Courses&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add User&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move course to another category&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Make course visible to students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;new features? Site wide subscription default/setting&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;optional/forced etc&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;recommended default optional for all OU forums&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;used to ban individuals from Moodle?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Course - home page ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add Blocks&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;On/Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT &amp; Staff = Off, Admins = On&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add/View users ALs/Staff/Students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = Read (this should be managed through circe or the administrator). Admins = Write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Course settings&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course teams = Read, Staff = no access. Admins = write&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move blocks?&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = off, Admin = on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete resource/page/activity/block &lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff= off, Admin = on. As we have no recovery process would it be best to prevent course teams from deleting resource pages &amp; other items on the home page?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;hide items&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, staff=off, admin=on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add resource&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which resource types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add activity&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which activity types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;upload calendar (OU feature?)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write. CTs should not be able to upload a calendar (admin will add this &amp; need to ensure the CT don't overwrite it with an alternative) &lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit calendar&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=write, Staff=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;admin functions, e.g. back up, restore, import&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit groups&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admins = write CT/Moderators=on staff=read?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Course - resource page (OU version) ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add authid&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admin=Write, CT=Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add placeholder&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT=Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add RSS feed&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, ct=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/noaccess&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;use to restrict access to pages by role?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Forum==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;move discussion to (archive/move feature)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;update this forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=write, CT/Moderator=off? it would be good to break this down further and or premote some defaults for use. e.g subscription I think there should be a server wide default of optional for all OU forums which can't be oevrriden at the course level.&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;delete message/thread&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off? some course teams won't want students/als to be able to delete their own posts&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;split&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;post to forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;attach file to message&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Blog==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Quiz==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Wiki==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Resources==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Questions==<br /> I am adding question categories here because they seem to have been forgotten since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in [http://www.moodle.org/bugs/bug.php?op=show&amp;bugid=6118&amp;pos= bug 6118].<br /> <br /> ==Scenarios==<br /> <br /> This section is for brainstorming some example roles that we would like to support:<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY) and Key Stage 1 (KS1) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary.<br /> <br /> In Key stages 3 and 4 this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments.<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> <br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=13137 2006-07-15T12:23:38Z

<p>Hatshepsut: /* Questions */</p> <hr /> <div>'''Roles and capabilities''' are planned to be included in Moodle 1.7. For now, we have some basic ideas of how to implement such a structure in Moodle.<br /> <br /> ''Please note that none of the following is finalised.''<br /> <br /> ==Definitions==<br /> <br /> By roles, we mean an identifier of the user's status, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a permission to access some particular Moodle feature. Capabilities are associated with roles. For example, ''forum_canreadpost'' is a capability.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> The new system will allow authorized users to define an arbitrary number of roles. Each role can have a customizable set of capabilities in every context. A context can be the whole Moodle site, a course, or a module instance, e.g. quiz 5 in 'Introduction to Photography'. An authorized user will be able to assign an arbitrary number of roles to each user. Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by giving roles different 'priorities'. For example, to prevent a naughty student from posting, one could assign him a 'naughty student' role that does not allow him to post. This role should have a priority higher than that of a normal 'student' role. <br /> <br /> To facilitate exceptional cases in roles and capabilities, we can use exception rules. For example, we can specify a rule saying that all students are able to mark/read other students' assignment in this particular course. Note that such rules need to have a priority as well. The capability of a user, in any context is then resolved by finding the highest priority role/rule.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the exisiting capabilities will be retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, which pretty much is what we have in 1.6. The whole process is automatic so there's nothing to worry about =). With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> ==The plan==<br /> <br /> There are a few major things that need to be done. Here's a list (in no particular order):<br /> <br /> #Identify permissions required for site/course/each module.<br /> #Define the database structure for storing roles and capabilities.<br /> #Recode the whole of Moodle, including all modules to support the new structure. Instead of using &lt;code&gt;isteacher()&lt;/code&gt; or &lt;code&gt;isstudent()&lt;/code&gt; we should be using &lt;code&gt;has_capability($capability, $instanceid)&lt;/code&gt; etc. A new API for handling roles and capabilities will be implemented (accesslib.php).<br /> #Add storage of capabilities for each module. Can be done either in a file, e.g. db/capability.xml, or as a sql file that gets installed to a central db whenever this module is installed. Either way, what do we do when we need to upgrade these capabilities? Some capabilities might need refining/splitting later on. How do we control the 'version' of a capability?<br /> #Consider interface issues, especially how to manage conflicting role/exception rules.<br /> #Upon logging in, we should use a cache to store capability, down to module level. How should that be structured?<br /> #Consider the impact on backup/restore.<br /> #Upgrade path for current users. The user information in table user_coursecreators, user_admins, user_teachers, and user_students will most likely be migrated to the new roles and capabilities tables. The users will most likely be assigned default roles that comes with default capabilities (e.g. teachers, admins, students, etc). The old tables themselves could possibly be dropped at the end of the upgrade.<br /> <br /> ==Capabilities==<br /> <br /> This is a comprehensive list of capabilities, well, in the making. It is important that capability names are unique. Please edit. Should we distinguish canedit and candelete?<br /> <br /> What about a canview capability? Like for choice, where a person is allowed to see the choice question but not participate in it? --[[User:N Hansen|N Hansen]] 19:29, 16 May 2006 (WST)<br /> <br /> Certainly need a canview or cansee capability for parents as linked to their child's data/contributions.<br /> <br /> Do we need to add canview and cansearch logs at site/course/user/group level?<br /> <br /> I could use a canview at a course level, if I understand what that means exactly.--[[User:N Hansen|N Hansen]] 19:43, 12 June 2006 (WST)<br /> <br /> <br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capabilitie names start with 'moodle/'. The capabilities for the Moodle core are defined in lib/db/access.php<br /> Do we still keep student view? What is a student view?<br /> <br /> #moodle/site:config - applicialbe in admin/index.php and config.php (might break down later)<br /> #moodle/course:create - create courses<br /> #moodle/course:view - possibly a capability used for checking student role<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:update - updates a course, i.e. adding/removing/editting activities <br /> #moodle/course:viewscales - view scales (i.e. in a help window?)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down<br /> #moodle/course:managegroups - managing groups, add, delete, add user in etc<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:read - reading the assignment description<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entry <br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:managediscussions<br /> ##mod/forum:viewrating<br /> ##mod/forum:rate<br /> #Glossary<br /> ##mod/glossary:read - view entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:readrate - view rating?<br /> #Hotpot<br /> #Label<br /> #Lams<br /> #Lesson<br /> #Quiz<br /> #Resource<br /> #Scorm<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> #Workshop<br /> <br /> ==OU Desired Capabilities==<br /> <br /> We will use this page to detail the specific capabilities needed to create the roles for the OU. Each capability has three parts:<br /> <br /> # the name itself which can be anything and should be simple and short<br /> # the name of the module it belongs to (&quot;moodle&quot;, &quot;blog&quot;, &quot;course&quot;, &quot;forum&quot; etc)<br /> # the name of the &quot;class&quot; it belongs to, currently &quot;read&quot; or &quot;write&quot;. We can change <br /> this in future if we can work out a sensible scheme. This is purely used for the <br /> GUI to &quot;clump&quot; similar capabilties together<br /> <br /> I would recommend we create a table for each module with the name, module and class of the capability<br /> <br /> ==Moodle Site==<br /> <br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Catagory&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;View Courses&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add User&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move course to another category&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Make course visible to students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;new features? Site wide subscription default/setting&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;optional/forced etc&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;recommended default optional for all OU forums&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;used to ban individuals from Moodle?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Course - home page ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add Blocks&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;On/Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT &amp; Staff = Off, Admins = On&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add/View users ALs/Staff/Students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = Read (this should be managed through circe or the administrator). Admins = Write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Course settings&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course teams = Read, Staff = no access. Admins = write&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move blocks?&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = off, Admin = on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete resource/page/activity/block &lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff= off, Admin = on. As we have no recovery process would it be best to prevent course teams from deleting resource pages &amp; other items on the home page?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;hide items&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, staff=off, admin=on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add resource&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which resource types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add activity&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which activity types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;upload calendar (OU feature?)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write. CTs should not be able to upload a calendar (admin will add this &amp; need to ensure the CT don't overwrite it with an alternative) &lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit calendar&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=write, Staff=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;admin functions, e.g. back up, restore, import&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit groups&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admins = write CT/Moderators=on staff=read?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Course - resource page (OU version) ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add authid&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admin=Write, CT=Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add placeholder&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT=Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add RSS feed&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, ct=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/noaccess&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;use to restrict access to pages by role?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Forum==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;move discussion to (archive/move feature)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;update this forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=write, CT/Moderator=off? it would be good to break this down further and or premote some defaults for use. e.g subscription I think there should be a server wide default of optional for all OU forums which can't be oevrriden at the course level.&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;delete message/thread&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off? some course teams won't want students/als to be able to delete their own posts&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;split&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;post to forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;attach file to message&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Blog==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Quiz==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Wiki==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Resources==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Questions==<br /> I am adding question categories here because they seem to have been forgotten since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in [[http://www.moodle.org/bugs/bug.php?op=show&amp;bugid=6118&amp;pos= bug 6118]].<br /> <br /> ==Scenarios==<br /> <br /> This section is for brainstorming some example roles that we would like to support:<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY) and Key Stage 1 (KS1) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary.<br /> <br /> In Key stages 3 and 4 this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments.<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> <br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Roles&diff=13136 2006-07-15T12:21:59Z

<p>Hatshepsut: </p> <hr /> <div>'''Roles and capabilities''' are planned to be included in Moodle 1.7. For now, we have some basic ideas of how to implement such a structure in Moodle.<br /> <br /> ''Please note that none of the following is finalised.''<br /> <br /> ==Definitions==<br /> <br /> By roles, we mean an identifier of the user's status, for example, teacher, student and forum moderator are examples of roles.<br /> <br /> A capability is a permission to access some particular Moodle feature. Capabilities are associated with roles. For example, ''forum_canreadpost'' is a capability.<br /> <br /> ==The existing system==<br /> <br /> Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.<br /> <br /> ==The new roles and capability system==<br /> <br /> The new system will allow authorized users to define an arbitrary number of roles. Each role can have a customizable set of capabilities in every context. A context can be the whole Moodle site, a course, or a module instance, e.g. quiz 5 in 'Introduction to Photography'. An authorized user will be able to assign an arbitrary number of roles to each user. Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by giving roles different 'priorities'. For example, to prevent a naughty student from posting, one could assign him a 'naughty student' role that does not allow him to post. This role should have a priority higher than that of a normal 'student' role. <br /> <br /> To facilitate exceptional cases in roles and capabilities, we can use exception rules. For example, we can specify a rule saying that all students are able to mark/read other students' assignment in this particular course. Note that such rules need to have a priority as well. The capability of a user, in any context is then resolved by finding the highest priority role/rule.<br /> <br /> ''A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the exisiting capabilities will be retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, which pretty much is what we have in 1.6. The whole process is automatic so there's nothing to worry about =). With no modifications, Moodle will operate exactly the same before and after the upgrade.''<br /> <br /> ==The plan==<br /> <br /> There are a few major things that need to be done. Here's a list (in no particular order):<br /> <br /> #Identify permissions required for site/course/each module.<br /> #Define the database structure for storing roles and capabilities.<br /> #Recode the whole of Moodle, including all modules to support the new structure. Instead of using &lt;code&gt;isteacher()&lt;/code&gt; or &lt;code&gt;isstudent()&lt;/code&gt; we should be using &lt;code&gt;has_capability($capability, $instanceid)&lt;/code&gt; etc. A new API for handling roles and capabilities will be implemented (accesslib.php).<br /> #Add storage of capabilities for each module. Can be done either in a file, e.g. db/capability.xml, or as a sql file that gets installed to a central db whenever this module is installed. Either way, what do we do when we need to upgrade these capabilities? Some capabilities might need refining/splitting later on. How do we control the 'version' of a capability?<br /> #Consider interface issues, especially how to manage conflicting role/exception rules.<br /> #Upon logging in, we should use a cache to store capability, down to module level. How should that be structured?<br /> #Consider the impact on backup/restore.<br /> #Upgrade path for current users. The user information in table user_coursecreators, user_admins, user_teachers, and user_students will most likely be migrated to the new roles and capabilities tables. The users will most likely be assigned default roles that comes with default capabilities (e.g. teachers, admins, students, etc). The old tables themselves could possibly be dropped at the end of the upgrade.<br /> <br /> ==Capabilities==<br /> <br /> This is a comprehensive list of capabilities, well, in the making. It is important that capability names are unique. Please edit. Should we distinguish canedit and candelete?<br /> <br /> What about a canview capability? Like for choice, where a person is allowed to see the choice question but not participate in it? --[[User:N Hansen|N Hansen]] 19:29, 16 May 2006 (WST)<br /> <br /> Certainly need a canview or cansee capability for parents as linked to their child's data/contributions.<br /> <br /> Do we need to add canview and cansearch logs at site/course/user/group level?<br /> <br /> I could use a canview at a course level, if I understand what that means exactly.--[[User:N Hansen|N Hansen]] 19:43, 12 June 2006 (WST)<br /> <br /> <br /> <br /> ===Core-level Capabilities===<br /> <br /> Moodle core capabilitie names start with 'moodle/'. The capabilities for the Moodle core are defined in lib/db/access.php<br /> Do we still keep student view? What is a student view?<br /> <br /> #moodle/site:config - applicialbe in admin/index.php and config.php (might break down later)<br /> #moodle/course:create - create courses<br /> #moodle/course:view - possibly a capability used for checking student role<br /> #moodle/course:viewparticipants - allows a user to view participant list<br /> #moodle/course:update - updates a course, i.e. adding/removing/editting activities <br /> #moodle/course:viewscales - view scales (i.e. in a help window?)<br /> #moodle/course:managescales - add, delete, edit scales, move scales up and down<br /> #moodle/course:managegroups - managing groups, add, delete, add user in etc<br /> <br /> ===Module-level Capabilities===<br /> The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.<br /> <br /> The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The module capabilities are defined in mod/mod_name/db/access.php.<br /> <br /> #Assignment<br /> ##mod/assignment:read - reading the assignment description<br /> ##mod/assignment:grade - grading, viewing of list of submitted assignments<br /> #Chat<br /> ##mod/chat:chat - allows a user to participate in this chat<br /> ##mod/chat:readlog - allows a user to read past chat session logs<br /> ##mod/chat:deletelog - allows a user to delete past chat logs<br /> #Choice<br /> ##mod/choice:choose - make a choice<br /> ##mod/choice:readresponses - read all responses<br /> ##mod/choice:deleteresponses - deletes all responses<br /> ##mod/choice:downloadresponses - download responses<br /> #Database<br /> ##mod/data:readentry - reads other people's entry<br /> ##mod/data:writeentry - add / edit and delete (own) entries<br /> ##mod/data:managetemplates - add, delete, edit fields and templates<br /> ##mod/data:manageentries - edit/delete all entry <br /> ##mod/data:comment - comment<br /> ##mod/data:managecomments - edit/delete all comments<br /> ##mod/data:rate - rate an entry<br /> ##mod/data:approve - approves an entry<br /> ##mod/data:uploadentries - batch upload of entries<br /> #Exercise<br /> ##mod/exercise:assess<br /> #Forum<br /> ##mod/forum:viewforum<br /> ##mod/forum:viewdiscussion<br /> ##mod/forum:viewdiscussionsfromallgroups<br /> ##mod/forum:startdiscussion<br /> ##mod/forum:replypost<br /> ##mod/forum:managediscussions<br /> ##mod/forum:viewrating<br /> ##mod/forum:rate<br /> #Glossary<br /> ##mod/glossary:read - view entries<br /> ##mod/glossary:write - add entries<br /> ##mod/glossary:manageentries - add, edit, delete entries<br /> ##mod/glossary:managecategories - create, delete, edit categories<br /> ##mod/glossary:comment - comment on an entry<br /> ##mod/glossary:managecomments - edit, delete comments<br /> ##mod/glossary:import - import glossaries<br /> ##mod/glossary:export - export glossaries<br /> ##mod/glossary:approve - approve glossaries<br /> ##mod/glossary:rate - rates glossary<br /> ##mod/glossary:readrate - view rating?<br /> #Hotpot<br /> #Label<br /> #Lams<br /> #Lesson<br /> #Quiz<br /> #Resource<br /> #Scorm<br /> #Survey<br /> ##mod/survey:download - downloads survery result<br /> ##mod/survey:participate - participate/ do survey<br /> ##mod/survey:readresponses - read all user's responese<br /> #Wiki<br /> #Workshop<br /> <br /> ==OU Desired Capabilities==<br /> <br /> We will use this page to detail the specific capabilities needed to create the roles for the OU. Each capability has three parts:<br /> <br /> # the name itself which can be anything and should be simple and short<br /> # the name of the module it belongs to (&quot;moodle&quot;, &quot;blog&quot;, &quot;course&quot;, &quot;forum&quot; etc)<br /> # the name of the &quot;class&quot; it belongs to, currently &quot;read&quot; or &quot;write&quot;. We can change <br /> this in future if we can work out a sensible scheme. This is purely used for the <br /> GUI to &quot;clump&quot; similar capabilties together<br /> <br /> I would recommend we create a table for each module with the name, module and class of the capability<br /> <br /> ==Moodle Site==<br /> <br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Create Catagory&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;View Courses&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add User&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move course to another category&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Make course visible to students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;new features? Site wide subscription default/setting&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;optional/forced etc&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;recommended default optional for all OU forums&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Site&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;used to ban individuals from Moodle?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Course - home page ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add Blocks&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;On/Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT &amp; Staff = Off, Admins = On&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add/View users ALs/Staff/Students&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = Read (this should be managed through circe or the administrator). Admins = Write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Course settings&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course teams = Read, Staff = no access. Admins = write&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Move blocks?&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff = off, Admin = on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Delete resource/page/activity/block &lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;CT/Staff= off, Admin = on. As we have no recovery process would it be best to prevent course teams from deleting resource pages &amp; other items on the home page?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;hide items&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, staff=off, admin=on&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add resource&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which resource types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add activity&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which activity types are listed per course/site&lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;upload calendar (OU feature?)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write. CTs should not be able to upload a calendar (admin will add this &amp; need to ensure the CT don't overwrite it with an alternative) &lt;/i&gt;&lt;/td&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit calendar&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=write, Staff=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;admin functions, e.g. back up, restore, import&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Ct=read, admin=write &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;edit groups&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admins = write CT/Moderators=on staff=read?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Access course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Course - resource page (OU version) ==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add authid&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Read/Write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Admin=Write, CT=Read&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;add placeholder&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course (resource page)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT=Off&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;Add RSS feed&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, ct=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Course resource page&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/noaccess&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;use to restrict access to pages by role?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Forum==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;move discussion to (archive/move feature)&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL=off?&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;update this forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=write, CT/Moderator=off? it would be good to break this down further and or premote some defaults for use. e.g subscription I think there should be a server wide default of optional for all OU forums which can't be oevrriden at the course level.&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;delete message/thread&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off? some course teams won't want students/als to be able to delete their own posts&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;split&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;admin=on, CT/Moderator=on AL/student=off &lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;post to forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;access forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;read/write/no access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;attach file to message&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;Forum&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;on/off access&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> &lt;/table&gt;<br /> <br /> ==Blog==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Quiz==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Wiki==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Resources==<br /> &lt;table width=60% border=0&gt;<br /> &lt;tr bgcolor=#EEEEEE&gt;<br /> &lt;td&gt;&lt;b&gt;Name&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Module&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Class&lt;/b&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;b&gt;Comment&lt;/b&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;td&gt;&lt;i&gt;replace&lt;/i&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> ==Questions==<br /> I am adding question categories here because they seem to have been forgotten since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in bug 6118.<br /> <br /> ==Scenarios==<br /> <br /> This section is for brainstorming some example roles that we would like to support:<br /> <br /> ===Student===<br /> Has this one been missed?<br /> <br /> ===Site Designers===<br /> Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.<br /> <br /> ===Educational Authority Adviser===<br /> Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.<br /> <br /> ===Educational Inspector===<br /> Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.<br /> <br /> ===Second Marker / Moderator===<br /> A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.<br /> <br /> ===External Examiner===<br /> Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.<br /> <br /> ===Parent===<br /> A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.<br /> <br /> In Early Years (EY) and Key Stage 1 (KS1) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary.<br /> <br /> In Key stages 3 and 4 this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.<br /> <br /> In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments.<br /> <br /> Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.<br /> <br /> In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face. <br /> <br /> The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.<br /> <br /> In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.<br /> <br /> ===Manager===<br /> ''Please add text here...''<br /> <br /> ===Weekly Seminar Leader===<br /> ''In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus &quot;Allow Quiz Authoring Role&quot; or &quot;Allow Assignment Authoring Role&quot; at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.''<br /> <br /> ===Mentor/Mentee===<br /> ''Please add text here...''<br /> <br /> ===Community-Designed Rating Criteria===<br /> ''The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?''<br /> <br /> ===Visitor===<br /> <br /> This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant. <br /> <br /> ===Former Student===<br /> This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?<br /> <br /> ===Librarian===<br /> <br /> Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.<br /> <br /> ===Teacher===<br /> <br /> Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity. <br /> <br /> I think that what is needed is a simple heirarchy of permissions and levels of granularity.<br /> <br /> I would take issue with &quot;teachers should have read access to other teacher's courses unless explicitly prohibited.&quot; This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--[[User:N Hansen|N Hansen]] 19:54, 12 June 2006 (WST)<br /> <br /> ===Community Education Tutors/Trainers===<br /> Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.<br /> <br /> ===Secretary/Student Worker===<br /> <br /> We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.<br /> <br /> ===Teaching Assistant===<br /> <br /> Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker<br /> <br /> ===Admin - Catgory based===<br /> <br /> Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.<br /> <br /> ===PROCESS ROLES===<br /> <br /> organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:<br /> &lt;li&gt;1. Give a student the role of forum-moderator with edit and chunk-rights<br /> &lt;li&gt;2. Give students different roles &amp; rights in a Webquest design (and change these roles next week<br /> &lt;li&gt;3. Give students different resources, depending of their roles in a rolegame/simulation<br /> &lt;li&gt;4. Give a student the rights to create the section content of next week (and only that week..)<br /> &lt;li&gt;5. ..<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture] forum discussion<br /> <br /> [[Category:Developer]]<br /> [[Category:Future]]<br /> <br /> <br /> [[ru:Роли]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=UK_MoodleMoot_06_hackfest&diff=13073 2006-07-12T00:30:34Z

<p>Hatshepsut: /* 2 What next for the quiz module? */</p> <hr /> <div>Monday 24th July, 2006<br /> <br /> ''Welcommen zum Hackfest'' (OK - I've been watching too much WorldCup on TV). <br /> <br /> The first MoodleMoot hackfest is nearly upon us... and we don't have an agenda!<br /> <br /> This is an open source agenda for the hackfest. We'll have a day before the Moot to geek out on some code, maybe develop a feature or two, fix some bugs and generally make our favorite learning system a happier place. But I leave it up to you to tell me exactly what we should do. We have four or five rooms with internet connections, a few projectors, and I'll try to get pizza. <br /> <br /> Let's start by brainstorming some ideas here for a few days. If someone posts something you're interested in, put your name under it as a vote. The top votes become our central organizing ideas. For example<br /> <br /> ==1 Bug fixing==<br /> <br /> Let's spend a few hours and hunt down as many outstanding bugs in 1.6 as possible. Bounties for most bugs killed, trickiest bug killed, and most unusual bug killed.<br /> <br /> ''I'm Interested:''<br /> # Jason Cole<br /> # skodak<br /> # martin langhoff (auth &amp; enrolment specifically).<br /> # Martin Dougiamas<br /> # Juliette White (arriving late though!)<br /> <br /> (iarenaza) I won't be there, but here are a couple of bugs for Martin L., related to auth: #4648 and #5373. Very easy to fix :-)<br /> <br /> ==2 What next for the quiz module?==<br /> <br /> If any other quizzy people are there, we should have a talk about where we see the quiz module going.<br /> <br /> I/the OU have the following priorities:<br /> <br /> # Make question type plugins really plug-in-able. At the moment there are some limitations:<br /> #* All the lang strings are still in lang/en_utf8/quiz.php.<br /> #* qtype plugins cannot easily feed CSS and Javascript into the page.<br /> #* pluggable qtypes and pluggable inport/export filters don't play nicely together.<br /> # Write some new question types.<br /> # Make some improvements to existing question types.<br /> # Get RQP working again, so our in-house question engine can talk to Moodle.<br /> <br /> I'm not going to be there, but I think it would be helpful if you were to discuss ways in which the teacher's usage of the quiz module could be made more efficient, more in terms of grading than in creating quizzes (as there have already been a lot of improvements in that respect in 1.6). I've submitted a lot of bug reports about this already but personally efficiency would be more of a priority to me than new question types.--[[User:N Hansen|N Hansen]] 08:27, 12 July 2006 (WST)<br /> <br /> ''I'm Interested:''<br /> # Tim Hunt<br /> # Jamie Pratt<br /> <br /> ==Performance profiling==<br /> <br /> Pick a (memory|database) hog and put it on a diet. <br /> <br /> ''I'm interested''<br /> <br /> # martin langhoff<br /> <br /> (iarenaza) Once again, I won't be there, but here's an unfixed bug in 1.6.x and HEAD (was fixed in 1.5.x, but not applied to HEAD at the moment): bug #4591<br /> <br /> ==Hacking on the OLPC Board==<br /> <br /> MartinL will be bringing the OLPC board (if it is booting, and customs allows!) for people to have a play with it. If we have any Mozilla/XUL experts in the house, he will want to explore building a limited cached Moodle UI with it for offline work.<br /> <br /> '''Note:''' We will need some spare parts &amp; hardware to get the board going. I will bring a power supply, but a VGA monitor, USB mouse + keyboard, USB ext disk, USB hub, and open wifi (no ethernet on the board) will be needed. <br /> <br /> ''JC: We'll make sure you have the appropriate stuff. I need a USB disk anyway.''<br /> <br /> ''I'm interested:''<br /> <br /> # martin langhoff<br /> # Jason Cole<br /> <br /> ==How to save/retrieve a complete section from stock?==<br /> Now the sections become more and more accepted as the tasksets for a week, our teachers wish to have topic oriented stores (courses for the moment) as section stores and want to copy one/more sections form that task store to a clean course..<br /> <br /> ''(In the end we wish that students can select sections from the store to compose their own courses, until the teacher freezes their choice set and the learning game can begin.)''<br /> <br /> ''I'm interested:''<br /> # Ger Tielemans (I arrive a little later, so start with the bugs first, please :))<br /> # Jan Kater (same arrival=same message as Ger T.)<br /> <br /> ==How to reveale files outside a course without using datadir for course 1?==<br /> Can someone explain the right setup and use of the exception array: <br /> - we want to show a student (after login) only his own file from that store<br /> - we want to show a teacher/tutor only the files from the students in his course(s)<br /> <br /> ''I'm interested:''<br /> # Ger Tielemans<br /> # Jan Kater<br /> <br /> ==How to repair the last bug in the old bookmark option ?==<br /> We changed William's bookmark in a student only note-taking tool and (thanks Chardelle!) almost repaired the complete bookmark for 1.6. (and it can be accessed from My Page)<br /> Bug: Only when the user tries to sort the heder in the overview, the text of the headers disappear.<br /> Code clean-up: how to remove obsolete code and make the bookmark pages secure?<br /> (Wish for new code: categories are privat, so allow a student to delete a self created category)<br /> <br /> ''I'm interested:''<br /> Ger Tielemans<br /> <br /> ==How to insert a HTML-editor in old code block and make it secure ?==<br /> To make the set of student note-taking tools complete, I found old code to have a global private notebook.<br /> (I group this with bookmarks in the calender, so the student has: 1. privat time-related-notes in the calendar, 2. a button for the overview of the privat page-related-notes under the calendar and 3. a global privat notebook for other scribbles..) <br /> On this moment this piece of code has a flat text editor, would be nice to have HTML or even the new (Ajax?) miniWiki?) <br /> <br /> With the new &quot;View as student button&quot; check like if isstudent() {..show..} offers teachers and admins empty - only for real student - spots (so an error)<br /> <br /> ''I'm interested:''<br /> # Ger Tielemans<br /> # Jan Kater<br /> <br /> == Improve the way we integrate Rubrics in Moodle, like... ==<br /> http://docs.subjectivemetrics.com/User/cam/rubistar/rs_overview.html<br /> <br /> maybe with some flavors of...<br /> <br /> http://ipeer.apsc.ubc.ca/ipeer_site/<br /> <br /> ==Add your suggestion here ...==<br /> <br /> <br /> <br /> Go on, you know you want to.<br /> <br /> ==See also==<br /> * [http://moodlemoot.org/ http://moodlemoot.org/]<br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=UK_MoodleMoot_06_hackfest&diff=13072 2006-07-12T00:27:57Z

<p>Hatshepsut: /* 2 What next for the quiz module? */</p> <hr /> <div>Monday 24th July, 2006<br /> <br /> ''Welcommen zum Hackfest'' (OK - I've been watching too much WorldCup on TV). <br /> <br /> The first MoodleMoot hackfest is nearly upon us... and we don't have an agenda!<br /> <br /> This is an open source agenda for the hackfest. We'll have a day before the Moot to geek out on some code, maybe develop a feature or two, fix some bugs and generally make our favorite learning system a happier place. But I leave it up to you to tell me exactly what we should do. We have four or five rooms with internet connections, a few projectors, and I'll try to get pizza. <br /> <br /> Let's start by brainstorming some ideas here for a few days. If someone posts something you're interested in, put your name under it as a vote. The top votes become our central organizing ideas. For example<br /> <br /> ==1 Bug fixing==<br /> <br /> Let's spend a few hours and hunt down as many outstanding bugs in 1.6 as possible. Bounties for most bugs killed, trickiest bug killed, and most unusual bug killed.<br /> <br /> ''I'm Interested:''<br /> # Jason Cole<br /> # skodak<br /> # martin langhoff (auth &amp; enrolment specifically).<br /> # Martin Dougiamas<br /> # Juliette White (arriving late though!)<br /> <br /> (iarenaza) I won't be there, but here are a couple of bugs for Martin L., related to auth: #4648 and #5373. Very easy to fix :-)<br /> <br /> ==2 What next for the quiz module?==<br /> <br /> If any other quizzy people are there, we should have a talk about where we see the quiz module going.<br /> <br /> I/the OU have the following priorities:<br /> <br /> # Make question type plugins really plug-in-able. At the moment there are some limitations:<br /> #* All the lang strings are still in lang/en_utf8/quiz.php.<br /> #* qtype plugins cannot easily feed CSS and Javascript into the page.<br /> #* pluggable qtypes and pluggable inport/export filters don't play nicely together.<br /> # Write some new question types.<br /> # Make some improvements to existing question types.<br /> # Get RQP working again, so our in-house question engine can talk to Moodle.<br /> <br /> I'm not going to be there, but I think it would be helpful if you were to discuss ways in which the teacher's usage of the quiz module could be made more efficient. I've submitted a lot of bug reports about this already but personally efficiency would be more of a priority to me than new question types.--[[User:N Hansen|N Hansen]] 08:27, 12 July 2006 (WST)<br /> <br /> ''I'm Interested:''<br /> # Tim Hunt<br /> # Jamie Pratt<br /> <br /> ==Performance profiling==<br /> <br /> Pick a (memory|database) hog and put it on a diet. <br /> <br /> ''I'm interested''<br /> <br /> # martin langhoff<br /> <br /> (iarenaza) Once again, I won't be there, but here's an unfixed bug in 1.6.x and HEAD (was fixed in 1.5.x, but not applied to HEAD at the moment): bug #4591<br /> <br /> ==Hacking on the OLPC Board==<br /> <br /> MartinL will be bringing the OLPC board (if it is booting, and customs allows!) for people to have a play with it. If we have any Mozilla/XUL experts in the house, he will want to explore building a limited cached Moodle UI with it for offline work.<br /> <br /> '''Note:''' We will need some spare parts &amp; hardware to get the board going. I will bring a power supply, but a VGA monitor, USB mouse + keyboard, USB ext disk, USB hub, and open wifi (no ethernet on the board) will be needed. <br /> <br /> ''JC: We'll make sure you have the appropriate stuff. I need a USB disk anyway.''<br /> <br /> ''I'm interested:''<br /> <br /> # martin langhoff<br /> # Jason Cole<br /> <br /> ==How to save/retrieve a complete section from stock?==<br /> Now the sections become more and more accepted as the tasksets for a week, our teachers wish to have topic oriented stores (courses for the moment) as section stores and want to copy one/more sections form that task store to a clean course..<br /> <br /> ''(In the end we wish that students can select sections from the store to compose their own courses, until the teacher freezes their choice set and the learning game can begin.)''<br /> <br /> ''I'm interested:''<br /> # Ger Tielemans (I arrive a little later, so start with the bugs first, please :))<br /> # Jan Kater (same arrival=same message as Ger T.)<br /> <br /> ==How to reveale files outside a course without using datadir for course 1?==<br /> Can someone explain the right setup and use of the exception array: <br /> - we want to show a student (after login) only his own file from that store<br /> - we want to show a teacher/tutor only the files from the students in his course(s)<br /> <br /> ''I'm interested:''<br /> # Ger Tielemans<br /> # Jan Kater<br /> <br /> ==How to repair the last bug in the old bookmark option ?==<br /> We changed William's bookmark in a student only note-taking tool and (thanks Chardelle!) almost repaired the complete bookmark for 1.6. (and it can be accessed from My Page)<br /> Bug: Only when the user tries to sort the heder in the overview, the text of the headers disappear.<br /> Code clean-up: how to remove obsolete code and make the bookmark pages secure?<br /> (Wish for new code: categories are privat, so allow a student to delete a self created category)<br /> <br /> ''I'm interested:''<br /> Ger Tielemans<br /> <br /> ==How to insert a HTML-editor in old code block and make it secure ?==<br /> To make the set of student note-taking tools complete, I found old code to have a global private notebook.<br /> (I group this with bookmarks in the calender, so the student has: 1. privat time-related-notes in the calendar, 2. a button for the overview of the privat page-related-notes under the calendar and 3. a global privat notebook for other scribbles..) <br /> On this moment this piece of code has a flat text editor, would be nice to have HTML or even the new (Ajax?) miniWiki?) <br /> <br /> With the new &quot;View as student button&quot; check like if isstudent() {..show..} offers teachers and admins empty - only for real student - spots (so an error)<br /> <br /> ''I'm interested:''<br /> # Ger Tielemans<br /> # Jan Kater<br /> <br /> == Improve the way we integrate Rubrics in Moodle, like... ==<br /> http://docs.subjectivemetrics.com/User/cam/rubistar/rs_overview.html<br /> <br /> maybe with some flavors of...<br /> <br /> http://ipeer.apsc.ubc.ca/ipeer_site/<br /> <br /> ==Add your suggestion here ...==<br /> <br /> <br /> <br /> Go on, you know you want to.<br /> <br /> ==See also==<br /> * [http://moodlemoot.org/ http://moodlemoot.org/]<br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3344&diff=12736 2006-07-03T01:12:03Z

<p>Hatshepsut: </p> <hr /> <div>The contents of the event field are now defined in questionlib.php. Should that fact be added here?--[[User:N Hansen|N Hansen]] 09:12, 3 July 2006 (WST)</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12724 2006-07-02T12:21:06Z

<p>Hatshepsut: /* Releases */</p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayor. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6.<br /> <br /> It would be helpful if when someone creates and lists a new version here they state what version their new version is based on.--[[User:N Hansen|N Hansen]] 04:38, 2 July 2006 (WST) <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> <br /> '''AL v2.1(john)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006, based on the version of activity locking released by Stuart Meyor on October 19, 2005. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Johns Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them.[http://moodle.org/mod/forum/discuss.php?d=46863#220125 AL v2.1-M1.6]<br /> <br /> '''AL v2.1 for 1.6(chardelle)''' - link posted by Chardelle on 25 June 2006, 03:35 PM. This flavor has a hide future activity function and seems to be functioning on some Moodles but is being tweaked for others. See forum discussion: [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 Certificate 1.6 with Security discussion in Activity Module forum].The link for the external website is: [http://proemployees.com/ActivityLockingWithHide-1.6.zip AL v2.1 for 1.6(chardelle)].<br /> <br /> [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.<br /> <br /> Locking a topic is an all-or-nothing proposition. If you lock at topic, you cannot have individual conditions on locking of the items inside that topic. It would be nice if this were not the case.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Activity_Locking&diff=12720 2006-07-02T05:21:28Z

<p>Hatshepsut: /* AL Branch 3.s for Moodle 1.6 (Stuart Mayor) */</p> <hr /> <div>=Overview=<br /> This page is an attempt to consolidate and explain the available activity locking (AL) code that is present for Moodle 1.5.x and 1.6.x. This page will hopefully help explain all the available versions and their respective features. Some of the reference here will overlap with the existing MoodleDoc page covering [[Conditional activities]]. <br /> <br /> Please be patient as this page is new and under development. See page comments for reference material.<br /> <br /> =Types of activity locking code=<br /> For the purpose of this MoodleDoc article: AL is any code that allows the user to make decisions on the next available resource or item the student will be able to use based on student events or quiz performance. There is some activity locking code that is very quick and dirty to simply lock future activities and then there is much more complex code based on the conditional activity though structure which attempts to progress the student through the course in a thought out progression based on activities and performance. Again we hope to clarify some of this here.<br /> <br /> ==AL Branch 1.0 (Bernard Boucher)==<br /> Bernard started all this with a hack to lock the certificate based on a quiz score in 2004. It was a great start! <br /> <br /> == AL Branch 2.1 for Moodle 1.6 (Stuart Meyor)==<br /> *This has been virtually a complete rewrite and as such there are areas of functionality the were available in older versions of AL that are not in this. <br /> <br /> * Conditional locking: Lock based on a user's performance in previous activities. You can also choose to unlock and activity if a user scores less than a certain grade.<br /> * Show activity completion: The checkbox that appears before each activity to show it have been done.<br /> * A variation on this also hides future activities, see AL Branch 2.1 for Moodle 1.6 (John Gschnaidner-Chardelle Busch) below.<br /> * Bernard Boucher reworked Stuart's version and on June 20, 2006 posted [http://206.167.134.155/bb/authoring1/activity_locking_v2_for_16_20060620.zip '''Activity_locking_v2_for_16_20060620.zip'''] on [http://moodle.org/mod/forum/user.php?id=1323&amp;course=5 Activity Locking v3 or v2 for testing only]. The link is outside moodle.org and the link was not working on June 29, 2006.<br /> <br /> ===Installation for 2.1 for Moodle 1.6(Stuart Meyor)===<br /> '''activitylocking20051201.zip''' the initial version<br /> <br /> * Firstly, you need the stable build of Moodle 1.6. This version of AL might work on earlier releases but I didn't write it with them in mind and I certainly can't support them.<br /> Next, you need to modify one table in the database and add a new one (I use phpmyadmin for this). <br /> <br /> * The table you need to modify is mdl_course_modules and you need to add the following fields:<br /> completedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '0'<br /> completedscore VARCHAR(255) NOT NULL<br /> completedstyle VARCHAR(255) NOT NULL<br /> lockedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> lockedstyle VARCHAR(255) NOT NULL DEFAULT 'locked'<br /> lockedvisible TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> delay INT(10) UNSIGNED NOT NULL DEFAULT '0'<br /> <br /> * The table you need to create is as follows:<br /> CREATE TABLE `mdl_course_locks` (<br /> `id` int(10) unsigned NOT NULL auto_increment,<br /> `courseid` int(10) unsigned NOT NULL default '0',<br /> `locktype` varchar(10) NOT NULL default '',<br /> `targetid` int(10) unsigned NOT NULL default '0',<br /> `locks` longtext NOT NULL,<br /> PRIMARY KEY (`id`)<br /> ) TYPE=MyISAM COMMENT='Contains locks for sections and modules';<br /> * Lastly, you need to copy the following files from the zip file:<br /> lib/moodlelib.php to moodle/lib/moodlelib.php<br /> lib/locklib.php to moodle/lib/locklib.php<br /> course/lib.php to moodle/course/lib.php<br /> course/lock.php to moodle/course/lock.php<br /> course/mod.php to moodle/course/mod.php<br /> course/settings.html to moodle/course/settings.html<br /> pix/t/open.gif to moodle/pix/t/open.gif<br /> pix/t/closed.gif to moodle/pix/t/closed.gif<br /> lang/en/lock.php to moodle/lang/en/lock.php<br /> <br /> ==AL Branch 2.2 for Moodle 1.6 (John Gschnaidner-Chardelle Busch and others)==<br /> John's versionincludes the settings tab--making it possible to set the hide/visible options, as well as the completion (a checkmark in front of a resource/activity) options, says Chardelle. <br /> * A variation on Stuart Mayor's 2.1, it hides topics dependent upon conditions set on specific activities/resources '''ALV2_1_debug.ZIP''' (John). Had bug which Benard tweaked out.<br /> * A build of Stuarts Mayor's 2.1 it locks and/or hides specific activities depending upon conditions set on specific activities/resources. Was posted by Chardelle in [http://proemployees.com/ActivityLockingWithHide-1.6.zip '''ActivityLockingWithHide-1.6.zip''']. Probably same as above. Had bug which Benard tweaked out.<br /> * A tweak by Bernard Boucher on June 27, 2006 was posted [http://moodle.org/mod/forum/discuss.php?d=35488&amp;parent=222516 moodle/lib/locklib.php file] and called '''locklib.zip''' seems to fix known bug in both the above downloads.<br /> <br /> ==AL Branch 3.s for Moodle 1.6 (Stuart Meyor)==<br /> Similar to the 2.x versions. Major difference is that a question to the student unlocks activities. Being actively developed and tested.<br /> <br /> ==CA Branch 1.0 for Moodle 1.5.2 (David Delgado)==<br /> Details and discussed in the thread &quot;NEW research on CONDITIONAL ACTIVITIES in Moodle&quot;<br /> <br /> = Table of Versions, to be completed... =<br /> {| border=&quot;3&quot; padding=&quot;4&quot;<br /> |+ Activity Locking updated 29 June 2006 10:00 AM EST<br /> ! -Version- <br /> ! Moodle version<br /> ! Who<br /> ! Status<br /> ! MySql Install<br /> ! Docs<br /> ! Comments <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Bug <br /> ! Bug <br /> |-----<br /> | AL 3.0<br /> | 1.5.2<br /> | Stuart Mayor<br /> | not finished<br /> |<br /> |[http://moodle.org/mod/forum/discuss.php?d=46863]<br /> | <br /> | AL<br /> | A/R dep on questions<br /> |-----<br /> | AL 2.3<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | <br /> | AL<br /> | A/R/T dep on A/Rs<br /> |-----<br /> | AL 2.2<br /> | 1.6<br /> | Gschnaidner, Mayor, Busch, Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488#220946]<br /> | almost<br /> | AL<br /> | A/R dep on A/Rs<br /> | +Hide<br /> |<br /> | bug fix<br /> |-----<br /> | AL 2.1<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | base<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | see above<br /> | AL<br /> |-----<br /> | C A 1.0<br /> | 1.5.2<br /> | David Delgado Borja Rubio Reyes<br /> | <br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=36697]<br /> |<br /> | AL<br /> |}<br /> <br /> =General installation instructions DRAFT=<br /> Installing AL on a localhost (desktop) machine was not difficult! Some months ago I must have downloaded and connected phpAdministration and that came in handy for step 6. I just did a conversion and it took me less than 30 minutes (actually I think the AL part was done in 3 minutes ) because I wanted to install the latest version of Moodle 1.6 and then zipped my entire Moodle16 file structure before I attempted the AL installation.<br /> *1. Perform any backups you think are necessary (I zipped everything in my localhost path).<br /> *2. Select the zip file flavor of AL you want and download it (I used Chardelle's zip plus Bernards tweak found in 2.2 above)<br /> *3. Unzip it to a non Moodle place. (Like to keep the folder structures option)<br /> *4. Locate the MySQL.sql file so you can find it again.<br /> *5. In Moodle as admin, go to Administration, Configuration and turn on Maintence Mode.<br /> *6. Go to Administration, Database. In the home query window, on the left, click on moodle (mine says Moodle16 and has a bunch of mdl_ listings under it). <br /> *7. Best: Click on the SQL tab. In the location of the text file, browse to the file in #4, then click go.<br /> *7. Alternative: use the MySQL document and make or changes in <br /> *8. Leave Moodle, shut that browser window.<br /> *9. Now you need to move the files in the folders located in #3 to your Moodle file structure. (See my tip below). In your non moodle area you have unpack the file to a folder called ActivityLockingWithHide. It has a folder called Moodle in it, with sub folders under it, for example ActivityLockingWithHide\Moodle\Course. You should copy ever file from there to your local host file structure in the same spot. (Mine is Moodle16\Moodle\Course ).<br /> *10. Go back into Moodle, log in as Admin, go to Administration. Moodle will adjust itself.<br /> *11 Check in Administration, Configuration, Maintence to make sure it is disabled. <br /> *12. You are done, check out a lesson with weeks or topics, go to lesson settings and notice the new tabs.<br /> * TIP? There is probably a slicker way but after I unzipped the file in #3, I went down a level and zipped the Moodle folder. Then I unpacked the files to Moodle16\, told the unzip program to keep the folder structure and overwrite existing files. <br /> <br /> <br /> <br /> <br /> <br /> <br /> =See Also=<br /> *[[Adding_activity_locks]] will give the reader an idea of what one of the flavors of Activity Locking looks like for a student and teacher setting it up. <br /> <br /> Please visit the Moodle Forum for more information concerning Activity Locking and Conditional Activities-<br /> <br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> * http://moodle.org/mod/forum/view.php?id=4295<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> There is a very specialized-limited type of activity locking under a lesson (activity) setting called dependency in 1.6. See: *https://docs.moodle.org/en/Adding/editing_a_lesson#Dependent_on . <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Activity_Locking&diff=12719 2006-07-02T05:18:36Z

<p>Hatshepsut: /* AL Branch 2.1 for Moodle 1.6 (Stuart Meyor) */</p> <hr /> <div>=Overview=<br /> This page is an attempt to consolidate and explain the available activity locking (AL) code that is present for Moodle 1.5.x and 1.6.x. This page will hopefully help explain all the available versions and their respective features. Some of the reference here will overlap with the existing MoodleDoc page covering [[Conditional activities]]. <br /> <br /> Please be patient as this page is new and under development. See page comments for reference material.<br /> <br /> =Types of activity locking code=<br /> For the purpose of this MoodleDoc article: AL is any code that allows the user to make decisions on the next available resource or item the student will be able to use based on student events or quiz performance. There is some activity locking code that is very quick and dirty to simply lock future activities and then there is much more complex code based on the conditional activity though structure which attempts to progress the student through the course in a thought out progression based on activities and performance. Again we hope to clarify some of this here.<br /> <br /> ==AL Branch 1.0 (Bernard Boucher)==<br /> Bernard started all this with a hack to lock the certificate based on a quiz score in 2004. It was a great start! <br /> <br /> == AL Branch 2.1 for Moodle 1.6 (Stuart Meyor)==<br /> *This has been virtually a complete rewrite and as such there are areas of functionality the were available in older versions of AL that are not in this. <br /> <br /> * Conditional locking: Lock based on a user's performance in previous activities. You can also choose to unlock and activity if a user scores less than a certain grade.<br /> * Show activity completion: The checkbox that appears before each activity to show it have been done.<br /> * A variation on this also hides future activities, see AL Branch 2.1 for Moodle 1.6 (John Gschnaidner-Chardelle Busch) below.<br /> * Bernard Boucher reworked Stuart's version and on June 20, 2006 posted [http://206.167.134.155/bb/authoring1/activity_locking_v2_for_16_20060620.zip '''Activity_locking_v2_for_16_20060620.zip'''] on [http://moodle.org/mod/forum/user.php?id=1323&amp;course=5 Activity Locking v3 or v2 for testing only]. The link is outside moodle.org and the link was not working on June 29, 2006.<br /> <br /> ===Installation for 2.1 for Moodle 1.6(Stuart Meyor)===<br /> '''activitylocking20051201.zip''' the initial version<br /> <br /> * Firstly, you need the stable build of Moodle 1.6. This version of AL might work on earlier releases but I didn't write it with them in mind and I certainly can't support them.<br /> Next, you need to modify one table in the database and add a new one (I use phpmyadmin for this). <br /> <br /> * The table you need to modify is mdl_course_modules and you need to add the following fields:<br /> completedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '0'<br /> completedscore VARCHAR(255) NOT NULL<br /> completedstyle VARCHAR(255) NOT NULL<br /> lockedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> lockedstyle VARCHAR(255) NOT NULL DEFAULT 'locked'<br /> lockedvisible TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> delay INT(10) UNSIGNED NOT NULL DEFAULT '0'<br /> <br /> * The table you need to create is as follows:<br /> CREATE TABLE `mdl_course_locks` (<br /> `id` int(10) unsigned NOT NULL auto_increment,<br /> `courseid` int(10) unsigned NOT NULL default '0',<br /> `locktype` varchar(10) NOT NULL default '',<br /> `targetid` int(10) unsigned NOT NULL default '0',<br /> `locks` longtext NOT NULL,<br /> PRIMARY KEY (`id`)<br /> ) TYPE=MyISAM COMMENT='Contains locks for sections and modules';<br /> * Lastly, you need to copy the following files from the zip file:<br /> lib/moodlelib.php to moodle/lib/moodlelib.php<br /> lib/locklib.php to moodle/lib/locklib.php<br /> course/lib.php to moodle/course/lib.php<br /> course/lock.php to moodle/course/lock.php<br /> course/mod.php to moodle/course/mod.php<br /> course/settings.html to moodle/course/settings.html<br /> pix/t/open.gif to moodle/pix/t/open.gif<br /> pix/t/closed.gif to moodle/pix/t/closed.gif<br /> lang/en/lock.php to moodle/lang/en/lock.php<br /> <br /> ==AL Branch 2.2 for Moodle 1.6 (John Gschnaidner-Chardelle Busch and others)==<br /> John's versionincludes the settings tab--making it possible to set the hide/visible options, as well as the completion (a checkmark in front of a resource/activity) options, says Chardelle. <br /> * A variation on Stuart Mayor's 2.1, it hides topics dependent upon conditions set on specific activities/resources '''ALV2_1_debug.ZIP''' (John). Had bug which Benard tweaked out.<br /> * A build of Stuarts Mayor's 2.1 it locks and/or hides specific activities depending upon conditions set on specific activities/resources. Was posted by Chardelle in [http://proemployees.com/ActivityLockingWithHide-1.6.zip '''ActivityLockingWithHide-1.6.zip''']. Probably same as above. Had bug which Benard tweaked out.<br /> * A tweak by Bernard Boucher on June 27, 2006 was posted [http://moodle.org/mod/forum/discuss.php?d=35488&amp;parent=222516 moodle/lib/locklib.php file] and called '''locklib.zip''' seems to fix known bug in both the above downloads.<br /> <br /> ==AL Branch 3.s for Moodle 1.6 (Stuart Mayor)==<br /> Similar to the 2.x versions. Major difference is that a question to the student unlocks activities. Being actively developed and tested.<br /> <br /> ==CA Branch 1.0 for Moodle 1.5.2 (David Delgado)==<br /> Details and discussed in the thread &quot;NEW research on CONDITIONAL ACTIVITIES in Moodle&quot;<br /> <br /> = Table of Versions, to be completed... =<br /> {| border=&quot;3&quot; padding=&quot;4&quot;<br /> |+ Activity Locking updated 29 June 2006 10:00 AM EST<br /> ! -Version- <br /> ! Moodle version<br /> ! Who<br /> ! Status<br /> ! MySql Install<br /> ! Docs<br /> ! Comments <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Bug <br /> ! Bug <br /> |-----<br /> | AL 3.0<br /> | 1.5.2<br /> | Stuart Mayor<br /> | not finished<br /> |<br /> |[http://moodle.org/mod/forum/discuss.php?d=46863]<br /> | <br /> | AL<br /> | A/R dep on questions<br /> |-----<br /> | AL 2.3<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | <br /> | AL<br /> | A/R/T dep on A/Rs<br /> |-----<br /> | AL 2.2<br /> | 1.6<br /> | Gschnaidner, Mayor, Busch, Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488#220946]<br /> | almost<br /> | AL<br /> | A/R dep on A/Rs<br /> | +Hide<br /> |<br /> | bug fix<br /> |-----<br /> | AL 2.1<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | base<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | see above<br /> | AL<br /> |-----<br /> | C A 1.0<br /> | 1.5.2<br /> | David Delgado Borja Rubio Reyes<br /> | <br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=36697]<br /> |<br /> | AL<br /> |}<br /> <br /> =General installation instructions DRAFT=<br /> Installing AL on a localhost (desktop) machine was not difficult! Some months ago I must have downloaded and connected phpAdministration and that came in handy for step 6. I just did a conversion and it took me less than 30 minutes (actually I think the AL part was done in 3 minutes ) because I wanted to install the latest version of Moodle 1.6 and then zipped my entire Moodle16 file structure before I attempted the AL installation.<br /> *1. Perform any backups you think are necessary (I zipped everything in my localhost path).<br /> *2. Select the zip file flavor of AL you want and download it (I used Chardelle's zip plus Bernards tweak found in 2.2 above)<br /> *3. Unzip it to a non Moodle place. (Like to keep the folder structures option)<br /> *4. Locate the MySQL.sql file so you can find it again.<br /> *5. In Moodle as admin, go to Administration, Configuration and turn on Maintence Mode.<br /> *6. Go to Administration, Database. In the home query window, on the left, click on moodle (mine says Moodle16 and has a bunch of mdl_ listings under it). <br /> *7. Best: Click on the SQL tab. In the location of the text file, browse to the file in #4, then click go.<br /> *7. Alternative: use the MySQL document and make or changes in <br /> *8. Leave Moodle, shut that browser window.<br /> *9. Now you need to move the files in the folders located in #3 to your Moodle file structure. (See my tip below). In your non moodle area you have unpack the file to a folder called ActivityLockingWithHide. It has a folder called Moodle in it, with sub folders under it, for example ActivityLockingWithHide\Moodle\Course. You should copy ever file from there to your local host file structure in the same spot. (Mine is Moodle16\Moodle\Course ).<br /> *10. Go back into Moodle, log in as Admin, go to Administration. Moodle will adjust itself.<br /> *11 Check in Administration, Configuration, Maintence to make sure it is disabled. <br /> *12. You are done, check out a lesson with weeks or topics, go to lesson settings and notice the new tabs.<br /> * TIP? There is probably a slicker way but after I unzipped the file in #3, I went down a level and zipped the Moodle folder. Then I unpacked the files to Moodle16\, told the unzip program to keep the folder structure and overwrite existing files. <br /> <br /> <br /> <br /> <br /> <br /> <br /> =See Also=<br /> *[[Adding_activity_locks]] will give the reader an idea of what one of the flavors of Activity Locking looks like for a student and teacher setting it up. <br /> <br /> Please visit the Moodle Forum for more information concerning Activity Locking and Conditional Activities-<br /> <br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> * http://moodle.org/mod/forum/view.php?id=4295<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> There is a very specialized-limited type of activity locking under a lesson (activity) setting called dependency in 1.6. See: *https://docs.moodle.org/en/Adding/editing_a_lesson#Dependent_on . <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Activity_Locking&diff=12718 2006-07-02T05:17:59Z

<p>Hatshepsut: /* AL Branch 2.1 for Moodle 1.6 (Stuart Mayor) */</p> <hr /> <div>=Overview=<br /> This page is an attempt to consolidate and explain the available activity locking (AL) code that is present for Moodle 1.5.x and 1.6.x. This page will hopefully help explain all the available versions and their respective features. Some of the reference here will overlap with the existing MoodleDoc page covering [[Conditional activities]]. <br /> <br /> Please be patient as this page is new and under development. See page comments for reference material.<br /> <br /> =Types of activity locking code=<br /> For the purpose of this MoodleDoc article: AL is any code that allows the user to make decisions on the next available resource or item the student will be able to use based on student events or quiz performance. There is some activity locking code that is very quick and dirty to simply lock future activities and then there is much more complex code based on the conditional activity though structure which attempts to progress the student through the course in a thought out progression based on activities and performance. Again we hope to clarify some of this here.<br /> <br /> ==AL Branch 1.0 (Bernard Boucher)==<br /> Bernard started all this with a hack to lock the certificate based on a quiz score in 2004. It was a great start! <br /> <br /> == AL Branch 2.1 for Moodle 1.6 (Stuart Meyor)==<br /> *This has been virtually a complete rewrite and as such there are areas of functionality the were available in older versions of AL that are not in this. <br /> <br /> * Conditional locking: Lock based on a user's performance in previous activities. You can also choose to unlock and activity if a user scores less than a certain grade.<br /> * Show activity completion: The checkbox that appears before each activity to show it have been done.<br /> * A variation on this also hides future activities, see AL Branch 2.1 for Moodle 1.6 (John Gschnaidner-Chardelle Busch) below.<br /> * Bernard Boucher reworked Stuart's version and on June 20, 2006 posted [http://206.167.134.155/bb/authoring1/activity_locking_v2_for_16_20060620.zip '''Activity_locking_v2_for_16_20060620.zip'''] on [http://moodle.org/mod/forum/user.php?id=1323&amp;course=5 Activity Locking v3 or v2 for testing only]. The link is outside moodle.org and the link was not working on June 29, 2006. Bernard Boucher's version is not based on Stuart's version 3 anyway.--[[User:N Hansen|N Hansen]] 13:17, 2 July 2006 (WST)<br /> <br /> ===Installation for 2.1 for Moodle 1.6(Stuart Meyor)===<br /> '''activitylocking20051201.zip''' the initial version<br /> <br /> * Firstly, you need the stable build of Moodle 1.6. This version of AL might work on earlier releases but I didn't write it with them in mind and I certainly can't support them.<br /> Next, you need to modify one table in the database and add a new one (I use phpmyadmin for this). <br /> <br /> * The table you need to modify is mdl_course_modules and you need to add the following fields:<br /> completedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '0'<br /> completedscore VARCHAR(255) NOT NULL<br /> completedstyle VARCHAR(255) NOT NULL<br /> lockedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> lockedstyle VARCHAR(255) NOT NULL DEFAULT 'locked'<br /> lockedvisible TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> delay INT(10) UNSIGNED NOT NULL DEFAULT '0'<br /> <br /> * The table you need to create is as follows:<br /> CREATE TABLE `mdl_course_locks` (<br /> `id` int(10) unsigned NOT NULL auto_increment,<br /> `courseid` int(10) unsigned NOT NULL default '0',<br /> `locktype` varchar(10) NOT NULL default '',<br /> `targetid` int(10) unsigned NOT NULL default '0',<br /> `locks` longtext NOT NULL,<br /> PRIMARY KEY (`id`)<br /> ) TYPE=MyISAM COMMENT='Contains locks for sections and modules';<br /> * Lastly, you need to copy the following files from the zip file:<br /> lib/moodlelib.php to moodle/lib/moodlelib.php<br /> lib/locklib.php to moodle/lib/locklib.php<br /> course/lib.php to moodle/course/lib.php<br /> course/lock.php to moodle/course/lock.php<br /> course/mod.php to moodle/course/mod.php<br /> course/settings.html to moodle/course/settings.html<br /> pix/t/open.gif to moodle/pix/t/open.gif<br /> pix/t/closed.gif to moodle/pix/t/closed.gif<br /> lang/en/lock.php to moodle/lang/en/lock.php<br /> <br /> ==AL Branch 2.2 for Moodle 1.6 (John Gschnaidner-Chardelle Busch and others)==<br /> John's versionincludes the settings tab--making it possible to set the hide/visible options, as well as the completion (a checkmark in front of a resource/activity) options, says Chardelle. <br /> * A variation on Stuart Mayor's 2.1, it hides topics dependent upon conditions set on specific activities/resources '''ALV2_1_debug.ZIP''' (John). Had bug which Benard tweaked out.<br /> * A build of Stuarts Mayor's 2.1 it locks and/or hides specific activities depending upon conditions set on specific activities/resources. Was posted by Chardelle in [http://proemployees.com/ActivityLockingWithHide-1.6.zip '''ActivityLockingWithHide-1.6.zip''']. Probably same as above. Had bug which Benard tweaked out.<br /> * A tweak by Bernard Boucher on June 27, 2006 was posted [http://moodle.org/mod/forum/discuss.php?d=35488&amp;parent=222516 moodle/lib/locklib.php file] and called '''locklib.zip''' seems to fix known bug in both the above downloads.<br /> <br /> ==AL Branch 3.s for Moodle 1.6 (Stuart Mayor)==<br /> Similar to the 2.x versions. Major difference is that a question to the student unlocks activities. Being actively developed and tested.<br /> <br /> ==CA Branch 1.0 for Moodle 1.5.2 (David Delgado)==<br /> Details and discussed in the thread &quot;NEW research on CONDITIONAL ACTIVITIES in Moodle&quot;<br /> <br /> = Table of Versions, to be completed... =<br /> {| border=&quot;3&quot; padding=&quot;4&quot;<br /> |+ Activity Locking updated 29 June 2006 10:00 AM EST<br /> ! -Version- <br /> ! Moodle version<br /> ! Who<br /> ! Status<br /> ! MySql Install<br /> ! Docs<br /> ! Comments <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Bug <br /> ! Bug <br /> |-----<br /> | AL 3.0<br /> | 1.5.2<br /> | Stuart Mayor<br /> | not finished<br /> |<br /> |[http://moodle.org/mod/forum/discuss.php?d=46863]<br /> | <br /> | AL<br /> | A/R dep on questions<br /> |-----<br /> | AL 2.3<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | <br /> | AL<br /> | A/R/T dep on A/Rs<br /> |-----<br /> | AL 2.2<br /> | 1.6<br /> | Gschnaidner, Mayor, Busch, Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488#220946]<br /> | almost<br /> | AL<br /> | A/R dep on A/Rs<br /> | +Hide<br /> |<br /> | bug fix<br /> |-----<br /> | AL 2.1<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | base<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | see above<br /> | AL<br /> |-----<br /> | C A 1.0<br /> | 1.5.2<br /> | David Delgado Borja Rubio Reyes<br /> | <br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=36697]<br /> |<br /> | AL<br /> |}<br /> <br /> =General installation instructions DRAFT=<br /> Installing AL on a localhost (desktop) machine was not difficult! Some months ago I must have downloaded and connected phpAdministration and that came in handy for step 6. I just did a conversion and it took me less than 30 minutes (actually I think the AL part was done in 3 minutes ) because I wanted to install the latest version of Moodle 1.6 and then zipped my entire Moodle16 file structure before I attempted the AL installation.<br /> *1. Perform any backups you think are necessary (I zipped everything in my localhost path).<br /> *2. Select the zip file flavor of AL you want and download it (I used Chardelle's zip plus Bernards tweak found in 2.2 above)<br /> *3. Unzip it to a non Moodle place. (Like to keep the folder structures option)<br /> *4. Locate the MySQL.sql file so you can find it again.<br /> *5. In Moodle as admin, go to Administration, Configuration and turn on Maintence Mode.<br /> *6. Go to Administration, Database. In the home query window, on the left, click on moodle (mine says Moodle16 and has a bunch of mdl_ listings under it). <br /> *7. Best: Click on the SQL tab. In the location of the text file, browse to the file in #4, then click go.<br /> *7. Alternative: use the MySQL document and make or changes in <br /> *8. Leave Moodle, shut that browser window.<br /> *9. Now you need to move the files in the folders located in #3 to your Moodle file structure. (See my tip below). In your non moodle area you have unpack the file to a folder called ActivityLockingWithHide. It has a folder called Moodle in it, with sub folders under it, for example ActivityLockingWithHide\Moodle\Course. You should copy ever file from there to your local host file structure in the same spot. (Mine is Moodle16\Moodle\Course ).<br /> *10. Go back into Moodle, log in as Admin, go to Administration. Moodle will adjust itself.<br /> *11 Check in Administration, Configuration, Maintence to make sure it is disabled. <br /> *12. You are done, check out a lesson with weeks or topics, go to lesson settings and notice the new tabs.<br /> * TIP? There is probably a slicker way but after I unzipped the file in #3, I went down a level and zipped the Moodle folder. Then I unpacked the files to Moodle16\, told the unzip program to keep the folder structure and overwrite existing files. <br /> <br /> <br /> <br /> <br /> <br /> <br /> =See Also=<br /> *[[Adding_activity_locks]] will give the reader an idea of what one of the flavors of Activity Locking looks like for a student and teacher setting it up. <br /> <br /> Please visit the Moodle Forum for more information concerning Activity Locking and Conditional Activities-<br /> <br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> * http://moodle.org/mod/forum/view.php?id=4295<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> There is a very specialized-limited type of activity locking under a lesson (activity) setting called dependency in 1.6. See: *https://docs.moodle.org/en/Adding/editing_a_lesson#Dependent_on . <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Activity_Locking&diff=12717 2006-07-02T05:17:44Z

<p>Hatshepsut: /* Installation for 2.1 for Moodle 1.6(Stuart Mayor) */</p> <hr /> <div>=Overview=<br /> This page is an attempt to consolidate and explain the available activity locking (AL) code that is present for Moodle 1.5.x and 1.6.x. This page will hopefully help explain all the available versions and their respective features. Some of the reference here will overlap with the existing MoodleDoc page covering [[Conditional activities]]. <br /> <br /> Please be patient as this page is new and under development. See page comments for reference material.<br /> <br /> =Types of activity locking code=<br /> For the purpose of this MoodleDoc article: AL is any code that allows the user to make decisions on the next available resource or item the student will be able to use based on student events or quiz performance. There is some activity locking code that is very quick and dirty to simply lock future activities and then there is much more complex code based on the conditional activity though structure which attempts to progress the student through the course in a thought out progression based on activities and performance. Again we hope to clarify some of this here.<br /> <br /> ==AL Branch 1.0 (Bernard Boucher)==<br /> Bernard started all this with a hack to lock the certificate based on a quiz score in 2004. It was a great start! <br /> <br /> == AL Branch 2.1 for Moodle 1.6 (Stuart Mayor)==<br /> *This has been virtually a complete rewrite and as such there are areas of functionality the were available in older versions of AL that are not in this. <br /> <br /> * Conditional locking: Lock based on a user's performance in previous activities. You can also choose to unlock and activity if a user scores less than a certain grade.<br /> * Show activity completion: The checkbox that appears before each activity to show it have been done.<br /> * A variation on this also hides future activities, see AL Branch 2.1 for Moodle 1.6 (John Gschnaidner-Chardelle Busch) below.<br /> * Bernard Boucher reworked Stuart's version and on June 20, 2006 posted [http://206.167.134.155/bb/authoring1/activity_locking_v2_for_16_20060620.zip '''Activity_locking_v2_for_16_20060620.zip'''] on [http://moodle.org/mod/forum/user.php?id=1323&amp;course=5 Activity Locking v3 or v2 for testing only]. The link is outside moodle.org and the link was not working on June 29, 2006. Bernard Boucher's version is not based on Stuart's version 3 anyway.--[[User:N Hansen|N Hansen]] 13:17, 2 July 2006 (WST)<br /> <br /> ===Installation for 2.1 for Moodle 1.6(Stuart Meyor)===<br /> '''activitylocking20051201.zip''' the initial version<br /> <br /> * Firstly, you need the stable build of Moodle 1.6. This version of AL might work on earlier releases but I didn't write it with them in mind and I certainly can't support them.<br /> Next, you need to modify one table in the database and add a new one (I use phpmyadmin for this). <br /> <br /> * The table you need to modify is mdl_course_modules and you need to add the following fields:<br /> completedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '0'<br /> completedscore VARCHAR(255) NOT NULL<br /> completedstyle VARCHAR(255) NOT NULL<br /> lockedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> lockedstyle VARCHAR(255) NOT NULL DEFAULT 'locked'<br /> lockedvisible TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> delay INT(10) UNSIGNED NOT NULL DEFAULT '0'<br /> <br /> * The table you need to create is as follows:<br /> CREATE TABLE `mdl_course_locks` (<br /> `id` int(10) unsigned NOT NULL auto_increment,<br /> `courseid` int(10) unsigned NOT NULL default '0',<br /> `locktype` varchar(10) NOT NULL default '',<br /> `targetid` int(10) unsigned NOT NULL default '0',<br /> `locks` longtext NOT NULL,<br /> PRIMARY KEY (`id`)<br /> ) TYPE=MyISAM COMMENT='Contains locks for sections and modules';<br /> * Lastly, you need to copy the following files from the zip file:<br /> lib/moodlelib.php to moodle/lib/moodlelib.php<br /> lib/locklib.php to moodle/lib/locklib.php<br /> course/lib.php to moodle/course/lib.php<br /> course/lock.php to moodle/course/lock.php<br /> course/mod.php to moodle/course/mod.php<br /> course/settings.html to moodle/course/settings.html<br /> pix/t/open.gif to moodle/pix/t/open.gif<br /> pix/t/closed.gif to moodle/pix/t/closed.gif<br /> lang/en/lock.php to moodle/lang/en/lock.php<br /> <br /> ==AL Branch 2.2 for Moodle 1.6 (John Gschnaidner-Chardelle Busch and others)==<br /> John's versionincludes the settings tab--making it possible to set the hide/visible options, as well as the completion (a checkmark in front of a resource/activity) options, says Chardelle. <br /> * A variation on Stuart Mayor's 2.1, it hides topics dependent upon conditions set on specific activities/resources '''ALV2_1_debug.ZIP''' (John). Had bug which Benard tweaked out.<br /> * A build of Stuarts Mayor's 2.1 it locks and/or hides specific activities depending upon conditions set on specific activities/resources. Was posted by Chardelle in [http://proemployees.com/ActivityLockingWithHide-1.6.zip '''ActivityLockingWithHide-1.6.zip''']. Probably same as above. Had bug which Benard tweaked out.<br /> * A tweak by Bernard Boucher on June 27, 2006 was posted [http://moodle.org/mod/forum/discuss.php?d=35488&amp;parent=222516 moodle/lib/locklib.php file] and called '''locklib.zip''' seems to fix known bug in both the above downloads.<br /> <br /> ==AL Branch 3.s for Moodle 1.6 (Stuart Mayor)==<br /> Similar to the 2.x versions. Major difference is that a question to the student unlocks activities. Being actively developed and tested.<br /> <br /> ==CA Branch 1.0 for Moodle 1.5.2 (David Delgado)==<br /> Details and discussed in the thread &quot;NEW research on CONDITIONAL ACTIVITIES in Moodle&quot;<br /> <br /> = Table of Versions, to be completed... =<br /> {| border=&quot;3&quot; padding=&quot;4&quot;<br /> |+ Activity Locking updated 29 June 2006 10:00 AM EST<br /> ! -Version- <br /> ! Moodle version<br /> ! Who<br /> ! Status<br /> ! MySql Install<br /> ! Docs<br /> ! Comments <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Bug <br /> ! Bug <br /> |-----<br /> | AL 3.0<br /> | 1.5.2<br /> | Stuart Mayor<br /> | not finished<br /> |<br /> |[http://moodle.org/mod/forum/discuss.php?d=46863]<br /> | <br /> | AL<br /> | A/R dep on questions<br /> |-----<br /> | AL 2.3<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | <br /> | AL<br /> | A/R/T dep on A/Rs<br /> |-----<br /> | AL 2.2<br /> | 1.6<br /> | Gschnaidner, Mayor, Busch, Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488#220946]<br /> | almost<br /> | AL<br /> | A/R dep on A/Rs<br /> | +Hide<br /> |<br /> | bug fix<br /> |-----<br /> | AL 2.1<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | base<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | see above<br /> | AL<br /> |-----<br /> | C A 1.0<br /> | 1.5.2<br /> | David Delgado Borja Rubio Reyes<br /> | <br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=36697]<br /> |<br /> | AL<br /> |}<br /> <br /> =General installation instructions DRAFT=<br /> Installing AL on a localhost (desktop) machine was not difficult! Some months ago I must have downloaded and connected phpAdministration and that came in handy for step 6. I just did a conversion and it took me less than 30 minutes (actually I think the AL part was done in 3 minutes ) because I wanted to install the latest version of Moodle 1.6 and then zipped my entire Moodle16 file structure before I attempted the AL installation.<br /> *1. Perform any backups you think are necessary (I zipped everything in my localhost path).<br /> *2. Select the zip file flavor of AL you want and download it (I used Chardelle's zip plus Bernards tweak found in 2.2 above)<br /> *3. Unzip it to a non Moodle place. (Like to keep the folder structures option)<br /> *4. Locate the MySQL.sql file so you can find it again.<br /> *5. In Moodle as admin, go to Administration, Configuration and turn on Maintence Mode.<br /> *6. Go to Administration, Database. In the home query window, on the left, click on moodle (mine says Moodle16 and has a bunch of mdl_ listings under it). <br /> *7. Best: Click on the SQL tab. In the location of the text file, browse to the file in #4, then click go.<br /> *7. Alternative: use the MySQL document and make or changes in <br /> *8. Leave Moodle, shut that browser window.<br /> *9. Now you need to move the files in the folders located in #3 to your Moodle file structure. (See my tip below). In your non moodle area you have unpack the file to a folder called ActivityLockingWithHide. It has a folder called Moodle in it, with sub folders under it, for example ActivityLockingWithHide\Moodle\Course. You should copy ever file from there to your local host file structure in the same spot. (Mine is Moodle16\Moodle\Course ).<br /> *10. Go back into Moodle, log in as Admin, go to Administration. Moodle will adjust itself.<br /> *11 Check in Administration, Configuration, Maintence to make sure it is disabled. <br /> *12. You are done, check out a lesson with weeks or topics, go to lesson settings and notice the new tabs.<br /> * TIP? There is probably a slicker way but after I unzipped the file in #3, I went down a level and zipped the Moodle folder. Then I unpacked the files to Moodle16\, told the unzip program to keep the folder structure and overwrite existing files. <br /> <br /> <br /> <br /> <br /> <br /> <br /> =See Also=<br /> *[[Adding_activity_locks]] will give the reader an idea of what one of the flavors of Activity Locking looks like for a student and teacher setting it up. <br /> <br /> Please visit the Moodle Forum for more information concerning Activity Locking and Conditional Activities-<br /> <br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> * http://moodle.org/mod/forum/view.php?id=4295<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> There is a very specialized-limited type of activity locking under a lesson (activity) setting called dependency in 1.6. See: *https://docs.moodle.org/en/Adding/editing_a_lesson#Dependent_on . <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/Activity_Locking&diff=12716 2006-07-02T05:17:27Z

<p>Hatshepsut: /* AL Branch 2.1 for Moodle 1.6 (Stuart Mayor) */</p> <hr /> <div>=Overview=<br /> This page is an attempt to consolidate and explain the available activity locking (AL) code that is present for Moodle 1.5.x and 1.6.x. This page will hopefully help explain all the available versions and their respective features. Some of the reference here will overlap with the existing MoodleDoc page covering [[Conditional activities]]. <br /> <br /> Please be patient as this page is new and under development. See page comments for reference material.<br /> <br /> =Types of activity locking code=<br /> For the purpose of this MoodleDoc article: AL is any code that allows the user to make decisions on the next available resource or item the student will be able to use based on student events or quiz performance. There is some activity locking code that is very quick and dirty to simply lock future activities and then there is much more complex code based on the conditional activity though structure which attempts to progress the student through the course in a thought out progression based on activities and performance. Again we hope to clarify some of this here.<br /> <br /> ==AL Branch 1.0 (Bernard Boucher)==<br /> Bernard started all this with a hack to lock the certificate based on a quiz score in 2004. It was a great start! <br /> <br /> == AL Branch 2.1 for Moodle 1.6 (Stuart Mayor)==<br /> *This has been virtually a complete rewrite and as such there are areas of functionality the were available in older versions of AL that are not in this. <br /> <br /> * Conditional locking: Lock based on a user's performance in previous activities. You can also choose to unlock and activity if a user scores less than a certain grade.<br /> * Show activity completion: The checkbox that appears before each activity to show it have been done.<br /> * A variation on this also hides future activities, see AL Branch 2.1 for Moodle 1.6 (John Gschnaidner-Chardelle Busch) below.<br /> * Bernard Boucher reworked Stuart's version and on June 20, 2006 posted [http://206.167.134.155/bb/authoring1/activity_locking_v2_for_16_20060620.zip '''Activity_locking_v2_for_16_20060620.zip'''] on [http://moodle.org/mod/forum/user.php?id=1323&amp;course=5 Activity Locking v3 or v2 for testing only]. The link is outside moodle.org and the link was not working on June 29, 2006. Bernard Boucher's version is not based on Stuart's version 3 anyway.--[[User:N Hansen|N Hansen]] 13:17, 2 July 2006 (WST)<br /> <br /> ===Installation for 2.1 for Moodle 1.6(Stuart Mayor)===<br /> '''activitylocking20051201.zip''' the initial version<br /> <br /> * Firstly, you need the stable build of Moodle 1.6. This version of AL might work on earlier releases but I didn't write it with them in mind and I certainly can't support them.<br /> Next, you need to modify one table in the database and add a new one (I use phpmyadmin for this). <br /> <br /> * The table you need to modify is mdl_course_modules and you need to add the following fields:<br /> completedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '0'<br /> completedscore VARCHAR(255) NOT NULL<br /> completedstyle VARCHAR(255) NOT NULL<br /> lockedbox TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> lockedstyle VARCHAR(255) NOT NULL DEFAULT 'locked'<br /> lockedvisible TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'<br /> delay INT(10) UNSIGNED NOT NULL DEFAULT '0'<br /> <br /> * The table you need to create is as follows:<br /> CREATE TABLE `mdl_course_locks` (<br /> `id` int(10) unsigned NOT NULL auto_increment,<br /> `courseid` int(10) unsigned NOT NULL default '0',<br /> `locktype` varchar(10) NOT NULL default '',<br /> `targetid` int(10) unsigned NOT NULL default '0',<br /> `locks` longtext NOT NULL,<br /> PRIMARY KEY (`id`)<br /> ) TYPE=MyISAM COMMENT='Contains locks for sections and modules';<br /> * Lastly, you need to copy the following files from the zip file:<br /> lib/moodlelib.php to moodle/lib/moodlelib.php<br /> lib/locklib.php to moodle/lib/locklib.php<br /> course/lib.php to moodle/course/lib.php<br /> course/lock.php to moodle/course/lock.php<br /> course/mod.php to moodle/course/mod.php<br /> course/settings.html to moodle/course/settings.html<br /> pix/t/open.gif to moodle/pix/t/open.gif<br /> pix/t/closed.gif to moodle/pix/t/closed.gif<br /> lang/en/lock.php to moodle/lang/en/lock.php<br /> <br /> ==AL Branch 2.2 for Moodle 1.6 (John Gschnaidner-Chardelle Busch and others)==<br /> John's versionincludes the settings tab--making it possible to set the hide/visible options, as well as the completion (a checkmark in front of a resource/activity) options, says Chardelle. <br /> * A variation on Stuart Mayor's 2.1, it hides topics dependent upon conditions set on specific activities/resources '''ALV2_1_debug.ZIP''' (John). Had bug which Benard tweaked out.<br /> * A build of Stuarts Mayor's 2.1 it locks and/or hides specific activities depending upon conditions set on specific activities/resources. Was posted by Chardelle in [http://proemployees.com/ActivityLockingWithHide-1.6.zip '''ActivityLockingWithHide-1.6.zip''']. Probably same as above. Had bug which Benard tweaked out.<br /> * A tweak by Bernard Boucher on June 27, 2006 was posted [http://moodle.org/mod/forum/discuss.php?d=35488&amp;parent=222516 moodle/lib/locklib.php file] and called '''locklib.zip''' seems to fix known bug in both the above downloads.<br /> <br /> ==AL Branch 3.s for Moodle 1.6 (Stuart Mayor)==<br /> Similar to the 2.x versions. Major difference is that a question to the student unlocks activities. Being actively developed and tested.<br /> <br /> ==CA Branch 1.0 for Moodle 1.5.2 (David Delgado)==<br /> Details and discussed in the thread &quot;NEW research on CONDITIONAL ACTIVITIES in Moodle&quot;<br /> <br /> = Table of Versions, to be completed... =<br /> {| border=&quot;3&quot; padding=&quot;4&quot;<br /> |+ Activity Locking updated 29 June 2006 10:00 AM EST<br /> ! -Version- <br /> ! Moodle version<br /> ! Who<br /> ! Status<br /> ! MySql Install<br /> ! Docs<br /> ! Comments <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Feature <br /> ! Bug <br /> ! Bug <br /> |-----<br /> | AL 3.0<br /> | 1.5.2<br /> | Stuart Mayor<br /> | not finished<br /> |<br /> |[http://moodle.org/mod/forum/discuss.php?d=46863]<br /> | <br /> | AL<br /> | A/R dep on questions<br /> |-----<br /> | AL 2.3<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | <br /> | AL<br /> | A/R/T dep on A/Rs<br /> |-----<br /> | AL 2.2<br /> | 1.6<br /> | Gschnaidner, Mayor, Busch, Boucher<br /> | Testing<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488#220946]<br /> | almost<br /> | AL<br /> | A/R dep on A/Rs<br /> | +Hide<br /> |<br /> | bug fix<br /> |-----<br /> | AL 2.1<br /> | 1.6<br /> | Stuart Mayor, Benard Boucher<br /> | base<br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=35488]<br /> | see above<br /> | AL<br /> |-----<br /> | C A 1.0<br /> | 1.5.2<br /> | David Delgado Borja Rubio Reyes<br /> | <br /> | <br /> | [http://moodle.org/mod/forum/discuss.php?d=36697]<br /> |<br /> | AL<br /> |}<br /> <br /> =General installation instructions DRAFT=<br /> Installing AL on a localhost (desktop) machine was not difficult! Some months ago I must have downloaded and connected phpAdministration and that came in handy for step 6. I just did a conversion and it took me less than 30 minutes (actually I think the AL part was done in 3 minutes ) because I wanted to install the latest version of Moodle 1.6 and then zipped my entire Moodle16 file structure before I attempted the AL installation.<br /> *1. Perform any backups you think are necessary (I zipped everything in my localhost path).<br /> *2. Select the zip file flavor of AL you want and download it (I used Chardelle's zip plus Bernards tweak found in 2.2 above)<br /> *3. Unzip it to a non Moodle place. (Like to keep the folder structures option)<br /> *4. Locate the MySQL.sql file so you can find it again.<br /> *5. In Moodle as admin, go to Administration, Configuration and turn on Maintence Mode.<br /> *6. Go to Administration, Database. In the home query window, on the left, click on moodle (mine says Moodle16 and has a bunch of mdl_ listings under it). <br /> *7. Best: Click on the SQL tab. In the location of the text file, browse to the file in #4, then click go.<br /> *7. Alternative: use the MySQL document and make or changes in <br /> *8. Leave Moodle, shut that browser window.<br /> *9. Now you need to move the files in the folders located in #3 to your Moodle file structure. (See my tip below). In your non moodle area you have unpack the file to a folder called ActivityLockingWithHide. It has a folder called Moodle in it, with sub folders under it, for example ActivityLockingWithHide\Moodle\Course. You should copy ever file from there to your local host file structure in the same spot. (Mine is Moodle16\Moodle\Course ).<br /> *10. Go back into Moodle, log in as Admin, go to Administration. Moodle will adjust itself.<br /> *11 Check in Administration, Configuration, Maintence to make sure it is disabled. <br /> *12. You are done, check out a lesson with weeks or topics, go to lesson settings and notice the new tabs.<br /> * TIP? There is probably a slicker way but after I unzipped the file in #3, I went down a level and zipped the Moodle folder. Then I unpacked the files to Moodle16\, told the unzip program to keep the folder structure and overwrite existing files. <br /> <br /> <br /> <br /> <br /> <br /> <br /> =See Also=<br /> *[[Adding_activity_locks]] will give the reader an idea of what one of the flavors of Activity Locking looks like for a student and teacher setting it up. <br /> <br /> Please visit the Moodle Forum for more information concerning Activity Locking and Conditional Activities-<br /> <br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> * http://moodle.org/mod/forum/view.php?id=4295<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> There is a very specialized-limited type of activity locking under a lesson (activity) setting called dependency in 1.6. See: *https://docs.moodle.org/en/Adding/editing_a_lesson#Dependent_on . <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12707 2006-07-01T20:38:15Z

<p>Hatshepsut: /* Releases */</p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayer. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6.<br /> <br /> It would be helpful if when someone creates and lists a new version here they state what version their new version is based on.--[[User:N Hansen|N Hansen]] 04:38, 2 July 2006 (WST) <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> <br /> '''AL v2.1(john)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006, based on the version of activity locking released by Stuart Meyor on October 19, 2005. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Johns Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them.[http://moodle.org/mod/forum/discuss.php?d=46863#220125 AL v2.1-M1.6]<br /> <br /> '''AL v2.1 for 1.6(chardelle)''' - link posted by Chardelle on 25 June 2006, 03:35 PM. This flavor has a hide future activity function and seems to be functioning on some Moodles but is being tweaked for others. See forum discussion: [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 Certificate 1.6 with Security discussion in Activity Module forum].The link for the external website is: [http://proemployees.com/ActivityLockingWithHide-1.6.zip AL v2.1 for 1.6(chardelle)].<br /> <br /> [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.<br /> <br /> Locking a topic is an all-or-nothing proposition. If you lock at topic, you cannot have individual conditions on locking of the items inside that topic. It would be nice if this were not the case.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12706 2006-07-01T20:36:59Z

<p>Hatshepsut: /* Releases */ fixed bad links</p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayer. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6. <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> <br /> '''AL v2.1(john)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006, based on the version of activity locking released by Stuart Meyor on October 19, 2005. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Johns Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them.[http://moodle.org/mod/forum/discuss.php?d=46863#220125 AL v2.1-M1.6]<br /> <br /> '''AL v2.1 for 1.6(chardelle)''' - link posted by Chardelle on 25 June 2006, 03:35 PM. This flavor has a hide future activity function and seems to be functioning on some Moodles but is being tweaked for others. See forum discussion: [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 Certificate 1.6 with Security discussion in Activity Module forum].The link for the external website is: [http://proemployees.com/ActivityLockingWithHide-1.6.zip AL v2.1 for 1.6(chardelle)].<br /> <br /> [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984 AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863 AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.<br /> <br /> Locking a topic is an all-or-nothing proposition. If you lock at topic, you cannot have individual conditions on locking of the items inside that topic. It would be nice if this were not the case.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=error/moodle/onlyeditown&diff=12671 2006-06-30T22:15:15Z

<p>Hatshepsut: </p> <hr /> <div>Students and teachers can only edit their own profiles. Administrators, however, can edit anyone's profile.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12630 2006-06-29T12:22:26Z

<p>Hatshepsut: /* Future of Conditional Activities */</p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayer. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6. <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> '''AL v2.1(john)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006, based on the version of activity locking released by Stuart Meyor on October 19, 2005. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Johns Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them.[http://moodle.org/mod/forum/discuss.php?d=46863#220125: AL v2.1-M1.6]<br /> <br /> '''AL v2.1 for 1.6(chardelle)''' - link posted by Chardelle on 25 June 2006, 03:35 PM. This flavor has a hide future activity function and seems to be functioning on some Moodles but is being tweaked for others. See forum discussion: [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 Certificate 1.6 with Security discussion in Activity Module forum].The link for the external website is: [http://proemployees.com/ActivityLockingWithHide-1.6.zip AL v2.1 for 1.6(chardelle)].<br /> <br /> [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.<br /> <br /> Locking a topic is an all-or-nothing proposition. If you lock at topic, you cannot have individual conditions on locking of the items inside that topic. It would be nice if this were not the case.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12628 2006-06-29T11:34:26Z

<p>Hatshepsut: /* Releases */ adding extra information and correct misstatement I made</p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayer. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6. <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> '''AL v2.1(john)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006, based on the version of activity locking released by Stuart Meyor on October 19, 2005. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Johns Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them.[http://moodle.org/mod/forum/discuss.php?d=46863#220125: AL v2.1-M1.6]<br /> <br /> '''AL v2.1 for 1.6(chardelle)''' - link posted by Chardelle on 25 June 2006, 03:35 PM. This flavor has a hide future activity function and seems to be functioning on some Moodles but is being tweaked for others. See forum discussion: [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 Certificate 1.6 with Security discussion in Activity Module forum].The link for the external website is: [http://proemployees.com/ActivityLockingWithHide-1.6.zip AL v2.1 for 1.6(chardelle)].<br /> <br /> [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Developer_notes&diff=12547 2006-06-27T18:40:30Z

<p>Hatshepsut: </p> <hr /> <div>&lt;p class=&quot;note&quot;&gt; '''Note for contributors:''' This area is for developers to work on various bits of code and documentation as necessary. Once material has matured it should be linked to from the main [[Developer documentation]] page.<br /> Initial text has been taken from [http://moodle.org/course/view.php?id=5 Using Moodle] Developer Wiki. If you find any text missing, please email docs AT moodle DOT org.&lt;/p&gt;<br /> <br /> <br /> *[[Forum development|Forum functional upgrade]]<br /> *[[Other lang issues|Language issues]] <br /> *[[MoodleDocs development]]<br /> *[[Datalib Notes]]<br /> *[[Usability]]<br /> *[[Blogs and forums|Blogs, forums and the nature of discussion]]<br /> *[[Document Management API]]<br /> *[[Filters schema]]<br /> *[[Filterall support]]<br /> *[[Application/session variables]]<br /> *[[Wiki development|Wiki module development]]<br /> *[[Conditional activities]]<br /> *[[Roles]]<br /> *[[Improved Payment Plugin]]<br /> <br /> <br /> [[Category:Developer]]</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12518 2006-06-26T23:54:42Z

<p>Hatshepsut: /* Releases */</p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005<br /> *[http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayer. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6. <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> '''AL v2.1(john)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Johns Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them. Does not allow you to lock entire topics. [http://moodle.org/mod/forum/discuss.php?d=46863#220125: AL v2.1-M1.6]<br /> <br /> '''AL v2.1 for 1.6(chardelle)''' - link posted by Chardelle on 25 June 2006, 03:35 PM. This flavor has a hide future activity function and seems to be functioning on some Moodles but is being tweaked for others. See forum discussion: [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 Certificate 1.6 with Security discussion in Activity Module forum].The link for the external website is: [http://proemployees.com/ActivityLockingWithHide-1.6.zip AL v2.1 for 1.6(chardelle)].<br /> <br /> [http://moodle.org/mod/forum/discuss.php?d=47906&amp;parent=221613 AL v2.1 wH1.6] titled Re: Certificate for 1.6 with security in Activity Modules forum<br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12448 2006-06-25T12:21:44Z

<p>Hatshepsut: /* Releases */</p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005 <br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayer. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6. <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> '''AL v2.1(jon)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Jons Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them.[http://moodle.org/mod/forum/discuss.php?d=46863#220125: AL v2.1-M1.6]<br /> <br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.</div>

Hatshepsut https://docs.moodle.org/2x/ca/index.php?title=Broken/id:3303&diff=12447 2006-06-25T12:18:14Z

<p>Hatshepsut: </p> <hr /> <div>==Purpose of page==<br /> I think others have an idea, but some of us are confused about what is what. I am going through the condiditional activity forum to track what has been posted. I started with the summary of Alvin Shaffer - Wednesday, 21 June 2006, 08:18 AM as the outline. Comments placed here are out of context and were made by others in the forum threads listed below. I would like to see the link to the best versions 1.5.3 and 1.6 versions of AL placed on the article page.--[[User:chris collman 2|chris collman 2]] 19:13, 23 June 2006 (WST)<br /> <br /> AL 3.0 is conditional based vs AL 2.1 being more straight forward AL based.<br /> ==Forum Threads==<br /> These threads link to the Conditional Activity forum.<br /> *[http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] titled Activity Locking v2.1 (for Moodle 1.6)<br /> *[http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] titled Activity Locking v3<br /> *[http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] titled NEW research on CONDITIONAL ACTIVITIES in Moodle<br /> *[http://moodle.org/mod/forum/discuss.php?d=31627&amp;parent=152788: AL v2.1 LALR] titled Latest Activity Locking Release started 19 October 2005 <br /> <br /> ==Releases==<br /> There seem to be several flavors of AL. v1 and v2 seemed to be started by Stuart Mayer. Then Stuart and David Delgado worked independently on v3. There are v2 and v3 for 1.5 and for 1.6. <br /> <br /> '''AL v2.1(stuart''') - released by Stuart on Dec. 1, 2005 - Not a lot of success by forum (not sure if this version is based on pure AL or conditionals) <br /> *zip <br /> *zip 1 December 2005, 10:28 AM activitylocking20051201.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> '''AL v2.1(jon)'''- released by Jon on June 1, 2006 - Modified 2.1 with hides for ver 1.6. Non Block installed based AL , must hack database , etc. Not sure a list of feature differences to V2.1(stuart) <br /> *zip 12 May 2006, 09:02 AM ActivityLockingV2.1Moodle1.6.7z [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> *zip 15 May 2006, 02:23 AM AL2_1_debug.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> **Tweak 23 June 2006, 01:45 AM lock.php [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] <br /> <br /> <br /> '''AL v2.1(benard)''' - released by Bernard on June 21st, 2006. A hack of the Block installer based AL (2.1). So far in testing this version seams to work in 1.6, just not sure what features from Jons Hack are not included (as Chardelle alluded to). Locking seems to work, but setting activity prerequisites to &quot;no&quot; still shows them.<br /> <br /> <br /> '''AL v3.0(stuart)''' - Modified files to try to hack AL ver 3.0 for 1.6 released by Chardelle on June 15th, 2006 - (Stuart released Ver 3.0 AL for 1.5.X code) not a working version due to the quiz module changes and other issues (hopefully stuart is working on a 1.6 version) <br /> *zip 29 April 2006, 11:42 AM activitylocking_1.6_beta3.zip [http://moodle.org/mod/forum/discuss.php?d=35488#220984: AL v2.1-M1.6] (posted Eduardo)<br /> *zip 14 June 2006, 01:18 PM al_ver3_for16.ZIP [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted Chardelle)<br /> **tweak 6 June 2006, 02:55 AM mysql.sql [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> *zip 1 June 2006, 04:16 AM ActivityLockingWithHide.7z [http://moodle.org/mod/forum/discuss.php?d=46863: AL v3.0-Mx] (posted John G)<br /> <br /> '''AL v3.0(david)''' - David Delgado's group<br /> *zip 9 February 2006, 09:09 AM moodle-1.5.2.zip (for Windows) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD] <br /> *zip 9 February 2006, 09:09 moodle-1.5.2.tgz (for Linux and Unix) [http://moodle.org/mod/forum/discuss.php?d=36697 AL v3.0-DD]<br /> *zip SOURCE CODE.<br /> <br /> ==Future of Conditional Activities==<br /> <br /> Let's use this to brainstorm additional features of conditional activities we would like to see as well.--[[User:N Hansen|N Hansen]] 20:18, 25 June 2006 (WST)<br /> <br /> One feature that is missing is related to choice module. Making a lock dependent on a choice module instance only makes it so that the student has to view the choice, not actually make a choice. It seems that answering the choice should be required.</div>

Hatshepsut