Development:Assignment development - Revision history

Oasychev: /* Grading semi-plugins */

2009-10-13T18:24:02Z

Grading semi-plugins

← Older revision		Revision as of 18:24, 13 October 2009
Line 63:		Line 63:
	** if student from his/her group asks to delete him from team (or task change)		** if student from his/her group asks to delete him from team (or task change)
	** if there are students without task/team after date of last approval		** if there are students without task/team after date of last approval

			=== Grades aggregation ===
			Sometimes teacher want to grade student's submissions by several grading scales and than having the computer to calculate resulting grade. Is this possible using gradebook or should be duplicated in module is under investignation.

	=== Grading semi-plugins ===		=== Grading semi-plugins ===

Oasychev: /* DB structure */

2009-10-13T17:14:30Z

DB structure

← Older revision		Revision as of 17:14, 13 October 2009
Line 126:		Line 126:

	=== DB structure ===		=== DB structure ===
	[[Image:~~db_shema~~.jpg]]		[[Image:db schema.jpg]]

	The new db structure have such tables:		The new db structure have such tables:
Line 170:		Line 170:
	*# one student perform many roles		*# one student perform many roles
	Rethink tables/columns, define how a type plugin can use db, rename workgroups into teams everywhere --[[User:Oleg Sychev\|Oleg Sychev]] 11:12, 11 September 2009 (UTC)		Rethink tables/columns, define how a type plugin can use db, rename workgroups into teams everywhere --[[User:Oleg Sychev\|Oleg Sychev]] 11:12, 11 September 2009 (UTC)

	=== Tabs ===		=== Tabs ===

Josepuib: spelling mistakes

2009-10-09T16:47:24Z

spelling mistakes

Oasychev: Updating page before development begin

2009-09-11T11:12:37Z

Updating page before development begin

Show changes

Nakohdo: /* Capabilities */

2009-04-09T14:01:01Z

Capabilities

← Older revision		Revision as of 14:01, 9 April 2009
Line 222:		Line 222:
	* mod/task:selectowntask - student's ability to select task (setting to Deny allows for teachers-only tasks selection)		* mod/task:selectowntask - student's ability to select task (setting to Deny allows for teachers-only tasks selection)
	* mod/task:seeotherstasks - student's ability - if he/she is able to see what tasks are selected by other people, or he can see only if it free for selection		* mod/task:seeotherstasks - student's ability - if he/she is able to see what tasks are selected by other people, or he can see only if it free for selection

			[[Category:Assignment]]

Oasychev: Clean up things

2008-12-12T22:53:52Z

Clean up things

Show changes

Oasychev: /* Remove support of old syntactical constructs */

2008-12-07T19:28:15Z

Remove support of old syntactical constructs

← Older revision		Revision as of 19:28, 7 December 2008
Line 91:		Line 91:

	=== Remove support of old syntactical constructs ===		=== Remove support of old syntactical constructs ===
	It is possible to drop assignment_base class support ~~now~~, getting rid of legacy syntactical constructs.		It is possible to drop assignment_base class support at the end, getting rid of legacy syntactical constructs. The assigment_base class will be renamed and all legacy redirect functions will be deleted.

	Benefits:		Benefits:

Oasychev: /* Type plugins MDL-17531 */

2008-12-07T19:26:42Z

Type plugins MDL-17531

← Older revision		Revision as of 19:26, 7 December 2008
Line 73:		Line 73:


	Assignment_base class support can be dropped at any time from now on, if we want to force 3d party plugins to comply with new standards in 2.0 (or something), and get rid of internal legacy code as well.		Assignment_base class support can be dropped at any time from now on, if we want to force 3d party plugins to comply with new standards in 2.0 (or something), and get rid of internal legacy code as well. We can rename it to assignment_page and delete functions with compatibility redirections.

	=== Submission/grading separation ===		=== Submission/grading separation ===

Oasychev: /* Tabs MDL-17530 */

2008-12-07T19:26:00Z

Tabs MDL-17530

