Re: [tryton] Re: Contact Mechanisms - per Party versus per Address/Contact

2013-06-14 Thread Guillem Barba Domingo
El 13/06/2013 10:58, Cédric Krier cedric.kr...@b2ck.com va escriure:

 On 13/06/13 10:38 +0200, Axel Braun wrote:
  Am Donnerstag, 13. Juni 2013, 01:26:25 schrieb Chris Larsen:
   Thanks everybody for your very helpful replies. Cédric, allow me to
explain
   how I understand Parties versus Addresses:
   If I have one big company as a customer, and this company is one
party,
   then I will invariably end up with several contacts within that parts
(=
   big company) with their related telephone numbers and other contact
   mechanisms.
 
  ..a prerequisite for proper contact management and CRM

 You just name it: CRM where C=party R=relation. So we just need
 relations between parties.

I think these are different questions. CRM refers to the management of
comunication (and more) with your customers (from the company's point of
view), not about the relationship between parties (data in your information
system). It is more generic than CRM.
Anyway, it isn't the discussion.

  I had a look at this repository as well, lots of useful stuff in it! Is
there
  a reason why these modules are kept away from the Tryton standard repo?

 The main issue is the mixin of address and contact/party.

The Tryton Standard Repository is for generic modules, which could be
considered *framework* (sometimes it is a subjective consideration).

In TrytonSpain there are modules that could be included in this definition
(and we hope they will be moved to tryton's community infrastructure, in a
similar way that Nereid), others which are so generic to be useful for
other ERP implementors and some are specific for Spain. All of them are
opened to community feedback (and contributions ;-)).

Some months ago was created the tryton-contrib list [1] to discuss and
manage these kind of modules; modules which are part of Tryton's ecosystem
but not par ot its core. For now, this list is the unique infraestructure
to *manage* these modules (each member is doing in his own way, we chose
Bitbucket and create a community team TrytonSpain). Something like *Apps
website* where have a complete list of all contrib modules is an
interesting idea which has discussed a little bit. Raimon has developed a
first aproximation [2][3] and I wish that in a medium term I'll extend
these idea (now we have other priorities).

*To summarise*, TrytonSpain modules are part of Tryton ecosystem. Now, we
are in the spring to have a usable spanish localization so we decided to
develop some of our requirements in our own way assuming that the modules
which will be included in Tryton's core could be modified (improved). We
will work in these inclusion in the future. As Ramimon said before, if
there are someone interested in the inclusion sooner, he is free to open
the discussion in this list (or tryton-dev list [4]).

[1] http://groups.google.com/group/tryton-contrib/

[2] https://bitbucket.org/trytonspain/flask-appstryton

[3] http://apps.tryton-erp.es/

[4] https://groups.google.com/forum/?fromgroups#!forum/tryton-dev


Guillem Barba

NaN·tic


[tryton] Re: Contact Mechanisms - per Party versus per Address/Contact

2013-06-13 Thread Chris Larsen
Thanks everybody for your very helpful replies. Cédric, allow me to explain 
how I understand Parties versus Addresses:
If I have one big company as a customer, and this company is one party, 
then I will invariably end up with several contacts within that parts (= 
big company) with their related telephone numbers and other contact 
mechanisms.
Admittedly, this expands the role of the address-only idea, but it is 
undoubtedly useful. I think this is what raimonesteve and jmartin tried to 
refer to. Of course, I could also shift perspective, and link several 
parties to a super-party, where the party represents the company contact, 
and the superparty the company. 
The open question is what is the most user-friendly approach.
In any case, Merci beaucoup! and ¡Muchas gracias!; I will try to 
modules provided by Tryton Spain and Zigzag Media, and will report back.
Bests, Chris


Re: [tryton] Re: Contact Mechanisms - per Party versus per Address/Contact

2013-06-13 Thread Axel Braun
Am Donnerstag, 13. Juni 2013, 01:26:25 schrieb Chris Larsen:
 Thanks everybody for your very helpful replies. Cédric, allow me to explain
 how I understand Parties versus Addresses:
 If I have one big company as a customer, and this company is one party,
 then I will invariably end up with several contacts within that parts (=
 big company) with their related telephone numbers and other contact
 mechanisms.

..a prerequisite for proper contact management and CRM

 Admittedly, this expands the role of the address-only idea, but it is
 undoubtedly useful. I think this is what raimonesteve and jmartin tried to
 refer to. Of course, I could also shift perspective, and link several
 parties to a super-party, where the party represents the company contact,
 and the superparty the company.
 The open question is what is the most user-friendly approach.
 In any case, Merci beaucoup! and ¡Muchas gracias!; I will try to
 modules provided by Tryton Spain and Zigzag Media, and will report back.

I had a look at this repository as well, lots of useful stuff in it! Is there 
a reason why these modules are kept away from the Tryton standard repo? 

Cheers/Axel


Re: [tryton] Re: Contact Mechanisms - per Party versus per Address/Contact

2013-06-13 Thread Cédric Krier
On 13/06/13 01:26 -0700, Chris Larsen wrote:
 Thanks everybody for your very helpful replies. Cédric, allow me to explain 
 how I understand Parties versus Addresses:
 If I have one big company as a customer, and this company is one party, 
 then I will invariably end up with several contacts within that parts (= 
 big company) with their related telephone numbers and other contact 
 mechanisms.
 Admittedly, this expands the role of the address-only idea, but it is 
 undoubtedly useful. I think this is what raimonesteve and jmartin tried to 
 refer to. Of course, I could also shift perspective, and link several 
 parties to a super-party, where the party represents the company contact, 
 and the superparty the company. 
 The open question is what is the most user-friendly approach.

