↑ Source: #S18 Record ID Number: MH:SC270 Page: Birth year: 1702; Birth city: Albany; Birth state: NY. Data: Text: Birth date: 21 June 1702 Birth place: Albany, Albany, NY Death date: 11 May 1723 Death place: Marriage date: 11 May 1723 Marriage place: Albany, Albany, NY Note: #N350 Note: #N351
↑ Secretary Henry L. Bogert. Year Book of the Holland Society of New York. (New York: Knickerbocker Press, New York, 1905.)
↑ Secretary Henry L. Bogert. Year Book of the Holland Society of New York. (New York: Knickerbocker Press, New York, 1906.)
↑ Jonathan Pearson. 1873. Contributions for the genealogies of the descendants of the first settlers of the patent and city of Schenectady, from 1662 to 1800. (Albany, N.Y.: J. Munsell.)
Bogert, Secretary Henry L. Year Book of the Holland Society of New York. New York: Knickerbocker Press, New York, 1905.
Simms, Jeptha Root. History of Schohaire County and Border Wars of New York, Containing Also a Sketch of the Causes Which Led to the American Revolution, and Interesting Memoranda of the Mohawk Valley... Albany: Munsell & Tanner, 1845. p. 135-136.
Source: S12 Record ID Number: MH:S12 User ID: ABCA9416-464B-41E4-92A7-D37A2332DB7E Author: Edmund West, comp. Title: Family Data Collection - Births Publication: Online publication - Provo, UT, USA: Ancestry.com Operations Inc, 2001. Repository: #R1 Note: #N362 Repository: R1 Record ID Number: MH:R1 User ID: B0341857-AF12-41E8-AB5D-1F9B8C2D0936 Name: Ancestry.com
Source: S5 Record ID Number: MH:S5 User ID: 9704F1FE-57EF-4222-BF44-D0AE17B1E63F Title: Ancestry Family Trees Publication: Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members. Repository: #R1 Note: #N355 Record ID Number: MH:SC168 Page: Ancestry Family Trees Data: Text: https://www.ancestry.com/family-tree/tree/46150399/family
Source: S-2085618038 Repository: #R-2142120414 Title: Ancestry Family Trees Publication: Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members.
This person was created on 14 September 2010 through the import of 124-DeCoursey.ged.
Sponsored Search by Ancestry.com
DNA Connections
It may be possible to confirm family relationships with David by comparing test results with other carriers of his Y-chromosome or his mother's mitochondrial DNA.
However, there are no known yDNA or mtDNA test-takers in his direct paternal or maternal line.
It is likely that these autosomal DNA test-takers will share some percentage of DNA with David:
Project protection does not prevent normal editing of a profile. This profile is "protected" only because there are myriad spellings of "Quackenbosch", which have resulted in many duplicate profiles, and there was a desire to prevent repeated merges that would repeatedly change the LNAB.
This profile is in serious need of attention, not only to eliminate duplication of span tags, but also to get rid of GEDCOM garbage text like "Record ID Number: MH:S5 User ID: 9704F1FE-57EF-4222-BF44-D0AE17B1E63F," add reliable sources and content based on those sources, get rid of erroneous information, etc. There is a particular need to find and document more church records to help us determine which of those many spellings of "Quakkenbosch" should be identified as his LNAB. (This is why the profile is in the "Needs LNAB" category.)
The project consists of -- and depends on -- its members (and anyone else who wants to help) to correct errors and otherwise improve profiles. PLEASE jump in to help correct the problems that you see (and know how to correct). You might want to see Help:GEDCOM-Created Biographies for advice on what can be removed from GEDCOM-created profiles like this one.
I repeat: Project protection does not prevent normal editing of a profile.
Thank you all for your comments and attention to this record. I removed the last S5 (clear duplicate) from the Sources section and removed duplicate N226 (same as N225) and the reference to N226 from the biography. I appreciate you all for helping out on this record. Any questions, please feel free to contact me. Big thank you to Ellen!
Quackenbush-177 and Quackenbosch-97 appear to represent the same person because: This is the oldest paternal ancestor in this chain in need of a merge into the NNS PPP. No tree conflicts. Thanks! Merging into the name that the New Netherland Settlers project agreed upon long ago.
Quackenbush-353 and Quackenbosch-97 appear to represent the same person because: This is the oldest paternal ancestor in this chain in need of a merge into the NNS PPP name. No tree conflicts. Thanks!
Quackenbush-10 and Quackenbosch-97 appear to represent the same person because: This is the oldest paternal ancestor in this chain in need of a merge into the NNS PPP. No tree conflicts. Thanks! Merging into the New Netherland Settlers project accepted version of the name for this time period and one closest to church records.
Quackenbush-177 and Quackenbush-10 appear to represent the same person because: This is the oldest paternal ancestor in this chain in need of a merge into the NNS PPP. No tree conflicts. Thanks!
There are duplicate identical citations in the sources section:
Probably from a merge: Could the duplicates be removed safely without affecting the project?
This profile is in serious need of attention, not only to eliminate duplication of span tags, but also to get rid of GEDCOM garbage text like "Record ID Number: MH:S5 User ID: 9704F1FE-57EF-4222-BF44-D0AE17B1E63F," add reliable sources and content based on those sources, get rid of erroneous information, etc. There is a particular need to find and document more church records to help us determine which of those many spellings of "Quakkenbosch" should be identified as his LNAB. (This is why the profile is in the "Needs LNAB" category.)
The project consists of -- and depends on -- its members (and anyone else who wants to help) to correct errors and otherwise improve profiles. PLEASE jump in to help correct the problems that you see (and know how to correct). You might want to see Help:GEDCOM-Created Biographies for advice on what can be removed from GEDCOM-created profiles like this one.
I repeat: Project protection does not prevent normal editing of a profile.
edited by Ellen Smith