Author Topic: Best way to store datas (Read 328 times)

Matthias de MAUROY - CYIM · March 13, 2014, 08:26:39 am

Hello everyone.

I'm about to import relationships. But before doing so I want to be sure that I use the correct way to store those datas.

We are working for an Organisation that includes working teams such as "special commity" or "decision's board".

We want to save the "status" of each member of each working team, so we think that Relationship gives us the answer to our problem. Are we in the correct way ?

To save all of those "working teams" which solution is the best ? contact sub-types ? tags ? Maybe we should use groups and ACLs with it ?

We need the very best way to keep those informations sorted and readable.

Need your help

Thank's !

Matthias de MAUROY - CYIM · March 31, 2014, 01:52:48 am

Re-reading my post, I realize i forgot to include lot some important context information :

For the relationships :

The relationships represent a role in a team, for example "President" of " "executive commity". A role is kept for one or several years.
A person can be part of several teams
We need to keep an history of the role the persons had. i.e. : X was executive commity president from 01/01/2000 to 31/12/2005 and he also was special commity secretary from 01/01/2007 to 31/12/2008

So I think CiviCRM's relationships are the way to go.

For the working teams :

We need to differentiate the working teams from the other organizations
We need to link people to the teams

So, what would you recommend ?

Creating contact subtypes (organization ou household) ?

OR

creating tags ("commity", "boad",...) to apply to the working team contact ?

Thanks in advance for your advices
Matthias

CiviCRM Community Forums (archive)

News:

Author Topic: Best way to store datas (Read 328 times)

Matthias de MAUROY - CYIM

Best way to store datas

Matthias de MAUROY - CYIM

Re: Best way to store datas