DownsGenealogy

This blog is a running commentary of my web site, DownsGenealogy.com. As the site continually evolves, I hope that the input and discussions here will aid me as the webmaster of this grand undertaking.

I have turned the comment function off, unless you are a member of this blog. If you would like to become a member so you can leave comments, please email me. Otherwise you can email me comments and I will do my best to reply.

My Photo
Name:
Location: Old Bridge, New Jersey, United States

No, I am not dead! But the people who I research are, so I thought that this photo would be a fitting tribute to them. In case you haven't guessed, I'm a genealogist. I have been researching my family history for over 25 years and I have begun the massive project of creating a web site where I can publish my work.

Sunday, March 19, 2006

The Book of Numbers

Something has been brought to my attention a couple of times in the past two months. It appears that my numbering system for uniquely identifying individuals in my genealogy is unconventional. In my database of people I have assigned a number in the order in which I have entered them into the database. For example, I started with my family as a child. My father is #1, my mother is #2, I am #3, etc.

The reason I use the numbers on my web site, Downs Genealogy.com, is to help avoid confusion. This sample should prove my point:


My great-great-great-great-great-great-great-grandfather was Joshua Hopkins{#97}, who was born in 1657. I am descended from him through his son, Joshua Hopkins{#95}, born in 1698. Among his sons was my great-great-great-great-great-grandfather, Joshua Hopkins{#93}, born in 1725. This Joshua{#93} had a son, Joshua Hopkins{#91}, born in 1753. Joshua{#91} had eight children. Two of his sons were Joshua{#838}, born in 1787, and Giles{#89}, born in 1791. Giles Hopkins{#89} was my great-great-great-grandfather.


So this is my numbering system as it stands today. It is simple and it works for my needs. The problem seems to be that genealogists have become used to certain numbering systems when they read the material published by someone else. Two examples are “Register Style” and NGSQ. But these systems are designed for genealogies starting with a single progenitor and working forward. My research does a lot of working back, so this type of a system would not work.

I could use the Ahnentafel system which is quite neat. If you want to know who someone’s father is, just double their number. However, only parents are given a number and siblings are left out. This makes collateral lines, and multiple descents from a single individual, a nightmare for both the compiler and the reader.

I guess the real issue is if we consider my web site a final published product. If you look at a publication like the Mayflower Society’s Five Generation Project, you notice that it is set up so that the numbering system helps you navigate through the book, up and down generations. They use the Register System of numbering, but why does a system like that work for them while leaving me stymied?

The answer is that my web site is always a work in progress. One of the last steps in publishing a genealogy is assigning the numbers. It has become a finished product without need of change. When corrections need to be made in future editions, often the numbering has to be modified. In the Five Generation Project, we see this when a child needs to be added to a family. We’ll say the children in a family were originally #236, #237 and #238, and a new child has just been discovered who was born between #237 and #238. In order to make a correction in a subsequent a printing or edition, the numbering system has to be adjusted something like this: #236, #237, #237a and #238. The only other solution would be to renumber the entire publication, which would be confusing when referring to it in source citations, research and such.

It would be the same for me when I add people to the database or the web site. I would need to renumber everyone each time I expanded, which would cause more confusion. If someone printed a page of my research, filed it away and then wanted to check back a year later, he would assume that the numbers still had meaning. I think you see what I am trying to explain, so I’ll stop here.

Even though my site is a published work, it can’t be considered finished since I am constantly updating. It is for these reasons that a standard genealogical numbering system can’t be employed. Perhaps someday, if I publish a book, I will be able to use a better numbering system.


"None of us really understands what's going on with all these numbers."

Congressman David A. Stockman
On the US Budget, 1981

Bill Downs
DownsGenealogy.com

Friday, March 03, 2006

The Scope of the Project Suddenly Increases

DownsGenealogy.com now needs another facet. I have concentrated on my line of descent from Thomas Downs of Eastham and Orleans, Massachusetts. I’m now getting inquiries from people about Downs family lines in other states, unrelated to our own. I referred a recent person to the “Downs Message Board” at Ancestry.com. I decided to browse the message board myself and I was surprised that it was one of the largest boards I have seen on Ancestry.com. I also noted that the board had no administrator and Ancestry.com was willing to consider people for the position. For better or worse, I got the job. I am now the administrator of the Downs Surname Message Board on Ancestry.com.

My next step will be to connect my web site to the board and possibly vice versa. This way anyone who wishes information on the Downs family can get between the two places easier.

Another thing I noticed browsing the message board that a query for Downses in Eastham and Orleans Massachusetts yield a significant number of hits. None of these were related to our Downs family. There have been Downses on the Cape since the 17th century and I have been aware of this. I have never addressed it because it does not concern our family. Now, for sake of completeness, I will plan an article on these older Downs lines. This should keep me busy for some time.

Bill