click here for details... Sakai Executive Director Position Search now open
Issue Details (XML | Word | Printable)

Key: SAK-7583
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Oliver Heyer
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sakai

Add gradebook to Sakai site export/archive

Created: 09-Jan-2007 10:28   Updated: 23-Oct-2008 10:33  Due: 11-Jan-2007
Component/s: Gradebook, Site Archive (Admin Site Management)
Affects Version/s: 2.4.0
Fix Version/s: 2.4.0

Time Tracking:
Not Specified

Issue Links:
Depend
 
Duplicate
 
Relate
 

2.6.x Status: None
2.5.x Status: None
2.4.x Status: None


 Description  « Hide
Add gradebook to Sakai site export/archive.

1. All student information will be removed
2. All scores will be removed
3. Only internal gradebook assignments (those with all data stored in gradebook tables) will be included in the export.
4. Assignment due dates will be included in the export to ensure that the order of the assignments is retained. Assignment order is determined by due date. Assignments without due dates will be appended at the end of the list in alphanumeric order.

Specification at:
http://bugs.sakaiproject.org/confluence/display/SG2X/Export+and+import+between+sites

 All   Comments   Work Log   Change History   Subversion Commits   git Commits      Sort Order: Ascending order - Click to sort in descending order
Ray Davis added a comment - 10-Jan-2007 17:04
A couple of functional spec questions, with my guessed answers....

1) Should the assignment's "is counted" state be included? My guess is yes, since that's presumably often used to distinguish survey or trial assessments.

2) Should the assignment's "is released" state be included? My guess is no, since that's presumably more often used to indicate that everyone's taken the assignment.

3) Should gradebook-wide options (notably the grading scheme) be included? My guess is no, at least in this first release, since Sakai users can import from multiple sites / archives at once or over time.

Ray Davis added a comment - 10-Jan-2007 17:10
Since export/import is allowed at any time, I think it makes sense to add (as needed) to the Gradebook service API to handle all of the actual reads and writes. That way the same code can be used whether we use the legacy "Entity" approach or the projected new import/export approach.

Kate Ellis added a comment - 11-Jan-2007 11:18
Will the export include assignments tied to the Assignment , Test and Survey and Message Center tools if the data from those tools are also exported?

Oliver Heyer added a comment - 11-Jan-2007 11:49
It will not include anything from Test and Quzzes because that tool stores its own data about the grade entries that are exported.

As of 2.4, Assignments will allow you to create entries that are stored in the Gradebook database. Those entries will be included because they will not create the potential for future data problems upon import of the gradebook "shell."

Message Center does not store its own grade information, so there is no potential for conflict. All of the MC entries will be included.

It is important to distinguish between the ability to archive a site and to re-use it. We are tackling the latter in this task. Sakai does not yet provide a way to take a complete snapshot of a site and then selectively import that same site for re-use.

Ray Davis added a comment - 16-Jan-2007 12:33
Before adding new methods to the one monolithic GradebookService, we wanted to split it into three separate service interfaces to reflect our three types of programmatic client: code which wanted to act like the Gradebook application itself does (including any authorization checks), external assessment engines which completely control their own data and use the Gradebook just as a passive mirror, and the framework which creates and deletes Gradebook instances.

Since this task involves adding service methods, I finally made the split and checked it as revision 20345.

Ray Davis added a comment - 29-Jan-2007 11:11
After looking at the legacy "Site Archive" UI and code, Oliver and I agreed that for now we would stick to supporting migration between sites ("Import from Site" rather than "Import from File"). We'll leave external archival and restoration to be part of the newer archive / import / merge work.

Checked in support for site migration (with some guesses for future work) as revision 20758.

Megan May added a comment - 12-Apr-2007 13:45
Tasks for 2.4 have been completed. If you find a problem related to a task, please create a bug report and use the Link feature to create a connection between the two issues.