@cmelo and I looked into this, and the conclusion is that we will not be doing this for the time being, and that collaborative contributions tracking (CCT from now on) will be implemented with an ad-hoc boolean flag instead. The reason for this is that, while CCT is in principle a kind of tracking tool, it is also very different from the P&E Dashboard, the only currently available tracking tool. When implementing support for the Dashboard, we made the code extensible because we knew we might want to use it for other tools in the future; however, we still optimized for the then-current use case. CCT is not a good candidate because there are too many differences with the P&E Dashboard, including:

• It is an internal tool, not external
  • In particular, it does not need an "identifier of the event within that tool" (course slug for the P&E Dashboard): it's the event ID
• There are no "sync status" or "last sync time" (partly because it's an internal tool)
• It does not track participants
• Its status wouldn't be shown in EventDetails

So, as anticipated, we will use a boolean flag for the time being. This can be changed later, if we want to add more tracking tools.