openerp-connector-community team mailing list archive

[David Beal <david.beal@xxxxxxxxxxxx>]

Hi Leonardo, all,

* Here is example of imported datas with belspeed logistic center:
{60: {
     'picking': {},
     'moves': [{'carrier': u'DHL', 'product_id': 7, 'product_qty':
1.0}, {'carrier': u'DHL', 'product_id': 6, 'product_qty': 1.0}]}}

60 is the picking_id
if there are general infos in the picking, there are in picking dict

each picking item is stored in one buffer

This is just an example, but seems convenient to me of course. Other
points of views ?


* Extraction from external FTP and file reading are done in 2 steps
(distinct cron for each) : no archive folder for failed reading file
but a text field in 'file.document' to put error reporting. Maybe we
may consider to send this error reporting automatically (by 1 click
button) to logistic center, but perhaps by mail and in an other module


* Other point (@guewen): connector_logistic_center depends on
ecommerce addons because product connector tab is defined in this
branch, and I have to customize this view. Maybe should we consider to
define this view in product-attribute branch

Thanks

David BEAL, Akretion

2014/1/3 Leonardo Pistone <leonardo.pistone@xxxxxxxxxxxxxx>:
> Hi all,
>
> this general message is just to bring the everybody who is interested in the
> discussion about using the connector for generic csv imports. Like for
> e-commerce, this can bring realiability, ability to catch many errors (in
> retrieving the file, parsing, inserting into the db etc) and repeat what
> went wrong if necessary.
>
> Apart from the connector itself, there is already some excellent work in
> progress by Akretion, at:
>
> * https://code.launchpad.net/~akretion-team/file-exchange/file-exchange
> * https://code.launchpad.net/~akretion-team/+junk/logistic-center
> * https://code.launchpad.net/~akretion-team/+junk/poc-import-data
>
> I gave those modules a try, and here are some points I wish to discuss.
> First of all, well done.
>
> * If I inderstand correctly, we are spawning a job to import each line of
> the file. That line is stored in the "buffer", associated to the job. Still,
> some data needs to be imported in chunks (invoices with lines, for example).
> That needs a kind of multi-line buffer, probably not with a JSON dictionary
> "data" field, but something like a list of lists (i.e. a table). What do you
> think?
>
> * The file-exchange modules has the ability to move imported files to the
> "archive" folder. Should we have also a place to move the files we can't
> read?
>
> Thanks!
>
> --
> Mailing list: https://launchpad.net/~openerp-connector-community
> Post to     : openerp-connector-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-connector-community
> More help   : https://help.launchpad.net/ListHelp
>