Create a Database design for the Incident concept

[RobertLRead]

This is an issue to represent thought on an "incident", including the ability of people to enter data requests. I assume this should be created as a diagram at some level.

Concepts that should be modeled:

• The Incident Itself
• Needs Expressed which are relevant to this Incident
• • These should be classified as OKHs that we have, or
• • Items which are wanted but we do not know how to make.
• Decorations of the Incident, such as:
• • Type
• • Date
• • Location
• • History
• • Current Issues
• • Fulfilled needs
• • Needs which are obsolete, though not fulfilled by our system.

Onchana did much of this work already by defining a useful screenshot:

[RobertLRead]

I've tried to make a little diagram of some ideas here:
https://docs.google.com/drawings/d/1r1XFvaTgS53Zdi4tc124kprqlx5JBpJinRMcSZCrAco/edit?usp=sharing

[RobertLRead]

@touchthesun James ask me to ask you, Nathan, to review this informal database diagram:

[Onchana01]

[RobertLRead]

@AnsibleBat Do you believe this issue can now be closed? Do we have a working database design of tables that we can write code against?

[Jbutler-helpful]

@RobertLRead I think this was done by @AnsibleBat and merged to main if I a not correct by PR #89 (please confirm)