I’ve just written about project snapshots at Best practice: Keeping project snapshots .
In fact, no snapshot was taken of our project when we first went to print in 2010 (which was before I was involved in the project), but now I would like to take one. My question is: what is the best way to do this after the fact? It seems I have two options:
(Let’s say that the printed version matches the project at 5 Dec 2010 in the Project History.)
I could revert the relevant books to the 5 Dec 2010 point, import these books into the new project, and then undo the revert (by reverting to just before the revert). I could do an S/R before and after all this, but not in the middle, so that no other user is shocked by seeing the books reverted to their seven-year-old versions.
Still, this seems to have at least two issues and dangers:
- I now have two unnecessary points in the project history, that will stay there for evermore;
- In our project, it’s hard to ensure that no-one will edit while maintenance is taking place, because we have lots of users in diverse locations; if I email them, I’d have to insist on a reply from every user so that I’d know they’ve read the announcement. And because they are in a number of widely varying timezones, I also can’t pick a time of day when it’s unlikely that anyone is editing. If someone does edit, I’m concerned that there may be merge conflicts as a result of verses being changed by both me and another user.
The second possibility is based on the fact that you can view an old version of the text in one panel of the Compare Texts window. If I switch off View by Chapter, I can cut and paste whole books from this panel into a new project.
The problem is that it’s a lot of work if I need to copy multiple books.
Is there a better way?