moving data between sites

Bug #101229 reported by Martijn Faassen on 2004-09-28
Affects Status Importance Assigned to Milestone

Bug Description

This issue is to remind us that the ability to move data between sites is
important. The most urgent issue in this domain is issue 1110.

Some aspects of Silva rely on path information; in particular ghosts, the
catalog, and railroad objects. I believe ghosts and the catalog are more or less
okay, as long as data that is moved into a new site gets cataloged -- I think it
is but we need to verify this.

Railroad objects may be more complicated, as references to railroad objects in
the CMS are retained in the railroad repository itself. There needs to be some
way to inform railroad repository that the owner CMS for some objects is now a
different site, if I understand this architecture well.

I expect in the future we'll move to a system where the new-style XML
export/import system will be used for staging purposes. It is more easy to build
in options in this for all sorts of use cases than in the zexp case.

Martijn Faassen (faassen) wrote :

Since the immediate issue has been resolved and we won't be able to resolve any
other (potential) issues with the imminent Silva 1.1 release, I'll move this
along to Silva-1.2 (and keep it at Silva-future too).

Sylvain Viollon (thefunny) wrote :

The official way to exchange data between different Silva is to use the XML import and export feature, even if those sites are located inside the same Zope instance. Nothing less is supported.

Changed in silva:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers