Joining a team causes expertiza to lose everything you've done on your previous topic about expertiza

[efg]

I think the right thing for now is to prevent someone from changing teams after their team has submitted work (either by submitting a file, a URL, or writing on a wiki).

[efg]

Evidently this is the same as #45.

[nilbus]

Are you saying that this is the cause of #45? If you could tell how you know that, that would be helpful in debugging this.

[efg]

The issue there, I think, is that you can only be on one team for an assignment. If you change teams during the assignment (e.g., if someone didn't do a wiki chapter in the 1st half of the semester & needs to do 2 topics in the second half), then the 1st team is lost, and there is no way to fetch the score the student received (except via his/her teammate, if he had one).

I'm not sure if this is a bug or a bad feature, though.

-Ed

nilbus [email protected] 7/16/2011 5:46 PM >>>
Are you saying that this is the cause of #45? If you could tell how you know that, that would be helpful in debugging this.

Reply to this email directly or view it on GitHub:
#5 (comment)

[efg]

I do not know that this is the cause of issue #45. I just suspected that it was. For if someone abandons a topic and joins a different team after having some of his work reviewed, the reviews will have been done for a team that no longer exists (his team effectively ceased to exist when he joined another team).

Does this help explain it?
Ed

nilbus [email protected] 7/16/2011 5:46 PM >>>
Are you saying that this is the cause of #45? If you could tell how you know that, that would be helpful in debugging this.

Reply to this email directly or view it on GitHub:
#5 (comment)

[yangsong8]

In current Expertiza, one can still leave a team after this team has made a submission and got reviewed.
The record in teams table got deleted, too. The review response map for the reviews on this team also got deleted. So the last person's leaving is gonna cause a cascading delete on a lot of records.

I am not sure if this is the correct thing to do, but we should not force the last person to stay on the team even the artifact has been reviewed, right?

[yangsong8]

Updated: when the last team member leave but the work have been reviewed, the team record in db stays.