openerp-community team mailing list archive

[Nicolas Bessi <nicolas.bessi@xxxxxxxxxxxxxx>]

Hello,

Thank for the works provided

I have reviewed
https://code.launchpad.net/~nemry/partner-contact-management/7.0-partner-firstname/+merge/202713
except
some neat picks I'm ok with it principle.
This is true only in the scope of a simple partner first name, last name
management and to keep this module compatible with his original purpose.

But it appears that community needs a more generic module that will
replace/englobe partner_firstname and some others to address the full
problematic exposed in this mail thread.
Community should probably start a new blueprint and branch for that.

Regards

Nicolas





2014-01-31 Yannick Vaucher <yannick.vaucher@xxxxxxxxxxxxxx>:

> Hello,
>
> Just few though.
>
> About localization. I don't think we should be tied to it. After all in a
> country not every one comes from the same country.
> And you could even have someone ordering you something on your new e-shop
> (OpenERP or else ;-] ) ordering from outside of your country.
>
> What are needed in openerp is a name to put on an adress
> for correspondence and delivery to be read by the post office.
> And a name to address to the partner as 'Dear XXXX'.
>
> The tricky parts comes from connector with other applications (ie. magento
> with firstname lastname) when name is separated in an other way.
>
> Maybe the proper way should be a google contact like o2n relation on a
> name object with.
>
>  - the name
>  - a type (firstname, lastname, previous name, middle name, latin
> transcription, company name? pseudonyme and so on)
>
> Plus on other object or option to say which type of name should be used in
> which order (I think this should be configurable too)
> (twice the option once for delivery to construct a fullname and once for
> addressing to the partner)
>
>
> This would allow to define as well a firstname lastname split with birth
> name registred as it could simply be a fullname
>
> About sync with other application it should be the work of the connector
> to match to the right type. Having things separated makes it easier.
>
> Now the really hard part is to ensure everywhere we write a name in
> openerp, the name is correctly splitted. For exemple when you create a user.
> The simple way might be to make all needed create use a fullname type when
> it comes for exemple from a mail in CRM and make sure that on user type all
> views are changed to show a input for partner names.
>
> Otherwise we might need the following modules:
>
> partner_firstname
> partner_middlename
> partner_birthname
> partner_companyname
> and so on
>
>
> Cheers,
>
>
> On Thu, Jan 23, 2014 at 3:32 PM, Sandy Carter <
> sandy.carter@xxxxxxxxxxxxxxxxxxxx> wrote:
>
>> Hi thank you for your module,
>>
>> At first glance, on a technical standpoint, I have to give this +1 since
>> it passes OpenERP's tests, which partner_firstname doesn't.
>>
>> However, this module needs a bit of fixing since it is using deprecated
>> code (e.g. osv.osv, res_users(), "active", "demo_xml"), has PEP8 issues,
>> unused imports and uses _name unnecessarily.
>>
>> This can all be fixed easily.
>>
>> Le 2014-01-22 15:42, Yury Tello a écrit :
>>
>>> Hi Maxime, may be the module base_person would be an option.
>>> https://www.openerp.com/apps/7.0/base_person/
>>>
>>> Best Regards
>>>
>>>
>>> 2014/1/22 Maxime Chambreuil <maxime.chambreuil@xxxxxxxxxxxxxxxxxxxx
>>> <mailto:maxime.chambreuil@xxxxxxxxxxxxxxxxxxxx>>
>>>
>>>
>>>     Hello everyone,
>>>
>>>     I think we have few problems in regards to partner_firstname :
>>>     https://bugs.launchpad.net/partner-contact-management
>>>
>>>     As I am not convinced on the current implementation, I have started
>>>     a blueprint to discuss the options and decide on a solution :
>>>     https://blueprints.launchpad.net/partner-contact-
>>> management/+spec/partner-firstname
>>>
>>>     Feel free to join.
>>>     --
>>>     Maxime Chambreuil
>>>     +1 (514) 276-5468 #126
>>>
>>>
>>>     _______________________________________________
>>>     Mailing list: https://launchpad.net/~openerp-community
>>>     Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>>>
>>>     Unsubscribe : https://launchpad.net/~openerp-community
>>>     More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>>
>>> --
>>> Yury Tello Canchapoma
>>> TeraData SAC
>>> http://www.teradata.com.pe
>>> Telecomunicaciones, Software & Seguridad
>>>
>>> Telef.:(+51 1) 5362222 anexo 20
>>> Av. Arenales 395 Of. 507 - Lima 1 - Peru
>>>
>>>
>>>
>>> --
>>> Yury Tello Canchapoma
>>> TeraData SAC
>>> http://www.teradata.com.pe
>>> Telecomunicaciones, Software & Seguridad
>>>
>>> Telef.:(+51 1) 5362222 anexo 20
>>> Av. Arenales 395 Of. 507 - Lima 1 - Peru
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openerp-community
>>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openerp-community
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openerp-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Yannick Vaucher
> Business Solutions Software Developer
>
> Camptocamp SA
> PSE A, CH-1015 Lausanne
> Phone: +41 21 619 10 30
> Office: +41 21 619 10 10
> http://www.camptocamp.com/
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>