Rainer Schöpf schrieb:
On Tue, 26 May 2009, Andreas Hartmann wrote:
> Rainer Schöpf schrieb:
>
> > > > I'd like to merge a small publication (15 pages) into a larger one.
> > I'm
> > > > aware that it is easiest to just copy the content over, but I'd like
> > to
> > > > preserve the version history. Does anyone know a simple way to do
> > that?
> > > > actually the version history should be preserved if you copy the
> > complete
> > > document directories, since the backup files are located in the same
> > > directory. You'll have to copy the corresponding sitetree fragments too,
> > but
> > > I think with 15 documents that shouldn't be a problem.
> >
> > Ah, good, thanks. I had assumed that I need to change the uuid of the
> > documents when I copy them.
>
> That's the big benefit of the "U"s in "UUID" – you can just merge two content
> repositories without worrying about collisions.
I understand that, but if I keep the small publication after copying the content
to the larger one, I have the same UUIDs in both. More like non-"U" then ;-)
Now there would still be two options: Should the new documents be forks
of the old ones, or references? In either case you'd need new documents
with new UUIDs. In the first case, you could introduce a "reference"
resource type, just containing e.g. an <inc:include> element.
If someone wants to do that, I'd recommend to take a look at the
importer module in the contributions area. I'm sure you can re-use a lot
of the code and just make some minor adjustments (import from a 2.0.x
publication instead of a 1.2.x publication).
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
