Merging multiple places?

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Merging multiple places?

PaulR
A previous program I used seems to have duplicated many places in my gedcom
file; some places appear as many as thirty or more times in Gramps' Places
view.

I know I can merge these two at a time but is there a way to merge more than
two places at once? I have perhaps 10 places which are badly affected so
merging by hand would be rather tedious!

Many thanks,

Paul



--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

dbareis
I've also mumbled to my self about that. I have the same issue.

On Fri., 22 May 2020, 11:43 pm PaulR, <[hidden email]> wrote:
A previous program I used seems to have duplicated many places in my gedcom
file; some places appear as many as thirty or more times in Gramps' Places
view.

I know I can merge these two at a time but is there a way to merge more than
two places at once? I have perhaps 10 places which are badly affected so
merging by hand would be rather tedious!

Many thanks,

Paul



--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

Martnal
Have you considered trying a different way of exporting your data from the
source, to avoid the problem happening?





-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

dbareis
Hi,

How does exporting differently change the problem with the data or the way the tool works?  I'm pretty sure these options don't exist:
  • Export GEDCOM all nicely
  • Export GEDCOM with duplicates all over the place
Most tools I've seen don't try to dedup anything.
---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 25/05/20, 09:53:25 am

On Sun, 24 May 2020 at 23:27, Martnal <[hidden email]> wrote:
Have you considered trying a different way of exporting your data from the
source, to avoid the problem happening?





-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

enno

Hi Dennis,

How does exporting differently change the problem with the data or the way the tool works?  I'm pretty sure these options don't exist:
  • Export GEDCOM all nicely
  • Export GEDCOM with duplicates all over the place

There is no difference, because places don't have IDs like persons and families, sources, and notes. They are always exported as event attributes, and I'm assuming that they are merged by Gramps, if the names are identical.

Regards,

Enno




--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

Martnal
Dennis, I stand by my suggestion. Gramps has 13 different ways of exporting
data, some with sub-options. I would guess that your legacy system has more
than one.  The symptoms you are experiencing must be caused either by the
way data is exported, or by the way it is imported. It seems wise to ensure
that the exported data is clean, before progressing.

I'm not a Gramps expert, just a logical problem solver, trying to help.




-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

dbareis
Hi,

MyHeritage has ONE export option (3 variations based on photos). It is not legacy.  It duplicates everything (not on export, export just exports).  It even duplicates photos.  In any case, I don't think anyone said that the "duplicated" places were EXACT duplicates.  Some possible, likely examples:

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
MyHeritage has very powerful discovery tools (unlike Gramps) but that means you can expect all sorts of random spelling.  I certainly have never seen anyone who gets spelling right 100% of the time.

Obviously gramps knows that duplicates can exist otherwise there would be no need for a merge option at all, so knowing that this is an acknowledged issue within Gramps is it unreasonable to ask for the merge ability to be a billion times more useful than it is now? And with a change that is likely quite simple?

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:04:24 am

On Tue, 26 May 2020 at 04:28, Martnal <[hidden email]> wrote:
Dennis, I stand by my suggestion. Gramps has 13 different ways of exporting
data, some with sub-options. I would guess that your legacy system has more
than one.  The symptoms you are experiencing must be caused either by the
way data is exported, or by the way it is imported. It seems wise to ensure
that the exported data is clean, before progressing.

I'm not a Gramps expert, just a logical problem solver, trying to help.




-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

dbareis
Hi,

Please need to understand that not everyone needs all use cases. Instead of grumbling more I raised a feature request :-)



---
Thanks
Dennis

Mailtrack Sender notified by
Mailtrack 26/05/20, 08:28:01 am

On Tue, 26 May 2020 at 08:08, Dennis Bareis <[hidden email]> wrote:
Hi,

MyHeritage has ONE export option (3 variations based on photos). It is not legacy.  It duplicates everything (not on export, export just exports).  It even duplicates photos.  In any case, I don't think anyone said that the "duplicated" places were EXACT duplicates.  Some possible, likely examples:

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
MyHeritage has very powerful discovery tools (unlike Gramps) but that means you can expect all sorts of random spelling.  I certainly have never seen anyone who gets spelling right 100% of the time.

Obviously gramps knows that duplicates can exist otherwise there would be no need for a merge option at all, so knowing that this is an acknowledged issue within Gramps is it unreasonable to ask for the merge ability to be a billion times more useful than it is now? And with a change that is likely quite simple?

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:04:24 am