← Older revision		Revision as of 19:26, 7 December 2008
Line 43:		Line 43:
	#* check, if the user have a capabilities required to view this tab at all, and return a error message if necessary		#* check, if the user have a capabilities required to view this tab at all, and return a error message if necessary
	#* log tab action		#* log tab action
	# ~~assignment_page class~~ - child of abstract_tabbed_page with assignment-specific stuff; will create assignment_model instance and send it to the tab class		# assignment_base - child of abstract_tabbed_page with assignment-specific stuff; will create assignment_model instance and send it to the tab class, leaving there to not break compatibility with plugins (so it'll save all functions, that'll be moved to the tab and model classes, but their default implementations will redirect for needed class)
	# assignment_view class - child of abstract_tab to place a code for view function in assignment base, and all stuff closely related to it		# assignment_view class - child of abstract_tab to place a code for view function in assignment base, and all stuff closely related to it
	# assignment_grade class - child of abstract_tab to place a code for grading page (and popup window)		# assignment_grade class - child of abstract_tab to place a code for grading page (and popup window)
	# assignment_model class - class to place all functions of assignment_base, related to data handling and all generally useful helper functions; it will be cleaned up during next stages		# assignment_model class - class to place all functions of assignment_base, related to data handling and all generally useful helper functions; it will be cleaned up during next stages
	~~# assignment_base - may be left as a stub class to not break interface with plugins~~

	=== Plugins unification MDL-17529===		=== Plugins unification MDL-17529===

Oasychev: /* Tabs MDL-17530 */

2008-12-07T18:01:50Z

Tabs MDL-17530

← Older revision		Revision as of 18:01, 7 December 2008
Line 47:		Line 47:
	# assignment_grade class - child of abstract_tab to place a code for grading page (and popup window)		# assignment_grade class - child of abstract_tab to place a code for grading page (and popup window)
	# assignment_model class - class to place all functions of assignment_base, related to data handling and all generally useful helper functions; it will be cleaned up during next stages		# assignment_model class - class to place all functions of assignment_base, related to data handling and all generally useful helper functions; it will be cleaned up during next stages
	# assignment_base - ~~will~~ be left as a stub class to not break interface with plugins		# assignment_base - may be left as a stub class to not break interface with plugins

	=== Plugins unification MDL-17529===		=== Plugins unification MDL-17529===

← Older revision		Revision as of 16:47, 9 October 2009
Line 4:		Line 4:

	New module name will be a poasassignment.		New module name will be a poasassignment.
	== Assignment 1.9 ~~improvments~~ ==		== Assignment 1.9 improvements ==
	Just several simple, but useful ~~improvments~~ that can be done in stable version too:		Just several simple, but useful improvements that can be done in stable version too:
	# Usability ~~improvment~~: on submission.php add a ~~cobmo~~ box to filter the content of the table: Show all/with submissions/await grading. That speed up grading much. See MDL-14238		# Usability improvement: on submission.php add a combo box to filter the content of the table: Show all/with submissions/await grading. That speed up grading much. See MDL-14238
	# New capability: viewownsubmission. Setting it to Deny makes assignment module useful in exam context - collect student's work without their further access to it. See MDL-15356		# New capability: viewownsubmission. Setting it to Deny makes assignment module useful in exam context - collect student's work without their further access to it. See MDL-15356
	# Replace link with the number of submissions (for the teacher) with more informative "The ___ of ___ submissions needs grading". MDL-17613		# Replace link with the number of submissions (for the teacher) with more informative "The ___ of ___ submissions needs grading". MDL-17613
Line 30:		Line 30:
	* submission is one per team, but a grade can be given on per-team or per-student basis		* submission is one per team, but a grade can be given on per-team or per-student basis
	* teacher can define a minimum and maximum number of students in the team		* teacher can define a minimum and maximum number of students in the team
	* self-~~organisation~~ (with possibility of confirmation by teacher) or forced by teacher teams		* self-organization (with possibility of confirmation by teacher) or forced by teacher teams
	* maximum date of team membership editing		* maximum date of team membership editing
	* teacher can add ~~themselve~~ to teamas a mentor, then he only will be notified of events in this team		* teacher can add themselves to teamas a mentor, then he only will be notified of events in this team
	* 'roles' (or workroles to avoid confusion with Moodle Roles) of people in team (either teacher or student defined) - this is a way to explain who in group will do what		* 'roles' (or workroles to avoid confusion with Moodle Roles) of people in team (either teacher or student defined) - this is a way to explain who in group will do what
	** teacher-defined roles is a list, from which one or several roles can be selected for students		** teacher-defined roles is a list, from which one or several roles can be selected for students
