- Mailing Lists
- Contributors
- Re: [RFC] marketplaces connector module
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: [RFC] marketplaces connector module
Hi Xavier, hardcoded mappings are easily getting a huge mess. I'd definitely suggest a "per feed" export mapping that can be configured using the backend. Best Frederik Am Freitag, den 18.10.2019, 14:11 +0000 schrieb Xavier Brochard: > Hello > > We are working on a little maketplaces connector for small companies. > It > connects Odoo with a feed provider which will transform data to > export towards > marketplaces, prices comparators, etc. Everything is done with CSV > files > export-import because a lot of feed provider, specially small ones, > work like > this. > It was previously discussed in Roadmap Odoo 13 for retail industry : > https://github.com/odoo/odoo/issues/28179#issuecomment-462323744 > (and next comments). > > First step is to have something working with Iziflux, a little french > feed > provider. But... How does field mapping should be build ? > I ask because looking at OCA/connector-lengow (Lengow is a big feed > provider), > a lot of code is not Lengow related, but field mapping is hard-coded > in a file. > It's a pity. > I don't care if first step use hard-coded mapping. But later I would > like to > have something as generic as possible because all feed providers use > nearly > the same data and thus the connector should be easily adaptable. > > Should we use a form ? > or simply a CSV to put in the module directory ? > or hard coding is good ? > or something else ? > > (please CC me) > > -- > Librement, > Xavier Brochard / zeroheure > « La liberté est à l'homme ce que les ailes sont à l'oiseau » > (Jean-Pierre Rosnay) > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 04:26 - 18 Oct 2019
Reference
-
[RFC] marketplaces connector module
Hello We are working on a little maketplaces connector for small companies. It connects Odoo with a feed provider which will transform data to export towards marketplaces, prices comparators, etc. Everything is done with CSV files export-import because a lot of feed provider, specially small ones, work like this. It was previously discussed in Roadmap Odoo 13 for retail industry : https://github.com/odoo/odoo/issues/28179#issuecomment-462323744 (and next comments). First step is to have something working with Iziflux, a little french feed provider. But... How does field mapping should be build ? I ask because looking at OCA/connector-lengow (Lengow is a big feed provider), a lot of code is not Lengow related, but field mapping is hard-coded in a file. It's a pity. I don't care if first step use hard-coded mapping. But later I would like to have something as generic as possible because all feed providers use nearly the same data and thus the connector should be easily adaptable. Should we use a form ? or simply a CSV to put in the module directory ? or hard coding is good ? or something else ? (please CC me) -- Librement, Xavier Brochard / zeroheure « La liberté est à l'homme ce que les ailes sont à l'oiseau » (Jean-Pierre Rosnay)
by xavier - 04:10 - 18 Oct 2019-
Re: [RFC] marketplaces connector module
Hi Xavier, hardcoded mappings are easily getting a huge mess. I'd definitely suggest a "per feed" export mapping that can be configured using the backend. Best Frederik Am Freitag, den 18.10.2019, 14:11 +0000 schrieb Xavier Brochard: > Hello > > We are working on a little maketplaces connector for small companies. > It > connects Odoo with a feed provider which will transform data to > export towards > marketplaces, prices comparators, etc. Everything is done with CSV > files > export-import because a lot of feed provider, specially small ones, > work like > this. > It was previously discussed in Roadmap Odoo 13 for retail industry : > https://github.com/odoo/odoo/issues/28179#issuecomment-462323744 > (and next comments). > > First step is to have something working with Iziflux, a little french > feed > provider. But... How does field mapping should be build ? > I ask because looking at OCA/connector-lengow (Lengow is a big feed > provider), > a lot of code is not Lengow related, but field mapping is hard-coded > in a file. > It's a pity. > I don't care if first step use hard-coded mapping. But later I would > like to > have something as generic as possible because all feed providers use > nearly > the same data and thus the connector should be easily adaptable. > > Should we use a form ? > or simply a CSV to put in the module directory ? > or hard coding is good ? > or something else ? > > (please CC me) > > -- > Librement, > Xavier Brochard / zeroheure > « La liberté est à l'homme ce que les ailes sont à l'oiseau » > (Jean-Pierre Rosnay) > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 04:26 - 18 Oct 2019
-