mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Public bug reported:

What is wanted is a system where Mahara pages are archived as leap2a
files once they have been submitted for assessment purposes so that they
could be referenced more easily in the future if a student contests
their grades.

What this will entail is having a group config value where the group can
choose whether to archive the submission or not. So on release of
submission by teacher/tutor will send the submission off to an export
archive queue, which in turn archives the information as a leap2a file
before fully releasing the submission back to the student.

Because the releasing of submissions could be quite system intensive to
run all at once the export queue would check to see there is enough
system resources before doing the export.

This way the export queue could then be used for any leap2a exportation
(not just for submissions).

Also there will need to be a archive list that the admins can look at
and download the submitted leap2a file.

** Affects: mahara
     Importance: Medium
     Assignee: Robert Lyon (robertl-9)
         Status: In Progress


** Tags: archive

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1335670

Title:
  Allow submitted work to be archived as a leap2a file

Status in Mahara ePortfolio:
  In Progress

Bug description:
  What is wanted is a system where Mahara pages are archived as leap2a
  files once they have been submitted for assessment purposes so that
  they could be referenced more easily in the future if a student
  contests their grades.

  What this will entail is having a group config value where the group
  can choose whether to archive the submission or not. So on release of
  submission by teacher/tutor will send the submission off to an export
  archive queue, which in turn archives the information as a leap2a file
  before fully releasing the submission back to the student.

  Because the releasing of submissions could be quite system intensive
  to run all at once the export queue would check to see there is enough
  system resources before doing the export.

  This way the export queue could then be used for any leap2a
  exportation (not just for submissions).

  Also there will need to be a archive list that the admins can look at
  and download the submitted leap2a file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1335670/+subscriptions