| Thread Previous • Date Previous • Date Next • Thread Next |
Hi Lionel, I mismatched purpose of the project, sorry. However, we should be agree about how store data in software.And, in order to store data for all, we have to know how every data is coded by regional and local people.
So, what localized data we wish manage in this project? I would like: 1. Local address format 2. Administrative division of countries (may be NUTS) 3. Postal code zone (aka ZIP) 4. Domestic bank, may be useful to check IBAN 5. VAT structure: all EU countries have similar VAT tax 6. Is vatnumer checked by OpenERP for all countries?7. Some countries, like Italy and Spain, have also the fiscalcode; in Italy a business may have 2 vatnumber
In my mind, a common country table defines data structure that every local team manages indipendently.
What do think about?Il 16/03/2014 14:55, "Lionel Sausin, de la part de l'équipe informatique Numérigraphe" ha scritto:
Le 15/03/2014 17:31, Info SHS-AV a écrit :This would fit better in a localization effort than in a data-oriented project in my opinion. I think I already read discussions on this topic but i can't find them right now.Agree.UE team should ask regional teams about domestic structure in order to build functional software.In example, for address, UE team shold require these info: Address format: Italy -> %(zip) %(city)s %(state_id)s ZIP format: Italy -> 5 digits ZIP - City relanshionship: Italy -> Many2Many State_id means: Italy -> NUTS3 State_id - City relanshionship: Italy -> One2Many ... and so on I am avaiable to prepare a form to gather infomations.Lionel _______________________________________________ Mailing list: openerp-community@xxxxxxxxxxxxxxxxxxx Post to : openerp-community@xxxxxxxxxxxxxxxxxxx Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
-- Antonio M. Vigliotti
| Thread Previous • Date Previous • Date Next • Thread Next |
