r34565
Clear out the attached assignment when exporting since we don't know what to do with it yet.

Beth, moving this one over to you. I fixed the error when exporting, now you get the hard part of figuring out what to do with assignments! :)

Here are comments on matrix exporting use cases:
------------------------------------------------------------------------
On Sep 4, 2007, at 10:28 AM, Gonzalo Silverio wrote:

From our limited experience at Michigan: the only use cases I can think of for a matrix export are to:

1 - re-start authoring process after testing (export, import).

In this case the export acts to a) get rid of user data; b) unlock matrix for editing

It would be important in this case to keep assignment references, otherwise these would have to be redone.

2 - archive a scaffolding

In this case what is important is that the scaffolding made reference to an assignment - keeping the actual reference is not as important as knowing that there was one. For archival purposes we probably cannot guarantee permanence of the assignments it is making reference to.

3 - share a scaffolding

Important that no reference to an assignment be kept. Perhaps as above a stub that resolves to a message ("This cell originally made reference to an assignment")

Perhaps there should be 2 export types (Export for 1 above, Export for 2 and 3). Or better yet: 1) Restart authoring; 2) Export.

-----------------------------------------------------------------
On Sep 7, 2007, at 9:27 AM, Hugo Jacobs wrote:

When the export is meant to be reused within the same worksite, it is
easy to assess the 'links' leading to and from the matrix. (I see that
as the suggested option 1: Restart authoring)

When the export is reused in another worksite, it's integrity might be
compromised when links are included in the export. It may be imported at
another node or worksite where these links are dead ends. (here I refer
to option 2: export)

When including the assignments involves to much work it might be safer
to remove the links (In the export use case). In other software products
the result of an export is often reported on the screen or in a file (or
both). It would be possible to reconstruct/complete the imported matrix
with the help of such a report. This would require making new links to
available assignments in the worksite or making new assignments

There is a basic underpinning question that I have. What to export?
Forms are already included. But when including assignments, then how
about related goals?

--------------------------------------------------------------------
On Sep 7, 2007, at 10:22 AM, Sean Keesler wrote:

I'd like to add to Gonzalo's observations about what the matrix export is
used for.

I use the export feature NOT to merely restart the authoring process, but to
replicate the same environment for new cohorts of students. The new CIG gets
a fresh matrix with all of the form "dependencies" when I import it. I think
we have set a precedent for expected "export" behavior when the form
"dependencies" were included in a matrix export. Its pretty important to
follow through with that design decision.

If I wanted to replicate a matrix that had assignment dependencies, I would
be very confused when the same behavior (creating those assignments) did NOT
occur and I ended up with a "half-baked" matrix.

It will begin to be very difficult to share these data structures in our
(95% complete) community library if matrices have "bare wires" sticking out
of them, empty references to absent assignments.

Proposed Solution:

1. Always export the assignment references associated with a matrix (just the reference, or unique id, not the entire assignment)
2. Upon import valid assignments will be included in the matrix cell (if in the same worksite, see next note)
3. Upon import, if the matrix was exported from a different worksite than is current, the assignment references will not be used. This is to maintain consistent behavior with how assignments may be added (currently only within same worksite). This restriction can be removed once assignments can be added from any worksite.

Implemented for both matrices and wizards as described.

Updating fix version to 2.5.0.003 as tag was just cut and this ticket was included.

Closing subtasks for 2.5.0 release.