Point-of-Contact, Organization, Incident Relationships

[GoogleCodeExporter]

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 reported on code.google.com by v...@aarontitus.net on 13 Jan 2013 at 11:27

[GoogleCodeExporter]

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' } }

Original comment by joshua.eric.turcotte on 21 Jan 2013 at 6:41

[GoogleCodeExporter]

Joshua, I agree.

Original comment by v...@aarontitus.net on 30 Jan 2013 at 12:44

[GoogleCodeExporter]

Implemented. 
Each Contact has one and only one organization.
Each Organization has one and only one Event

Original comment by andy.n.g...@gmail.com on 17 Feb 2013 at 4:32

[GoogleCodeExporter]

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.

Original comment by v...@aarontitus.net on 18 Feb 2013 at 5:14

[GoogleCodeExporter]

Also, in case it wasn't clear- one organization may have multiple contacts.

Original comment by v...@aarontitus.net on 18 Feb 2013 at 5:30

[GoogleCodeExporter]

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 comment by andy.n.g...@gmail.com on 18 Feb 2013 at 10:01