The all design of Party is based on this book:
http://www.amazon.com/books/dp/0471380237

I really think that using address as contact is a very big mistake. The
simpliest proof is that a contact could have many addresses.

The proper way is to create links between parties if large company
structure needs to be stored.

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: cedric.kr...@b2ck.com
Website: http://www.b2ck.com/


pgpjkCqvPaD0i.pgp
Description: PGP signature


Re: [tryton] Re: Contact Mechanisms - per Party versus per Address/Contact

2013-06-13 Thread Cédric Krier
On 13/06/13 10:38 +0200, Axel Braun wrote:
 Am Donnerstag, 13. Juni 2013, 01:26:25 schrieb Chris Larsen:
  Thanks everybody for your very helpful replies. Cédric, allow me to explain
  how I understand Parties versus Addresses:
  If I have one big company as a customer, and this company is one party,
  then I will invariably end up with several contacts within that parts (=
  big company) with their related telephone numbers and other contact
  mechanisms.
 
 ..a prerequisite for proper contact management and CRM

You just name it: CRM where C=party R=relation. So we just need
relations between parties.

  Admittedly, this expands the role of the address-only idea, but it is
  undoubtedly useful. I think this is what raimonesteve and jmartin tried to
  refer to. Of course, I could also shift perspective, and link several
  parties to a super-party, where the party represents the company contact,
  and the superparty the company.
  The open question is what is the most user-friendly approach.
  In any case, Merci beaucoup! and ¡Muchas gracias!; I will try to
  modules provided by Tryton Spain and Zigzag Media, and will report back.
 
 I had a look at this repository as well, lots of useful stuff in it! Is there 
 a reason why these modules are kept away from the Tryton standard repo? 

The main issue is the mixin of address and contact/party.

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: cedric.kr...@b2ck.com
Website: http://www.b2ck.com/


pgpOqzvcILKEy.pgp
Description: PGP signature


Re: [tryton] Re: Contact Mechanisms - per Party versus per Address/Contact

2013-06-13 Thread Raimon Esteve
2013/6/13 Axel Braun axel.br...@gmx.de:
 Am Donnerstag, 13. Juni 2013, 01:26:25 schrieb Chris Larsen:
 Thanks everybody for your very helpful replies. Cédric, allow me to explain
 how I understand Parties versus Addresses:
 If I have one big company as a customer, and this company is one party,
 then I will invariably end up with several contacts within that parts (=
 big company) with their related telephone numbers and other contact
 mechanisms.

 ..a prerequisite for proper contact management and CRM

http://apps.tryton-erp.es/sale_opportunity_mail/

Integrate Sale opportunity to communication client (by mail).

 Admittedly, this expands the role of the address-only idea, but it is
 undoubtedly useful. I think this is what raimonesteve and jmartin tried to
 refer to. Of course, I could also shift perspective, and link several
 parties to a super-party, where the party represents the company contact,
 and the superparty the company.
 The open question is what is the most user-friendly approach.
 In any case, Merci beaucoup! and ¡Muchas gracias!; I will try to
 modules provided by Tryton Spain and Zigzag Media, and will report back.

 I had a look at this repository as well, lots of useful stuff in it! Is there
 a reason why these modules are kept away from the Tryton standard repo?

Tryton ERP is a site to known Tryton in Spain. From Nan-tic,
Zikzakmedia and BTactic (active companies in Spain), every month we
are meeting (TUC - Tryton Unconference Catalonia) and we are working
to develop localization or required project modules.

If there are modules we develop available in this list and do you like
to include in tryton.org repos, we are agree. We don't have time to
longer discussions but we can spend a little time to feedback. It's
good to known modules from other people. For example, account_payment
is a module that two companies are developing from same blueprint.

Regards

--
Si us plau, NO adjunti arxius a les seves respostes. Li preguem que
integri el text al cos del missatge. Pot respondre usant NetEtiquete
que li ajudarà a seguir la conversa.
http://es.wikipedia.org/wiki/Netiquette

Por favor, NO adjunte archivos a sus respuestas. Le rogamos que
integre el texto en el cuerpo del mensaje. Puede responder usando
NetEtiquete que le ayudará a seguir la
conversación.http://es.wikipedia.org/wiki/Netiquette

Please, DO NOT send attachment files with your answers, just copy and
paste only the text you need to send into the body of your mails.
Repply using NetEtiquete. http://en.wikipedia.org/wiki/Netiquette


[tryton] Re: Contact Mechanisms - per Party versus per Address/Contact

2013-06-13 Thread Chris Larsen
I get your point - so basically you propose a three layer model, where
the current Party stands for Contacts, addresses are just, well,
addresses (physical, invoice, postal, whatever), and there is a meta-
level to aggregate Parties, as required. This does make sense and
offers the highest degree of flexibility, the only issue being that
the meta-level is not quite there yet. The crutch of using the
trytond-party_communication module works for most situations, but is
admittedly, in the above sense, not scalable.
Is there any work on the meta-level in the make? Thanks a lot
everybody!
Chris