Contents | Sites Contents: Some document informations are lost with import and synchronize operations

[azayati]

When trying to perform Import or Synchronize operations of Contents | Sites Contents category with any filter and option, these document informations are lost:
-/ The association between document and categories.
-/ The association between document and tags.
-/ The watch/unwatch actions on the document.

[thomasdelhomenie]

The association between document and categories.

In order to correctly synchronize/import categories, the category trees need to be sync/imported first. If the category tree does not exist when the contents are sync/imported, the contents can't retrieve their categories.
Which means that we should either :

• exclude the categories from the content synchronization. Synchronizing categories would only be done through ECMAdmin/Taxonomy.
• automatically synchronize the category trees when the user chooses to export the whole site or checks the option "include taxonomy". In this case, the synchronization will include everything done in the Taxonomy synchronization. I guess this is the way to go as it simplifies the synchronization process.

WDYT ?

The association between document and tags.

This association is not stored on the contents. We need to import another nodes tree (collaboration:/tags). Do we sync it automatically or de we add another option ?
WDYT ?

The watch/unwatch actions on the document.

I can't reproduce. When I watch a content, then synchronize it, I still see the subscription enabled (which is logical as it is stored in the properties of the content).

[azayati]

-/ The association between document and categories:
I think that the second solution is the best. But I still have "There are no categories." message when I try to access the list of content's categories.
-/ The association between document and tags:
I think that we should add tags as a category for the different operations Export/Import/Synchronize.
When we want to Export/Import/Synchronize a content, we should take into account automatically its associations with tags (no option) (the tags must be implicitly synchronized if they don't already exist in the target server)
-/ The watch/unwatch actions on the document.
It's OK