pre 1700 gedcom import rejected though I have pre 1700 badge

Question

Why would a person on an imported gedcom pre 1700 be skipped when I have a pre-1700 badge

Comments

Some of the advice in this discussion is no longer applicable. A new process for working with Gedcoms has been inaugurated that allows pre-1700 people to be created as part of the processing of a Gedcom. See https://www.wikitree.com/g2g/461205/have-you-tried-gedcompare-2-0 for more information on the new process.

Answer 1

WT will not import pre-1700 profiles, no matter what.

"Individuals born prior to 1700 will be automatically skipped."  https://www.wikitree.com/wiki/Help:GEDCOM

Comments

So how do pre-1700 profiles get added. Your answer was not very informative

---

Manually, one by one.  Have you searched to see if any are already here?

And you're welcome.

---

Thank you Herbert.  I understand.  Yes I have done a search during the Gedcom compare process.  I found that if I accidently hit the profile instead of the compare that when coming back to the list the work since the last save was lost. I think there is room for improvement here.

Thanks for your prompt help

---

You are welcome.  WT has a major GEDCOM system re-work in process.  I have no idea about the time frame, or whether they will open up pre-1700 importing (kinda doubt it).

---

This probably should be a new question.

Is there a faster way of finding duplicates than selecting the profile of the person and then going to merges and matches. Can all the people managed by me be listed. This would be helpful when I deliberately make duplicates in order to import sources and media and merge these into an existing profile.

Dave

---

That's how I usually look for duplicates.  Below the list of candidates, there are filters that can narrow things down quite a bit.

The list of profiles you manage is your Watchlist.  At the top right center of any page, pull down My WikiTree, and Watchlist is near the bottom of the list.

I did a few deliberate duplicates for the same reason, and regretted it.  The sources come across in a very inconvenient form.  They are integrated as inline references in a timeline-style bio, with lots of redundancy and wikicode.  Teasing them out and editing the existing and imported bios into a coherent, readable form is ultra-heavy lifting.  These things only become real once you've experienced them.  Hence the universal GEDCOM advice:  Do a very small one first!

---

Great advice.

Thanks so much

Dave

---

I thought deliberate duplicates were discouraged. Why are you not able to do the work in a single profile rather than creating a new one and merging?

---

if I skip the person I have to add all the source documents manually.  I thought that creating a duplicate then merging the duplicate would transport the source records and attachments.  Herbert however says that the sources arent handled well anyway and it is faster to do this manually.  I think Ancestry does this much better.

---

Lynda, somewhere in the GEDCOM instructions (I think on the GEDCompare page), it suggests that a deliberate duplicate might be OK when the imported profile has significantly more sources than the existing one.  See previous comments for my experience.

---

The situation where I would knowingly allow a Gedcom to create a duplicate is the case of a Gedcom that contains numerous family connections that would have to be recreated manually if the person were skipped. For example, if the person is in WikiTree without any children and my Gedcom contains profiles for his or her 13 children... In that situation, merging the new duplicate profile with the existing profile will correctly connect all 13 children far more efficiently than if I import the children without the parent, then go in manually to create the connections.

---

Thanks for the explanation. That makes sense.

Answer 2

Yes people are correct about not be able to imput tree pre-1700, which they would change it to pre 1600/1500, yes it could/ would create data dumps and many other issues, but their is many reasons I can explain why, I just don't want to say. Another reason why they should add all from Family search.