Core App and Data model

[infohata]

We have an old data model consisting of 7 tables, which we can relate to the following object groups:

Geographical Objects

• countries
• regions
• cities

Connecting People

• members
• relations
• comments
• messages

That is all it is and that is more than fine for the old system. It was functioning fast due to little joins and so on. However, the naming convention of the fields is not existing, and indexes could be improved. In python, we have a convention to write data structures and code which would be humanly readable independently from which part of the code you start to read it.

I will suggest the new data structure and implement it into hc-core Django app. It will be, in fact, the main app of the project and will be most likely the dependency to everything. However, I suggest not to make an elephant out of it and implement every function to it's own app.

We'll see how it goes. It's a start

[infohata]

Implemented into hc-3-core-app-data-model with these changes:

• comments and messages merged into the same data model. This allows to track changes in people relationships, including counting the repeated visits, etc.;
• multiple addresses now are possible with their own properties for hosting options
• contact methods are now abstract
• few other minor abstractions
• fields now are humanly readable in the data model, with proper explanations and UI labels already implemented for most of the cases