GEPS 009: Import Export Merge
This page is for the discussion of a proposed implementation of the merging old and new data both whilst importing, and as a independent merge process, in GRAMPS. As this action is closely related to import and export, this section has been named "Import Export Merge"
Import Export Merge
Officially, GRAMPS import does not merge existing data with new data being imported. (The Spreadsheet/CSV does do a type of merge, but let's leave that aside for the moment. It is discussed in a section of Gramps Manual). However, the standard GRAMPS import will duplicate some data (such as events, but not people) if you import a GEDCOM file twice. This proposal will fix this bug by allowing a user to intelligently, interactively, or automatically do a better job than the current version.
This same process can be used to interactively merge two objects in GRAMPS by the user. For example, a user may realize that two person entries are really the same person, and so should be combined.
Current Related Files
- CSV Import
Currently exporting to gedcom and csv is limited to some information. Though gedcom is "standard" lingua franca of genealogy, it is inherently limited, particularly because various extant versions of gedcom. CSV has the advantage that it can be imported to any current spreadsheet, particularly OpenOffice.org. What are the limitation of csv exports in gramps?
CSV export/import is limited to the main objects in GRAMPS. It was not designed as a general purpose import/export but rather an alternative input/output tool.
This is not a trivial task, though probably not impossible. Because of the extent and complexity of the task, a separate thread is desirable. Merging: A reference to such thread is here. Some informed discussion is clearly desirable. Whilst there are a number of people with some knowledge of Python who are eager to contribute to a "real program", they need to be able to first find their way in the various files of Gramps. It would help to extract the names of the most pertinent file names from the general list and make the sublist here for the orientation purposes. Also, the aims of Merging should be first defined in non-ambiguous format.
One can sub-classify import in three sub-titles:
Fresh Data Import
This is probably the simplest option and safest - delete (first archive!) the current gramps data base and import all data.
Simply append all import data to the existing data base. The editing task would be left to the user. This option should be relatively easy to implement.
Leave some editing of the data to the program. Whilst manual intervention by the user would inevitably be required, some of it could be achieved in the program.
The above text is a raw outline only. The writer is not really familiar with gramps and has only offered to open a page in wiki to the Coordinator because everybody else seemed to be reluctant to do so. There is no doubt that this is a mere "bones" of the task and a very small step in potential programming task which can only occur if there is input from other persons interested in the topic and willing to discuss in the wiki style. There is some hope that such a discussion may take place as there has been a considerable exchange of thoughts and information in the developers' mailing list.
It would be helpful if substantial contributors to this page were to indicate who they are. Simplest is to append four "~"'s whilst in the editing mode! It would enable simpler direct communication between all interested parties. Of course, minor edits do not need to have the contributor's name, which is optional anyway. Al 21:03, 29 August 2008 (EDT)