Line 44:		Line 44:
	* standart fields: name, description, grade factor (1 by default), min/max teamnumber (if teams activated)		* standart fields: name, description, grade factor (1 by default), min/max teamnumber (if teams activated)
	* custom fields, which can be added in any given assignment, of several types: string, text, number, date, menu, file		* custom fields, which can be added in any given assignment, of several types: string, text, number, date, menu, file
	* some fields can only be ~~accesible~~ to the student once he is selected a task (and it will be approved by a teacher if necessary)		* some fields can only be accessible to the student once he is selected a task (and it will be approved by a teacher if necessary)
	* student's selection (with optional teacher approval), teacher-forced selection or random selection based on a student's selection of subset of tasks fields (number or menu mainly, i.e. some sort of 'complexity' field for example)		* student's selection (with optional teacher approval), teacher-forced selection or random selection based on a student's selection of subset of tasks fields (number or menu mainly, i.e. some sort of 'complexity' field for example)
	* maximum dates of selection (and approval if necessary)		* maximum dates of selection (and approval if necessary)
	* column with task name (link to the task) when grading		* column with task name (link to the task) when grading
	* random filling of some task fields (number or menu mainly) on selection or approval		* random filling of some task fields (number or menu mainly) on selection or approval
	** there is some problem of misuse of random generator; they are mainly ~~dealed~~ with fact that student's can change task and select new without teacher		** there is some problem of misuse of random generator; they are mainly dealt with fact that student's can change task and select new without teacher

	=== User interface - tabs ===		=== User interface - tabs ===
Line 56:		Line 56:
	New features will require more pages, so it's better to use tabs for them. Tabs visibility will be based on user's capabilities.		New features will require more pages, so it's better to use tabs for them. Tabs visibility will be based on user's capabilities.

	Urgent reminders will be places on top (or bottom?) of every tab with color ~~highliting~~;		Urgent reminders will be places on top (or bottom?) of every tab with color highlighting;
	* for students		* for students
	** if he is late to select a task/become a member of team		** if he is late to select a task/become a member of team
Line 77:		Line 77:
	* (2) student(s) can add themselves to the team, teacher can add students to the team (in last case student notified that he/she was added)		* (2) student(s) can add themselves to the team, teacher can add students to the team (in last case student notified that he/she was added)
	* (2) students can plead to free them from team/task, teacher can disapprove (if allowed) members or task (students is notified if they are disapproved)		* (2) students can plead to free them from team/task, teacher can disapprove (if allowed) members or task (students is notified if they are disapproved)
	* (2) after the team will have at least ~~minumum~~ number of participants -> '''have ~~enought~~ people''' (3)		* (2) after the team will have at least minimum number of participants -> '''have enough people''' (3)
	* (3) all (2) ~~operatoins~~ still available		* (3) all (2) operations still available
	* (3) students can confirm his will to work with team(now that he knows all it's ~~memebers~~), teacher can approve a team - approvment automatically cleared if team membership changes (people that have approves is notified)		* (3) students can confirm his will to work with team(now that he knows all it's members), teacher can approve a team - approvment automatically cleared if team membership changes (people that have approves is notified)
	* (3) after the date of last approval, no more changes in teams available for students, (for teachers it's depends on capabilities), if there is an unapproved team the teacher will be shown (and sent) urgent reminder		* (3) after the date of last approval, no more changes in teams available for students, (for teachers it's depends on capabilities), if there is an unapproved team the teacher will be shown (and sent) urgent reminder
	* (3) after the students (if allowed) approved a team and task -> '''ready''' (4) (if teacher approvment needed) or '''working''' (5) (students and teacher notified)		* (3) after the students (if allowed) approved a team and task -> '''ready''' (4) (if teacher approvment needed) or '''working''' (5) (students and teacher notified)
	* (4) after teacher approval -> '''working''' (5) (students notified)		* (4) after teacher approval -> '''working''' (5) (students notified)
	* (4) in case of teacher disapproval -> '''have ~~enought~~ people''' (3) (students notified)		* (4) in case of teacher disapproval -> '''have enough people''' (3) (students notified)
	* (5) any student in the team can submit work with flag 'please check our progress' (if allowed), then teacher is notified and able to give comment but not grade (teacher notified, student's notified of comment)		* (5) any student in the team can submit work with flag 'please check our progress' (if allowed), then teacher is notified and able to give comment but not grade (teacher notified, student's notified of comment)
	* (5) any student in team can make a normal submit, but it (optionally) may need an approval from other members for grading -> '''await grading''' (6) (teacher notified)		* (5) any student in team can make a normal submit, but it (optionally) may need an approval from other members for grading -> '''await grading''' (6) (teacher notified)
