Difference between revisions of "recover"

From GeneWeb
Jump to: navigation, search
m (Saving the base to GWformat)
(Saving the base to GWformat)
Line 19: Line 19:
  
 
== Saving the base to [[GWformat]] ==
 
== Saving the base to [[GWformat]] ==
With the '''older''' version of  GeneWeb, launch  [[gwsetup|gwsetup]], then select '''Save a GeneWeb source file'''. Remember the name of the saved source file with extension {{c|.gw}} (default name is that of your base). Close {{c|gwsetup}}. You may also trigger yourself the [[save]] process through a [[man#Exporting a gw file (gwu)|command-line]] with the {{c|gwu}} program.
+
With the '''older''' version of  GeneWeb, launch  [[gwsetup|gwsetup]], then select '''Save a GeneWeb source file'''. Remember the name of the saved source file with extension {{c|.gw}} (default name is that of your base). Close {{c|gwsetup}}. You may also trigger yourself the [[save]] process through a [[man#Exporting a GW file (gwu)|command-line]] with the {{c|gwu}} program.
  
 
== Importing a saved base ==
 
== Importing a saved base ==

Revision as of 18:35, 3 November 2015

150px-Geographylogo svg.png Language: English • français


This page describes how to recover a base from source files after version evolution of GeneWeb.

For minor revisions, implying no change in the data-base formats, it is sufficient to copy/paste the folder containing a base basname.gwd from one version to the other (assuming you have installed the new version in a separate folder as a precaution). Open your base with the new version to verify that your base is accepted by the new version of GeneWeb.

If you started from a GEDCOM file and have made no (or very few) modifications, you may choose to repeat the process with tne new GeneWeb version. From version to version, the GEDCOM to GW program may have improved and new GEDCOM tags might be accepted.

In the case of a major version evolution of GeneWeb, it is necessary to go through a save/restore cycle. In order to determine if this process is mandatory, you are encouraged to read the {{{2}}} file. Here are several cases where this is the case:

  • From 5.02 to 6.xx
  • From 6.xx to 7.yy
  • From a version compiled on a 32 bits machine to a 64 bits machine (This is the case since version 5.01)

The process is almost the same as that of cleaning a base: as in the "cleaning" case, the base is firstly saved, then restored. Other files associated with the base are copy/pasted. and launch the consanguinity and notes links restauration processes.

Repeat these steps for each of your bases.

Saving the base to GWformat

With the older version of GeneWeb, launch gwsetup, then select Save a GeneWeb source file. Remember the name of the saved source file with extension .gw (default name is that of your base). Close gwsetup. You may also trigger yourself the save process through a command-line with the gwu program.

Importing a saved base

With the newer version of GeneWeb, launch gwsetup and select Create a base ... from a GeneWeb source file (gwc1) or ... from a GeneWeb source file (gwc2). The source file to submit is the .gw file created at the previous step. You may also trigger yourself the import process through a command-line with the gwc1 or gwc2 programs.

Transferring auxiliary files

Copy/paste the other files associated with your base: cnt, etc, images and src from the older bases location to the newer (depending on evolutions, your template files in etc may require adjustments). Copy/paste the configuration file for your base (base_name.gwf) if one exists. Some descriptions in the install section discuss folder organisations avoiding this step.

Launching auxiliary programs (optional)

With the newer version of GeneWeb, launch gwsetup and select the initialisation of consanguinities and Update links page / family chronicle (update_nldb).