Re: [Gramps-users] Deleting a whole line

[Alex R. <sh...@al...>]

On Sat, Jan 10, 2004 at 08:57:53PM -0700, Don Allingham wrote:
>=20
> I'm not sure that I understand this. To which line are you referring?
>=20
> On Sat, 2004-01-10 at 14:21, Tom Weichmann wrote:
> > I have been using Gramps practically since the beginning.  Recently I n=
oticed=20
> > that a GEDCOM that I imported a long time ago did not import its source=
s.  I=20
> > tested it out and Gramps does now import this file just fine.  What I w=
ant to=20
> > know is if it is possible to delete everyone in this line so that I can=
=20
> > (re)import this GEDCOM and not produce a lot of duplicate people?

I think I understand the problem, and I don't think there's a good=20
solution available right now.

You have database with lots of people. Then you import more data from=20
GEDCOM. This incorporates the data into your database, so everything is=20
bundled together.

Then you edit your database, and you don't have a version you=20
had before importing GEDCOM. Then you want to re-import GEDCOM because=20
now gramps can handle more of GEDCOM fields, and handle them better.
If you do that, you will end up with duplicate of every person that was=20
in GEDCOM.

The idea is to remove the set of people that came from GEDCOM and then=20
re-import from GEDCOM. Typically, GEDCOM stores a single tree. It would=20
be nice to be able to remove the whole tree (descendants and families of=20
a given person). Tom, correct me if I'm wrong.

The broader function would be to remove people matching the filter. One=20
can make the filter that matches descendants, families, etc, test it a=20
few times, and then go ahead and remove the whole crowd. There's an RFE=20
requesting just that.

I think this is a good candidate for post-1.0.0 addition.

Alex

--=20
Alexander Roitman   http://ebner.neuroscience.umn.edu/people/alex.html
Dept. of Neuroscience, Lions Research Building
2001 6th Street SE, Minneapolis, MN  55455
Tel (612) 625-7566   FAX (612) 626-9201