diff -r aae25d2b4464 -r 3c1e16637ad7 app/soc/models/question.py --- a/app/soc/models/question.py Thu Nov 20 18:50:30 2008 +0000 +++ b/app/soc/models/question.py Thu Nov 20 19:43:31 2008 +0000 @@ -44,12 +44,12 @@ work.reviews: even Questions can be "reviewed" (possibly commented on during creation or annotated once put into use). - work.partial_path: used to scope (and, when combined with + work.scope_path: used to scope (and, when combined with work.link_id, uniquely identify) a Question in the same way the property are used with Documents, etc. work.link_id: used to identify (and, when combined with - work.partial_path, *uniquely* identify) a Question in the same way + work.scope_path, *uniquely* identify) a Question in the same way these properties are used with Documents, etc. work.content: the Question text, asked to the respondent @@ -86,10 +86,10 @@ when these ideas are implemented in the views and controllers; they are here now so that the concepts will not be lost before that time. - The recommended use for the combination of work.partial_path and + The recommended use for the combination of work.scope_path and work.link_id is to keep the *same* link_id when copying and modifying an existing Question for a new Program (or instance of a - Group that is per-Program), while changing the work.partial_path to + Group that is per-Program), while changing the work.scope_path to represent the Program and Group "ownership" of the Question. For example, if a Question asking about prior GSoC participation needed to have an additional choice (see the choice_ids and choices properties @@ -116,7 +116,7 @@ Question:google/ghop2009/gsoc_past_participation To get the combined results, query on a link_id of gsoc_past_participation. For more targeted results, include the - partial_path to make the query more specific. + scope_path to make the query more specific. Question creation to permit use cases like the one above is going to be a bit of an "advanced" skill, possibly. "Doing it wrong" the first