Adding place names on Ancestry

I have a fairly big tree now (see Complete Unst Tree – How’s it going?) and I’ve recently been having problems with the Ancrestry website when I add fact to someone with a area rather than a specific place name. For example when I add their occupation, I tend to just record it as “Unst, Shetland, Scotland” even though they lived in “Little Ham, Muness, Unst, Shetland, Scotland”, because I don’t really know the exact location of their work.

Ancestry Location entry field

Ancestry shows you all the locations which CONTAIN the letters you type into the location field

Recently Ancestry’s interface changed so that if you put in the first few letters of the place name you wanted to insert, say “Unst, S” instead of popping up a list with all the places you have previously used that BEGIN with those letters, it’s shows all the places you have previously used that CONTAIN those letters. For me this is a VERY long list, with the one I want at the bottom of the list! It also appears that this list is not scroll-able past the point it disappears off the bottom of your browser window. This was a pain.

Well totally by accident today, I discovered a way round this. If you put 2 spaces in front of the characters you type in, the list only seems to show you things that start with the letters you want, rather than all those which contain them. I’m not quite sure why, but I’ll take it!!

Advertisements

Working with 1841 Census Returns

If you’ve been using the census returns to follow your family tree back through the years, you may have noticed that the 1841 census returns don’t often show up as hints (a term used on the Ancestry website for showing possible records that may match a person in your tree).

The 1841 census is a bit different to all the subsequent census returns; recorded ages are rounded down to the nearest 5 years for anyone over 15 years of age; birthplaces were recorded as being in the county, rather than giving parish details as in later census; and it does not record the relationships between people in the same household. So for my Complete Unst Family Tree project all those people who were born on the island of Unst (marked on the map below) are recorded as being born in “Orkney and Shetland”, i.e. the full area covered by the map below! Just a slight difference.

There is however, a certain pattern that can be recognised in an 1841 census return which is useful, especially when you already know a lot about the members of the household from subsequent census returns. You can spot the parents and children from the ages; parents will be listed first and then the children in age descending order – sometimes with the male children listed first followed by the female children. The hard part comes at the end of the record for each household where a random selection of others may be listed; servants – usually identifiable as such from an occupation of “FS” (female servant) or “MS” (male servant); unmarried aunts; aged parents, and other random relations. Your only hope with these is that, if they are staying with the family in 1841, that it won’t be the only time. So it really pays to fully understand the family and it’s close relations, before trying to apply an 1841 census return to them.

They are worth searching for though (and you will most likely have to search explicitly for them due to the age and birthplace differences) as often they will provide details of older children that have moved out and got married by the next census, which is invaluable with linking together these early records, especially when Old Parish Marriage Records don’t record parents of the marrying parties.

My advice? Leave the 1841 census till last, but don’t ignore it completely.

Hints when merging people in an online family tree

I am currently developing my family tree on-line, after deciding to get it into a more manageable format than the old crinkly sheets of paper I found when back home. The website I use is Ancestry.

When working through census records I quite often find that the women “disappear” at around the age of 25. Of course, they don’t actually disappear, it’s just that they have got married and I don’t yet know their married name because I haven’t looked up their marriage details yet. Later when I do get to looking up their marriage details, I discover that they are already in my tree elsewhere under their married name. So now I have to merge them. Until a month ago, I was doing this manually, but Ancestry have just added an excellent new feature allowing you to merge two people in the same tree. I’ve already used this feature a number of times and it is so much easier than manual merging. I have some hints when using it which are described in this post.

Single entry facts

Before doing the merge of two people that you have decided are actually the same person, edit them manually to ensure the following facts are identical

  • Name: For example, you have the maiden surname in one and the married surname in the other.
  • Birth: For example, you have “abt 1850” in one and the exact birthdate in the other
  • Birth place
  • Death
  • Death place

The reason for doing this first is because, when the facts differ, Ancestry will add both in, one (which you choose) as the primary fact and the other as an alternative fact. I personally don’t like alternative facts, especially in the above cases where they are easily resolved, and find it less time consuming to deal with them before the merge rather than afterwards. It also has the benefit of making it much easier for Ancestry to present you with the correct person to merge with since the names and birth dates are identical! You know you’ve got it correct when the merge window shows that these facts are the same.

Ancestry Merge Duplicate

When everything matches, this is indicated by the tag “same”

Left over hints

When you have two people that need to be merged, it is almost certain that the hints you have applied to each will differ (or you would have noticed the need to merge them sooner). When merging two people, the hints that are remaining will be carried over. This means that you will end up with a person who has an “Unreviewed hint” that is actually already applied. You can reduce the number of these hints that you have by carefully selecting which of the two people you are merging to actually run the merge option from.

Merge Menu

Running the merge operation from the “more options” menu for one person

I have found that running the merge option from the person with the most remaining hints leaves you with the least tidying up to do. or in other words, the hints that are carried over even though they are already applied to the combined person, come from the person that you selected to match with, rather than the one you ran the merge option from.

N.B. I have reported the issue to Ancestry and it has been passed on to their developers.

More hints to come later.