|
|
|
Created:
16 years, 6 months ago by thelevybreaks Modified:
10 years, 1 month ago Reviewers:
james.k.crook, srabbelier, ljvderijk CC:
ajaksu Base URL:
http://code.google.com/p/soc Visibility:
Public. |
(Update: Looking into problems with getting patches formatted correctly....)
Whenever an evaluation is given, two surveys are actually given. One is for mentors for a program, and one is for students for a program. For each of these surveys, the student and mentor need to take the survey once for each project that they have active with the program.
While it might usually be possible to figure out which mentor survey_record fits with which student survey_record, there are some cases where it's not possible, and it's important enough so that it deserves to be stored.
Furthermore, this could be an opportunity to easily track the change in status of a project in relation to the survey or throughout the program.
The model that I created in response to this issue is called SurveyRecordGroup.
Patch Set 1 #
Total messages: 3
|
thelevybreaks
|
16 years, 6 months ago (2009年06月23日 09:19:27 UTC) #1 | |||||||||||||||||||
Can you create a new issue to replace this one, it's broken somehow :(.
On 2009年06月24日 05:19:01, SRabbelier wrote: > Can you create a new issue to replace this one, it's broken somehow :(. Yes, I'm going to have to get the update.py utility working to do this properly. Unfortunately I'll be afk most of today so I submitted a patch to the list until I can get them working on this site.