#6254 HIGH Never A: When resuming object in different activity, old activity id is reused

[Zarro Boogs per Child]

#6254: When resuming object in different activity, old activity id is reused
-------------------------------+--------------------------------------------
  Reporter:  bert              |       Owner:  tomeu                            
      Type:  defect            |      Status:  new                              
  Priority:  high              |   Milestone:  Never Assigned                   
 Component:  journal-activity  |     Version:  Development build as of this date
Resolution:                    |    Keywords:  Update.1?                        
  Verified:  0                 |    Blocking:                                   
 Blockedby:                    |  
-------------------------------+--------------------------------------------
Changes (by Eben):

 * cc: marco, tomeu (added)


Comment:

 Well, I think I need a little more clarification on the bits that back
 this system up.  In a sense, we need 3 separate identifiers.  The first
 identifies the kind of object (akin to a type code; I assume we just use
 MIME).  The second identifies an associated activity (akin to a creator
 code; I have no idea how we handle this).  The last is what's been known
 as the activity_id, which tracks the shared collaboration around a given
 object/activity (which has no mapping to current systems).

 I think the confusion here lies somewhere between the activity association
 and the activity_id, which I think are distinct entities.  In fact, it
 might be clearer to adjust the terminology and call it a collaboration_id
 instead, to detach it from any single Activity:  it refers to an activity
 in the general sense, rather than to the chunk of code which defines a
 ''single'' Activity on the laptop, the semantics of which aren't very
 clear.

 Using these new collaboration semantics, it would be clear that a
 collaboration can continue on a painting, regardless of what Activity the
 children use to work on it. Marco, Tomeu, how does this match what's
 currently under the hood? (For the record, I believe the reason
 collaboration_id wasn't chosen in the past was because it implies that an
 activity is shared.  This isn't the case, so we have to accept the notion
 of a single-child collaboration -- or the potential for future
 collaboration -- when using this terminology.)

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