Line 104:		Line 104:

	=== New options ===		=== New options ===
	Let's see an assignment creation/editing screen. ~~Assigment~~ module will keep all existing options.		Let's see an assignment creation/editing screen. Assignment module will keep all existing options.

	New options that will be added:		New options that will be added:
Line 113:		Line 113:
	** min and max count of members of team		** min and max count of members of team
	** the grade will be individual or one per team		** the grade will be individual or one per team
	** if students must confirm it will to work with team (first student, who create a team, may not be happy with someone who add ~~youself~~ to it later)		** if students must confirm it will to work with team (first student, who create a team, may not be happy with someone who add yourself to it later)
	** if teacher must confirm team membership		** if teacher must confirm team membership
	** if all team ~~memebers~~ must confirm a submission before grading		** if all team members must confirm a submission before grading
	* individual task options (active only if tasks is selected)		* individual task options (active only if tasks is selected)
	** allow using same tasks - can several students do one task or all tasks must be different?		** allow using same tasks - can several students do one task or all tasks must be different?
	** allow using same tasks in one group		** allow using same tasks in one group
	** individual date - allow individual due dates to the task		** individual date - allow individual due dates to the task
	** individual team ~~memebers~~ count - if teams used, can particular task override min/max number of students in team		** individual team members count - if teams used, can particular task override min/max number of students in team
	** teacher must confirm task selection		** teacher must confirm task selection
	** random task assignment		** random task assignment
Line 194:		Line 194:
	* student: browsing task list, viewing task details		* student: browsing task list, viewing task details
	* student (without teams): selecting a task		* student (without teams): selecting a task
	* student (in team mode): see current teams(at least ~~uncomplete~~), create team for a task, apply for team membership		* student (in team mode): see current teams(at least incomplete), create team for a task, apply for team membership


Line 207:		Line 207:
	* grade columns/popus will be showed only when grading is allowed (or if person has mod/assignment:manageanything capability)		* grade columns/popus will be showed only when grading is allowed (or if person has mod/assignment:manageanything capability)
	*# team grades - each string represent a team		*# team grades - each string represent a team
	*# individual grades - each string ~~repesent~~ a student, but they are sorted by team and teams is spaced somehow		*# individual grades - each string represents a student, but they are sorted by team and teams is spaced somehow
	* make an option for the teachers to make any grade final, forbidding further re-submissions and/or regrading (a person with mod/assignment:manageanything can still regrade); in teams with individual grading mode re-submission will be forbidden only when all team members receive final grade		* make an option for the teachers to make any grade final, forbidding further re-submissions and/or regrading (a person with mod/assignment:manageanything can still regrade); in teams with individual grading mode re-submission will be forbidden only when all team members receive final grade
	* dropdown to choose whom to display in the table (and in the popup): all, with submissions only, needs grading only		* dropdown to choose whom to display in the table (and in the popup): all, with submissions only, needs grading only