Difference between revisions of "Gramps Old database"

From Gramps
Jump to: navigation, search
m (Patsyblefebre moved page Old database to Gramps Old database: more meaningful)
(27 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Category:Documentation]]
+
{{languages|Old_database}}
 +
 
 +
If you have an old [[Gramps XML]] database generated '''some years ago''', then you may have some difficulties to import it into last stable release.
  
==Introduction==
+
'''Gramps-1''' did not store '''[[Events_in_Gramps|event]]''' as primary object and did not use bsddb references.
  
If you have an old database (GRAMPS XML) generated 4 years ago, then you could have some difficulties to import them into last stable release (3.1.x).
+
There was some [[Database_Formats#GRAMPS_1.0_and_earlier|limitations]] (''size, informations, encoding''), '''new Gramps versions''' tried to fix them.
  
 
==Solutions==
 
==Solutions==
  
* 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.
+
* The safety way is to import it into '''[http://sourceforge.net/projects/gramps/files/Stable/2.2.10/ Gramps-2]''' and to export this updated database. This will generate a new Gramps XML more compatible for an import into '''Gramps-3'''.
**If you 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]].
+
**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, libglade, 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.
 +
 
 +
* related to bug {{bug|6129}} : I downloaded the gramps 2.2.10 on my ubuntu 11.10 and did the following :
 +
  $ tar xzvf gramps-2.2.10.tar.gz
 +
  $ ./autogen.sh
 +
  $ make
 +
  $ python src/gramps.py
 +
    then
 +
    * import the 20060115.grdb ( your grdb file )
 +
    * export in gramps xml
  
* 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.
+
You can now load the new created file in your last gramps version. I hope it will work for everybody.
 +
 
 +
I choosed 2.2.10 because the original file was 20060115 : at this period, gramps was 2.2. or 2.0.
 +
So I used the last 2.2 available version.
 +
If this had not worked, I think I would have tried the last 2.0.11 available version.
 +
 
 +
==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, [[Media:123xsl.gz|here]] an experimental and partial test, which try to migrate a part of data to an other Gramps XML file, according to last [http://gramps-project.org/xml/ XML DTD].
 +
 
 +
Old Note:''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.''
 +
 
 +
[[Category:Documentation]]
 +
[[Category:Developers/Reference]]
 +
[[Category:Developers/General]]

Revision as of 02:30, 13 February 2013

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

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, libglade, etc...) or updated like python libs and related, then you could have a look at Linux Genealogy Live CD archives.
  • related to bug 6129 : I downloaded the gramps 2.2.10 on my ubuntu 11.10 and did the following :
 $ tar xzvf gramps-2.2.10.tar.gz
 $ ./autogen.sh
 $ make
 $ python src/gramps.py
    then
    * import the 20060115.grdb ( your grdb file )
    * export in gramps xml

You can now load the new created file in your last gramps version. I hope it will work for everybody.

I choosed 2.2.10 because the original file was 20060115 : at this period, gramps was 2.2. or 2.0. So I used the last 2.2 available version. If this had not worked, I think I would have tried the last 2.0.11 available version.

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.

Old Note: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.