Difference between revisions of "Gramps Old database"

From Gramps
Jump to: navigation, search
m (Experimental)
m (Solutions)
Line 13: Line 13:
  
 
* The safety way is to import it into '''[http://sourceforge.net/project/showfiles.php?group_id=25770&package_id=109309 Gramps-2]''' and to export this updated database. This will generate a new Gramps XML more compatible for an import into '''Gramps-3'''.
 
* The safety way is to import it into '''[http://sourceforge.net/project/showfiles.php?group_id=25770&package_id=109309 Gramps-2]''' and to export this updated database. This will generate a new Gramps XML more compatible for an import into '''Gramps-3'''.
**If your operating system do not support '''Gramps-2''' any more as some dependancies has been removed since '''Gramps-2''' (''GCONF, gnome-doc-utils, yelp, python-reportlab, etc...'') or updated like python libs and related, then you could have a look at [[Linux_Genealogy_CD|Linux Genealogy Live CD]] archives.
+
**If your operating system does not support '''Gramps-2''' any more as some dependancies has been removed since '''Gramps-2''' (''GCONF, gnome-doc-utils, yelp, python-reportlab, etc...'') or updated like python libs and related, then you could have a look at [[Linux_Genealogy_CD|Linux Genealogy Live CD]] archives.
  
 
* Also, you may [[Using_the_bug_tracker|submit your old database on bug-tracker]], mark this report as '''private''' (''will be hidden for non-developers'') and a developer will try to help you for updating your database.
 
* Also, you may [[Using_the_bug_tracker|submit your old database on bug-tracker]], mark this report as '''private''' (''will be hidden for non-developers'') and a developer will try to help you for updating your database.

Revision as of 07:23, 22 May 2009

Introduction

If you have an old Gramps XML database generated 4 years ago, then you may have some difficulties to import it into last stable release (3.1.x).

Gramps-1 did not store event as primary object and did not use bsddb references.

There was some limitations (size, informations, encoding), new Gramps versions tried to fix them.

Solutions

  • The safety way is to import it into Gramps-2 and to export this updated database. This will generate a new Gramps XML more compatible for an import into Gramps-3.
    • If your operating system does not support Gramps-2 any more as some dependancies has been removed since Gramps-2 (GCONF, gnome-doc-utils, yelp, python-reportlab, etc...) or updated like python libs and related, then you could have a look at Linux Genealogy Live CD archives.

Experimental

XML databases generated by Gramps-1 are not lost as they are written into a documented open format.

If a XML/XSL wizard planned to generate a script, here an experimental and partial test, which try to migrate a part of data to an other Gramps XML file, according to last XML DTD.

Event, Repository and Note references are broken because they was not primary objects on Gramps-1. If someone knows how to handle this, then feel free to do changes.