On Tue, 26 May 2020 at 04:28, Martnal <[hidden email]> wrote:
Dennis, I stand by my suggestion. Gramps has 13 different ways of exporting
data, some with sub-options. I would guess that your legacy system has more
than one.  The symptoms you are experiencing must be caused either by the
way data is exported, or by the way it is imported. It seems wise to ensure
that the exported data is clean, before progressing.

I'm not a Gramps expert, just a logical problem solver, trying to help.




-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
<img width="0" height="0" alt="" style="display: flex;" src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7">


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

Dave Scheipers
In reply to this post by dbareis
From your example, you will have six instances of Biggenden, one as a top level entry. One Queensland and one QLD as a top level entry.  Ans a Queensland, Queenslnnd, and QLD under Australia.

That Gramps managed to merge all of the many records with the same "Biggenden, Queensland, Australia" is a major achievement.

There have been Feature Requests to handle multiple merges,





On Mon, May 25, 2020 at 6:09 PM Dennis Bareis <[hidden email]> wrote:
Hi,

MyHeritage has ONE export option (3 variations based on photos). It is not legacy.  It duplicates everything (not on export, export just exports).  It even duplicates photos.  In any case, I don't think anyone said that the "duplicated" places were EXACT duplicates.  Some possible, likely examples:

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
MyHeritage has very powerful discovery tools (unlike Gramps) but that means you can expect all sorts of random spelling.  I certainly have never seen anyone who gets spelling right 100% of the time.

Obviously gramps knows that duplicates can exist otherwise there would be no need for a merge option at all, so knowing that this is an acknowledged issue within Gramps is it unreasonable to ask for the merge ability to be a billion times more useful than it is now? And with a change that is likely quite simple?

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:04:24 am

On Tue, 26 May 2020 at 04:28, Martnal <[hidden email]> wrote:
Dennis, I stand by my suggestion. Gramps has 13 different ways of exporting
data, some with sub-options. I would guess that your legacy system has more
than one.  The symptoms you are experiencing must be caused either by the
way data is exported, or by the way it is imported. It seems wise to ensure
that the exported data is clean, before progressing.

I'm not a Gramps expert, just a logical problem solver, trying to help.




-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

dbareis
HI,

If gramps managed to do it there wouldn't be a problem.  It being able to do so should be a trivial effort, the ONLY record that needs to matter is the final merged record (there is only one Biggenden) and if required that can be edited by the user to fix any remaining issues.   I'd have to look into the current implementation first... 

With my currently limited understanding I can see that actual addresses (street names and numbers) would need to be handled differently. But that is probably not a merge but possibly a different operation (plugin?) to attach them to the same towns etc. Not sure how the database currently looks for these...

Looks like that will go onto my todo list after I have successfully got my first "Form" addon change though the system.  I'm currently deciding if I want to continue help code open source systems.  So far I've spend twice the actual coding effort in GitHub things (for submitting a fraction of what I have done) and it looks like everything will be so slow.

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:55:04 am

On Tue, 26 May 2020 at 08:42, Dave Scheipers <[hidden email]> wrote:
From your example, you will have six instances of Biggenden, one as a top level entry. One Queensland and one QLD as a top level entry.  Ans a Queensland, Queenslnnd, and QLD under Australia.

That Gramps managed to merge all of the many records with the same "Biggenden, Queensland, Australia" is a major achievement.

There have been Feature Requests to handle multiple merges,





On Mon, May 25, 2020 at 6:09 PM Dennis Bareis <[hidden email]> wrote:
Hi,

MyHeritage has ONE export option (3 variations based on photos). It is not legacy.  It duplicates everything (not on export, export just exports).  It even duplicates photos.  In any case, I don't think anyone said that the "duplicated" places were EXACT duplicates.  Some possible, likely examples:

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
MyHeritage has very powerful discovery tools (unlike Gramps) but that means you can expect all sorts of random spelling.  I certainly have never seen anyone who gets spelling right 100% of the time.

Obviously gramps knows that duplicates can exist otherwise there would be no need for a merge option at all, so knowing that this is an acknowledged issue within Gramps is it unreasonable to ask for the merge ability to be a billion times more useful than it is now? And with a change that is likely quite simple?

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:04:24 am

