J
Jake M via AccessMonster.com
hI just started working for the ACLU. To organize our cases, we need to
create a database. The process works as follows: We intake many phone calls
and gather general info (name, addr, nature of claims etc.). We dispose of
the majority of the phone calls by refering them elsewhere. We then evaluate
few seemingly worthy complaints and send some of them to be approved for
representation by our legal committee. If legal committee approves a matter,
it becomes an open case and gets a case number. When we are done with the
case, it becomes a closed case.
Now is the question: How should we design the db? Should there be a table for
initial intakes only and a separate table for cases? How do I link them?
intake_number will become the unique id throughout its life at the
organization. Or should there two tables: one for intitial intakes and one
for the ontakes that became cases? How to I links them etc... Thank you
all for your responses and suggestions!
create a database. The process works as follows: We intake many phone calls
and gather general info (name, addr, nature of claims etc.). We dispose of
the majority of the phone calls by refering them elsewhere. We then evaluate
few seemingly worthy complaints and send some of them to be approved for
representation by our legal committee. If legal committee approves a matter,
it becomes an open case and gets a case number. When we are done with the
case, it becomes a closed case.
Now is the question: How should we design the db? Should there be a table for
initial intakes only and a separate table for cases? How do I link them?
intake_number will become the unique id throughout its life at the
organization. Or should there two tables: one for intitial intakes and one
for the ontakes that became cases? How to I links them etc... Thank you
all for your responses and suggestions!