Development:Backup 2.0 requirements: Difference between revisions
(New page: {{Template:Development:Backup 2.0}}{{Moodle_2.0}}__NOTOC__{{Work in progress}} This page shows the analysis/justification/decision for all the [[Development:Backup 2.0 drop in ideas|drop i...) |
(→RQ01:) |
||
| Line 5: | Line 5: | ||
== RQ01: == | == RQ01: == | ||
'''Enable Backup and restore of a Course and it's related meta courses IN ONE HIT to save on adminstration time''' | |||
Meta courses are out in Moodle 2.0 and their functionality will be, somehow, replaced my the new [[Development:Cohorts | Cohorts]] (a.k.a. site-wide groups). In any case, and as a general rule, any backup / restore operation involving more that one course is not backup / restore responsibility (i.e. the functionality is not built in there) but responsibility of newly scripts using the new backup API to do those "multiple operations". | |||
== RQ02: == | == RQ02: == | ||
Revision as of 10:17, 25 April 2010
Template:Development:Backup 2.0Template:Moodle 2.0
Note: This article is a work in progress. Please use the page comments or an appropriate moodle.org forum for any recommendations/suggestions for improvement.
This page shows the analysis/justification/decision for all the drop in ideas detected/suggested along the last months mashed up with the main goals of the project. While pinpointing all the requirements of the new Backup 2.0, also we'll be defining the main list of tasks to fulfil them.
Note: For easier reference, all the requirements are labelled "RQxx" and all the associated tasks "RTxxyy", where "xx" is the requirement number and "yy" the task number" (obviously hopping we won't have more than 99 of them ;-) ).
RQ01:
Enable Backup and restore of a Course and it's related meta courses IN ONE HIT to save on adminstration time
Meta courses are out in Moodle 2.0 and their functionality will be, somehow, replaced my the new Cohorts (a.k.a. site-wide groups). In any case, and as a general rule, any backup / restore operation involving more that one course is not backup / restore responsibility (i.e. the functionality is not built in there) but responsibility of newly scripts using the new backup API to do those "multiple operations".