On Tue, 26 May 2020 at 04:28, Martnal <[hidden email]> wrote:
Dennis, I stand by my suggestion. Gramps has 13 different ways of exporting
data, some with sub-options. I would guess that your legacy system has more
than one.  The symptoms you are experiencing must be caused either by the
way data is exported, or by the way it is imported. It seems wise to ensure
that the exported data is clean, before progressing.

I'm not a Gramps expert, just a logical problem solver, trying to help.




-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
<img width="0" height="0" style="display: flex;" alt="" src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7">
--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

Dave Scheipers
there is only one Biggenden

And how is Gramps to know that? 

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
These six records tells Gramps that there are six different places known as Biggenden.

Biggenden the country
Biggenden in the Australian state of Queenslnnd 
Biggenden in the country QLD
Biggenden in the Australian state of QLD
Biggenden in the country Queensland
Biggenden in the Australian state of Queensland 


When I first imported into Gramps, I had many places like the county Essex in Massachusetts.

Essex
Essex Co
Essex Co.

To say nothing to the states Massachusetts and Massachusets

Gramps can only understand them as separate and unique places.

Dave



On Mon, May 25, 2020 at 7:08 PM Dennis Bareis <[hidden email]> wrote:
HI,

If gramps managed to do it there wouldn't be a problem.  It being able to do so should be a trivial effort, the ONLY record that needs to matter is the final merged record (there is only one Biggenden) and if required that can be edited by the user to fix any remaining issues.   I'd have to look into the current implementation first... 

With my currently limited understanding I can see that actual addresses (street names and numbers) would need to be handled differently. But that is probably not a merge but possibly a different operation (plugin?) to attach them to the same towns etc. Not sure how the database currently looks for these...

Looks like that will go onto my todo list after I have successfully got my first "Form" addon change though the system.  I'm currently deciding if I want to continue help code open source systems.  So far I've spend twice the actual coding effort in GitHub things (for submitting a fraction of what I have done) and it looks like everything will be so slow.

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:55:04 am

On Tue, 26 May 2020 at 08:42, Dave Scheipers <[hidden email]> wrote:
From your example, you will have six instances of Biggenden, one as a top level entry. One Queensland and one QLD as a top level entry.  Ans a Queensland, Queenslnnd, and QLD under Australia.

That Gramps managed to merge all of the many records with the same "Biggenden, Queensland, Australia" is a major achievement.

There have been Feature Requests to handle multiple merges,





On Mon, May 25, 2020 at 6:09 PM Dennis Bareis <[hidden email]> wrote:
Hi,

MyHeritage has ONE export option (3 variations based on photos). It is not legacy.  It duplicates everything (not on export, export just exports).  It even duplicates photos.  In any case, I don't think anyone said that the "duplicated" places were EXACT duplicates.  Some possible, likely examples:

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
MyHeritage has very powerful discovery tools (unlike Gramps) but that means you can expect all sorts of random spelling.  I certainly have never seen anyone who gets spelling right 100% of the time.

Obviously gramps knows that duplicates can exist otherwise there would be no need for a merge option at all, so knowing that this is an acknowledged issue within Gramps is it unreasonable to ask for the merge ability to be a billion times more useful than it is now? And with a change that is likely quite simple?

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:04:24 am

On Tue, 26 May 2020 at 04:28, Martnal <[hidden email]> wrote:
Dennis, I stand by my suggestion. Gramps has 13 different ways of exporting
data, some with sub-options. I would guess that your legacy system has more
than one.  The symptoms you are experiencing must be caused either by the
way data is exported, or by the way it is imported. It seems wise to ensure
that the exported data is clean, before progressing.

I'm not a Gramps expert, just a logical problem solver, trying to help.




-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
Reply | Threaded
Open this post in threaded view
|

Re: Merging multiple places?

dbareis
Hi,

In your Essex example, I'd bet a fair bit of money that the last 2 are duplicates but the first?  I'd be googling or looking at maps, I can't expect Gramps to have to work it out... 

Why do you think Gramps needs to know it? It currently doesn't when 2 places are merged, there is no more reason for it to know for 100.  The user knows.  You obviously have got an issue with merge in general and not just for increasing it's capability.  There feature is there, the people who believe it's useful have "won".


---
Thanks
Dennis

p.s.  In case you have never used merge before it is a user invoked and confirmed operation.  

