[Collective-versioning] Re: Import/Export use cases

[Duncan B. <dun...@su...>]

Vincenzo Di Somma wrote:

> The use cases are:
> 
> 1) Once exported the content loses all the information about multisite.
> 
> 2) The content preserves the information. That means it assumes that
> when imported nothing around it is changed.
> 
> I don't find the n. 2 realistic.
> Any other consideration about this topic?

Use case number 2 is the one we are most likely to need in the short term. 
When we release a new version of the system we need to migrate all of the 
content from the old version of the cms and the old public sites.

The current multisite implementation includes some code and a ui for fixing 
up this information if it is missing after an import. i.e. it would be 
quite capable of taking a site imported assuming use case #1 and adding 
correct multisite information. So, if we only work to use case #1 there 
isn't a problem as use case #2 is already handled.

However, I can't see how we implement user case #1.

The problem is that what we really want to do is to mark certain attributes 
to not be exported (or to strip them on import, but export would be 
better), but so far as I am aware Zope doesn't give us any hooks for either 
the export or the import to allow us to restrict what it transfers.