Open aarontitus opened 11 years ago
From joshua.eric.turcotte on January 21, 2013 18:41:53 Given nosql; it may be sufficient to keep this set of relationships within the definition of each organization: (speaking json for a moment, but...):
organization: { ..., 'relationships': { '[other_org's_identifier]': 'sister', '[some_other_id]': 'parent' } }
From v...@aarontitus.net on January 30, 2013 12:44:05 Joshua, I agree.
From andy.n.g...@gmail.com on February 17, 2013 04:32:40 Implemented. Each Contact has one and only one organization. Each Organization has one and only one Event
From v...@aarontitus.net on February 18, 2013 17:14:54 While we don't need to jump through hoops to preserve the organizational integrity across incidents, it may be common for a single single organization to be associated with a Demo incident, a Drill incident, and a real incident.
I think that organizations will need to be able to be associated with more than one event.
From v...@aarontitus.net on February 18, 2013 17:30:46 Also, in case it wasn't clear- one organization may have multiple contacts.
From andy.n.g...@gmail.com on February 18, 2013 22:01:39 Yeah, one org can have multiple contacts. Also, I can see why we will eventually need an organization to have multiple events. I'll get on that.
Original author: v...@aarontitus.net (January 13, 2013 23:27:38)
One Organization may have multiple Points of Contact (this is a common scenario). By default, one Point of Contact should have one Organization (this is the common scenario); but I am willing to be talked into allowing a single point of contact to have a one-to-many relationship with organizations.
By default, one Organization is assigned to one Incident. This is the common and primary anticipated use-case. However, I would like the ability to assign a single organization to multiple disasters. I hope/anticipate this will not be necessary, but I'd rather add one more lookup table than box myself into a corner unnecessarily.
An Organization may have an "affiliation," "sister," "parent," or "child" relationship with another Organization. These relationships will permit automatic information sharing in the future.
These are foundational concepts, and will be used to implement several other features.
Original issue: http://code.google.com/p/sandy-disaster-recovery/issues/detail?id=141