Barking Up the Wrong Tree: To Infinity and Beyond

25 February 2013

To Infinity and Beyond

Comments after the jump.

Peter Merihew
B: 7 Oct 1826 in New Bedford, Bristol, Ma

SPOUSE & CHILDREN
Sarah Andrews (1738-1798) married 20 Feb 1791
✿ Edmund Merrihew B: 1791
✿ Elizabeth Merrihew B: 1793
✿ Ruby Merrihew B: 1795
✿ Amos Merrihew B: 1797
✿ Sarah Merrihew B: 1800
✿ Celista Pierce Merrihew B: 1802
✿ Alice Elsie Smith Merrihew B: 1805
✿ Peter Merrihew B: 1807
✿ Ruth Merrihew B: 1812

FATHER
Edmund Merrihew (1791-1882)
MOTHER
Eliza M. Taber (1786-1835)

GRANDFATHER
Peter Merihew
B: 7 Oct 1826 in New Bedford, Bristol, Ma
GRANDMOTHER
Sarah Andrews (1738-1798)

GREAT-GRANDFATHER
Edmund Merrihew (1791-1882)
GREAT-GRANDMOTHER
Eliza M. Taber (1786-1835)

GREAT-GREAT-GRANDFATHER
Peter Merihew
B: 7 Oct 1826 in New Bedford, Bristol, Ma
GREAT-GREAT-GRANDMOTHER
Sarah Andrews (1738-1798)

GREAT-GREAT-GREAT-GRANDFATHER
Edmund Merrihew (1791-1882)
GREAT-GREAT-GREAT-GRANDMOTHER
Eliza M. Taber (1786-1835)

This continues ad infinitum.

ⓑⓐⓡⓚⓘⓝⓖ ⓤⓟ ⓣⓗⓔ ⓦⓡⓞⓝⓖ ⓣⓡⓔⓔ

All the children were born before their father. Their mother was over 50 when four of the children were born, five were born after she was dead. That's minor compared to the insanity that follows. This branch of the tree is doing loop-de-loops. It's a genealogical Groundhog Day.
There have been reports in the last couple weeks of a glitch on Ancestry.com. The glitch adds spouses as children or vice versa when attaching certain records. There are no records attached to these profiles. There aren't even other trees attached so this is all on the tree owner. Once the tree owner added the son as the father using the "select from list" option Ancestry's program is then stuck in an endless loop.
Yet another tree to blame for site slow downs.

If the screen cap is unclear, those circled are ALL Peter Merihew, B: 1826.

How many of you now have this going through your head?

Thanks to Janet for the link to this tree ;-)
If you have a profile to suggest please send a link to buwtree(at)gmail(dot)com.

PREVIOUS POST: Photo Friday: The Vampire
NEXT POST: No Tree and Private Tree DNA Results

1 comment:

MelanieWednesday, 27 February, 2013
LOL Haven't heard that song in a few years! But it was exactly what I thought of.
ReplyDelete
Replies

Add comment

Blog Reviews

Barking has been "deemed offensive to [Ancestry.com's] brand" and is banned from their Facebook pages. In Ancestry's "Community" comments with links to Barking are censored.
Dear Emma, Hannah, Jemima, Mary Jane, and all of her other personalities agree that I use "the banner of 'education' to actually mock, deride and laugh at [Ancestry's] own customers" and I "can make [my] point concerning tree inaccuracies & cock-ups and their effect on our 'hints' system without being downright unpleasant and sarcastic about it."
Allen says, “your cute little blog is a waste of bandwidth at best”
Ann thinks I'm "...copying and pasting mistakes on trees and calling it a blog" and that my readers are "mean-spirited people...who like to have a laugh at the expense of others."
Sue was really offended by the “...continual stream of sarcasm and constant poking fun...What a nasty taste in my mouth your blog left me with. Unpleasant, sarcastic and jeering at people who you obviously see as your intellectual inferiors. Won't be reading that again.”
And finally from Les, "You truly are a horrible woman, pointing out mistakes is one thing but blatantly laughing and taking the p is completely out of order."

Why?

Researching our family histories we are bound to make mistakes. Hopefully we are quick to correct them. Unfortunately some people refuse to read or think before adding information to their family trees. Some trees have been abandoned so the errors are there for eternity. Here we will laugh, mock and shake our heads at the carelessness, stupidity and/or ignorance of those errors.
All examples are taken from trees published online.
I'll also post tips occasionally, though the messed up trees are a great example of what NOT to do.
If you have an online tree to suggest for a future post please send me a link: buwtree(at)gmail(dot)com

The Fine Print

1. Copyright: Barking Up the Wrong Tree is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License and is owned and administered by Loretta Gillespie.

2. Content: Barking Up the Wrong Tree is responsible for the content of this site, not including visitor comments. Barking Up the Wrong Tree reflects the personal views and opinions of Loretta Gillespie.

3. Credit: Credit is not given to tree owners to protect the clueless. A tree owner who discovers their tree on this site should correct their mistakes so no one else realizes they were once a clickophile.

4. Accuracy and Validity: While there are helpful pointers on Barking Up the Wrong Tree a majority of posts are intended to be humorous. The disastrous trees are copied exactly as they appear on Ancestry.com. These trees are being used to show others what NOT to do.

5. Images: Attempts are made to source images used despite the fact that the trees they are taken from do not include source information.

6. Comments: Barking Up the Wrong Tree will exercise its right to delete comments which are deemed to be spam, offensive, childish or just plain stupid.

7. Liability: The content at Barking Up the Wrong Tree is not to be taken as fact nor absolute. Barking Up the Wrong Tree contains posts that are humorous and posts that are research tips. Barking Up the Wrong Tree is not responsible for anyone who cannot tell the difference between the two. The sites that Barking Up the Wrong Tree links to via hyperlinks are not under its control. Those sites are responsible for the content of those sites. If you do not find the humor on Barking Up the Wrong Tree to your taste then stop reading. If you choose instead to send an email to the owner it may be published on Barking Up the Wrong Tree and mocked publicly.

Thanks to Thomas MacEntee for allowing the use of the GeneaBloggers terms as a template.