Suggested changes on Data models.
diff --git a/SocialFeaturesMelangeGSoC2010.wiki b/SocialFeaturesMelangeGSoC2010.wiki index 2ab916c..bc70139 100644 --- a/SocialFeaturesMelangeGSoC2010.wiki +++ b/SocialFeaturesMelangeGSoC2010.wiki
@@ -70,6 +70,10 @@ * user_page_status - *StringProperty* * tags - *StringProperty* (for filtering in maps+calendars searches) +----- +Comment (madhu): I think you must really use tag framework in Melange here and use the tag property. +----- + The User page feature should be in one of the following states implied by the user_page_status property of the model. @@ -164,16 +168,30 @@ * time - *DateTimeProperty* * tags - *StringProperty* +----- +Comment (madhu): + # Same as above. You may want to use tag framework for tags. + # Also you may want created by and created on along with modified by and modified on properties. + # Also you may want to use http://code.google.com/appengine/docs/python/datastore/typesandpropertyclasses.html#GeoPtProperty GeoPtProperty here instead of Lat Lng location float properties. The reason why it was used in previous model was because this property was not in Appengine then. But now we have! + # You also want reference to program. +----- + An event can only be published in one calendar(i.e. program calendar or org calendar). If is_org_event is true, then it will be published in the current user's org calendar, if is_org_event is set to false, then the event will be published in the program calendar. These two status properties differentiate the program admin and the org admins. +---- +Comment (madhu): Just to warn you, a user may be involved with two or more Organizations. For example, Sverre is mentoring two students this time :P One for Melange and another for Git +---- + Based on the calendar(org or program) in which the event is meant to be published, the status property is set to either of the three values. * *is_requested* : If the current user is not the owner of the calendar where the event is to be published, then this state is set by default. When it is approved by the owner, this is set to is_approved. * *is_approved* : If the current user is the owner of the calendar where the event is to be published, then this state is set by default. Else if the event is approved by the owner, this state is set for the event. * *is_declined* : If the calendar owner chooses to decline an event request this state is set. - +----- +Comment (madhu): For clarity reasons I think it is better to name these values *requested*, *approved* and *declined* since they are not really Boolean fields but a 3-state property. +----- === APIs & Libraries === @@ -183,6 +201,9 @@ * GeoModel (filtering locations, tentative) (more coming up...) +----- +Comment (madhu): Want to see them soon. Esp. jQuery plugins for tabbed pages since you are starting with User pages in two days. +----- == Use-Case Diagrams ==