Mailtrack Sender notified by
Mailtrack 26/05/20, 12:38:44 pm

On Tue, 26 May 2020 at 09:48, Dave Scheipers <[hidden email]> wrote:
there is only one Biggenden

And how is Gramps to know that? 

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
These six records tells Gramps that there are six different places known as Biggenden.

Biggenden the country
Biggenden in the Australian state of Queenslnnd 
Biggenden in the country QLD
Biggenden in the Australian state of QLD
Biggenden in the country Queensland
Biggenden in the Australian state of Queensland 


When I first imported into Gramps, I had many places like the county Essex in Massachusetts.

Essex
Essex Co
Essex Co.

To say nothing to the states Massachusetts and Massachusets

Gramps can only understand them as separate and unique places.

Dave



On Mon, May 25, 2020 at 7:08 PM Dennis Bareis <[hidden email]> wrote:
HI,

If gramps managed to do it there wouldn't be a problem.  It being able to do so should be a trivial effort, the ONLY record that needs to matter is the final merged record (there is only one Biggenden) and if required that can be edited by the user to fix any remaining issues.   I'd have to look into the current implementation first... 

With my currently limited understanding I can see that actual addresses (street names and numbers) would need to be handled differently. But that is probably not a merge but possibly a different operation (plugin?) to attach them to the same towns etc. Not sure how the database currently looks for these...

Looks like that will go onto my todo list after I have successfully got my first "Form" addon change though the system.  I'm currently deciding if I want to continue help code open source systems.  So far I've spend twice the actual coding effort in GitHub things (for submitting a fraction of what I have done) and it looks like everything will be so slow.

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:55:04 am

On Tue, 26 May 2020 at 08:42, Dave Scheipers <[hidden email]> wrote:
From your example, you will have six instances of Biggenden, one as a top level entry. One Queensland and one QLD as a top level entry.  Ans a Queensland, Queenslnnd, and QLD under Australia.

That Gramps managed to merge all of the many records with the same "Biggenden, Queensland, Australia" is a major achievement.

There have been Feature Requests to handle multiple merges,





On Mon, May 25, 2020 at 6:09 PM Dennis Bareis <[hidden email]> wrote:
Hi,

MyHeritage has ONE export option (3 variations based on photos). It is not legacy.  It duplicates everything (not on export, export just exports).  It even duplicates photos.  In any case, I don't think anyone said that the "duplicated" places were EXACT duplicates.  Some possible, likely examples:

  • Biggenden
  • Bigganden, Queenslnnd, Australia    
  • Biggenden, QLD  
  • Biggenden, QLD, Australia    
  • Biggenden, Queensland 
  • Biggenden, Queensland, Australia
MyHeritage has very powerful discovery tools (unlike Gramps) but that means you can expect all sorts of random spelling.  I certainly have never seen anyone who gets spelling right 100% of the time.

Obviously gramps knows that duplicates can exist otherwise there would be no need for a merge option at all, so knowing that this is an acknowledged issue within Gramps is it unreasonable to ask for the merge ability to be a billion times more useful than it is now? And with a change that is likely quite simple?

---
Thanks
Dennis


Mailtrack Sender notified by
Mailtrack 26/05/20, 08:04:24 am

On Tue, 26 May 2020 at 04:28, Martnal <[hidden email]> wrote:
Dennis, I stand by my suggestion. Gramps has 13 different ways of exporting
data, some with sub-options. I would guess that your legacy system has more
than one.  The symptoms you are experiencing must be caused either by the
way data is exported, or by the way it is imported. It seems wise to ensure
that the exported data is clean, before progressing.

I'm not a Gramps expert, just a logical problem solver, trying to help.




-----

Martin, SW London

Gedmatch DNA Kit H062246.
FT-DNA Kit B388093.

Names: Loughborough and Loughbrough, (London, Hull, Pirton and Hartlepool);
Watson, (Bedlington, Jarrow & H'pool);
Ballard & Glassop (E. London); 
Leggett (Corton, Scarborough, Hartlepool); 
Young & Wilson, (Hartlepool). 

I am using GrampsAIO64-5.0.0-1 on Windows 10.
--
Sent from: http://gramps.1791082.n4.nabble.com/GRAMPS-User-f1807095.html


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org
<img width="0" height="0" style="display: flex;" alt="" src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7">


--
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
https://gramps-project.org