moving data between sites
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.