EVASS

Hej Claudio--

a very early prototype, just to explain the principle:
1) renamed "ev" into "evr" (as in "Evacuee Registry").
I think it could eventually become a variant of "dvr", but to be able to decide that I really need more insight into your use-cases first.
2) introduced "evr_case", "evr_medical_details" and "evr_background" as EVR-specific components to the standard pr_person resource. Other data like physical description, identity, and personal details do already exist so can be re-used (we may need to customize them a little bit, though). This is certainly not comprehensive, so will need further refinement.
3) created a person and a group controller for EVR, based on the standard pr/person controller. Some of the sensitive fields are inlined here, but they would automatically hide if the user is not permitted to see them. The forms and lists may need customization, and of course there should be filter forms - working on that. I suppose we want pivot table reports and maps here? So we should use summary instead of plain list views.
4) I put in @todo's where I think we could extend this - namely the CR shelter registry should introduce a cr_shelter_person link table (probably with registration details) and then make this a component both of persons (the current shelter of a person), and shelter (the current occupants of a shelter).

I hope you can recognize the general architecture here - EVR as extended PR to register evacuees, CR as separate module to manage shelters - we will probably also want to add HRM (to manage staff), SUPPLY/INV (to manage inventories of supply items), and perhaps a few other things but those can come later.

You can probably not auto-merge this - simply because I rebased my working branch on current trunk. Once you did the same, you will be able to merge it (if you like it).

I will add more commits in the morning - but for now I'm tired and need some sleep.

Regards,
Dominic