Merging different page versions
I am looking for a good process to merge different page versions. In my example we have a space version 1.0 which was published. We are already working on the next version 2.0. At the same time there are some minor changes to create a version 1.1 o publish it again. At the end the changes of version 1.1 should be merged to 2.0.
The merge feature of scroll versions does it per page; it can be decided which page version should be used after merging. That is fine. We need a way to merge the content of the different changed pages. It is totally clear that this cannot be done automatically. I am looking for a good process to do that.
Idea is to have an editor where we have 1.1 on one side and 2.0 on the other. Then for every change it has to be decided to copy the content from 1.1 to 2.0. What is the best practice to do it?
I was thinking of identifying changed pages with scroll version and then export changed pages in version 1.1 and 2.0 to Word and use Word as the editor. After merging the file in Word importing it to 2.0 again. Does it make sense or are there additional options?
-
Hi Ralf,
Thanks for getting in touch.
You're correct currently you have to decide which page version you want to keep when performing a merge. We have an open improvement to give users more control and have a merge functionality on paragraph level (see https://k15t.jira.com/browse/VSN-1783, please feel free to sign up to watch, comment on or vote for this issue. We'll then send a notification for every status update).
Instead of exporting the content to word and copy and paste it back and forth - wouldn't it be better to do the same within Confluence? I know that copy+pasting is not ideal, however I think that might be better than having another tool, work in their and then re-import this content to Confluence.
Working with multiple windows and maybe the Confluence Source Editor would help here. Don't you think that's the better alternative?As you can see there's currently no ideal solution (until we implemented VSN-1783).
Cheers,
Nils
Please sign in to leave a comment.
Comments
1 comment