#7963 NORM 9.1.0: Handling of new user info data

[Zarro Boogs per Child]

#7963: Handling of new user info data
------------------------------+---------------------------------------------
   Reporter:  epmfairweather  |       Owner:  ypod         
       Type:  defect          |      Status:  new          
   Priority:  normal          |   Milestone:  9.1.0        
  Component:  cerebro         |     Version:  not specified
 Resolution:                  |    Keywords:               
Next_action:  never set       |    Verified:  0            
  Blockedby:                  |    Blocking:               
------------------------------+---------------------------------------------

Comment(by ypod):

 Precisely this was the goal of new_node: to signal whether this a change
 in info stored or a new node. This sounds like a good catch. I will look
 into it in the w/e.


 epmfairweather wrote:

 In any case this parameter's value seems to be of limited use. What would
 be more useful would be an indication of what user info was new or had
 changed rather than the user having to determine this by themself from the
 large JSON encoded dictionary of info provided by the first parameter.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7963#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system