Use Import Section in Update Engine does not update anything

Documenting the Import Section.

One of the classical use case required by customers is to be able to export a ctn (or a ctnlist, a whole sub-section or a whole site), provide it to a 3rd party translator and reimport it afterwards. Of course they do not want to have duplicates afterwards or similar. If the "translator" also act as a "speell-typo-checker" the existing content in the current lang, if updated in the XML file, should be also updated accordingly on reimport.

So I just created a small container (Main Description ctn on the News Template) in EN only and just a basic "FR" word in FR in order to get some export schema to reuse. Then I opened the FR export file, modified my big text (or description metadata field) and reimported it. It looks like working. No error. No warning. The engine close.... But nothing updated on my screen in FR. Same is true when opening the engine again (nt a cache issue).

I then removed all the JCR id or other kind of non updated metadata field in order to only keep the modified ones. I did the same operation again. Similar behavious. Everything looks ok. But nothing is imported.

Finally I created a new "News page" and imported the same (reduced and cleaned-up) file on the empty ctn. Similar behaviour. It close the engine. But nothing on the page. The ctn does not appear (but is present on the ctnlist). On refresh you suddently see it. So in such a use case there are cache flushing issues.

I redid my import on the update engine after having modified my initial import file. Same as previous behavious: nothing is updated but the engine closed "successfully".

So:

• If import does not work on the update engine let's remove it from the update and only keep it in the New engine
• If the import encounters some errors let's display them in a kind of "warning pop-up". Do not remember that editor do NOT have access to the console.

More globally speaking, more and more customers are asking to us about they could export a site or a section, give it for translation to a 3rd party professional translator and reimport it on the exsiting site once translated (or the typo cross-checked). Support for more standardized XML translation schema such as XLIFF would be great but being already able to access to any kind of XML data with some possible way to easily update content from any XML editor would be already great.

BTW: this is not celar at all the process to use in such a use case: should the editor keep the JCR id values? Should he removes them? Should he remove all the non-updated fields? What if he reimport the container with the old modification date? Does a new modification date (or a new last contributor name) is enforced? etc.... A little more doc and explanation would be useful.