My List of Personal Favorite Sites

 <?xml version="1.0" encoding="utf-8"?>

<setting name="PersonalFavoriteSites" serializeAs="Xml">

<value>

<ArrayOfAnyType>

<anyType xsi:type="xsd:string">Newspapers ; https://newspapers.com</anyType>

<anyType xsi:type="xsd:string">FindaGrave ; https://findagrave.com</anyType>

<anyType xsi:type="xsd:string">

History of Parliament ; https://www.historyofparliamentonline.org/

</anyType>

<anyType xsi:type="xsd:string">Geni ; https://www.geni.com/home</anyType>

<anyType xsi:type="xsd:string">

1320-1480IPM ; http://www.inquisitionspostmortem.ac.uk/browse/inquisitions/

</anyType>

<anyType xsi:type="xsd:string">

Families of Ancient New Haven ; https://www.ancestry.com/search/collections/48025/?ftm=1

</anyType>

<anyType xsi:type="xsd:string">

Soc Medieval Genealogy Google Group ; https://groups.google.com/g/soc.genealogy.medieval?pli=1

</anyType>

<anyType xsi:type="xsd:string">

Complete Baronage ; https://archive.org/details/cu31924092524382

</anyType>

<anyType xsi:type="xsd:string">

Burke's Peerage and Baronetage 1914 ; https://archive.org/details/bub_gb_Pf8cAAAAYAAJ

</anyType>

<anyType xsi:type="xsd:string">

Visitations of Cambridge (ukga.org) ; https://ukga.org/browse.php?action=ViewRec&DB=13&bookID=186&page=vii

</anyType>

<anyType xsi:type="xsd:string">

Guide and Index to England Visitations ; https://firstsettlers.genealogyvillage.com/visitations.html

</anyType>

<anyType xsi:type="xsd:string">

Baronia Anglica Concentrata by Banks ; https://archive.org/details/baroniaanglicaco01bankuoft

</anyType>

<anyType xsi:type="xsd:string">

Accepted Genealogy Abbreviations ; https://www.geni.com/projects/Abbreviations-Acronyms-for-Genealogy-The-Accepted/3096

</anyType>

<anyType xsi:type="xsd:string">

Chicheley ; https://www.google.com/books/edition/Genealogical_Memoirs_of_the_Extinct_Fami/OaxCAAAAYAAJ?hl=en&gbpv=1

</anyType>

<anyType xsi:type="xsd:string">

Archtecture and Historical Churches of Cambridgeshire ; https://archive.org/details/architecturalhis00hillrich

</anyType>

<anyType xsi:type="xsd:string">

Inner Temple Bios ; https://archive.org/details/acataloguenotab00hutcgoog

</anyType>

<anyType xsi:type="xsd:string">

History of Middlesex Cty, MA ; https://archive.org/details/historyofmiddles01hurdh

</anyType>

</ArrayOfAnyType>

</value>

</setting>

2022 Class 3 Building a Template Tree

• Finish Accessing Resources
• FTM Overview
• Build the Template Tree
• Video on Using the Template Tree
• Folder of starter icons
• Run through the build process for real

The last power point demonstrates building a template tree.  For convenience, here is the summary of the steps:

1. Start FTM- make sure you are not starting on an existing tree but are starting a new one. (Plan.New Tree.  Enter what you know)
2. Enter a real name or a fictitious name you will always recognize. This person will be deleted from your .ftm tree when you start building a new tree
3. Basic tree setup:
   • Decide on tree naming convention
   • Fill in Menu.Tools.UserInformation
   • Complete Menu.Tools.Options
4. Add your standard sources: Menu.Edit.Manage Sources
5. Edit and add history events: Menu.Edit.Manage Historical Events
6. Add standard Repositories: Menu.Edit.Manage Repositories
7. Edit and add Facts: Menu.Edit.Manage Facts
8. Add standard Media: Workspace.Media
• Decide on naming conventions for media
9. Add your personal categories
10. Add Favorite Search Locations
11. Save file in a special folder as is (Menu.File.Save or Save As)
12. Use the FTM.Menu.File.Backup function to back up the tree as and .ftmb file.  Make sure you have the Backup Location right- it has to be the same folder  in which you created the Template file.

To use the Template:

1. When you are ready to start a new tree, and it is not a tree or a portion of the tree you already have that you are going to export...
2. Use File Explorer or Finder to create a new folder in your genealogy database folder and name it so you will recognize the folder as containing the tree you are going to build.  (clumsy sentence, but that's the rule)
3. Open the _Template folder and copy the folder inside it (Should be called _Template Media) and the .ftm file.
4. Open the folder you created in 2 above. 
5. Paste the _Template Media folder and the .ftm file into the folder
6. Open the .ftm file by clicking on it.  FTM should open the _Template file.
7. Click on the small arrow next to the file name in the top left corner of the FTM window (eg, _Template).  A list of the files you have opened in FTM will appear, with the _Template file at the top.
8. Click on the arrow head to the right of that name.  There will be a Rename option.
9. Click on that option.  Rename the tree to whatever you want the name to be.
10. (Never rename the any .ftm file or Media folder outside FTM; always us this Rename function)
11. Add some individuals to the tree, starting with the home person for the new tree- OR- import an existing tree by whatever means you want.
12. Delete the placeholder people that came with the template.
13. If you imported a .ftm tree or a tree from Ancestry, clean up the Facts and Places using the Manage functions under FTM.Menu.Edit.

2022 Class 5: A Canonical Tree

In mathematics and logic an important concept is "canonical form."  This means that the mathematical or logical concept is written or phrased in a standardized way.  Transferring that concept to genealogy, a canonical tree is a family tree database that meets standards for form and content.  I'm going to take a stab at listing some of these standards.  In future posts, using the term canonical tree will mean that it meets these standards.

By the way, this is a draft and I welcome additions and corrections.

A family tree is in canonical form if:

• For the tree itself
• No two person entries are the same person.
• There are no incorrect links (relationships), such as double links, or links that result in the wrong children being assigned to the wrong parent.
• For the facts list
• No redundant facts in the the Facts list (Lived in vs Residence).
• No orphan facts... these are facts that are imported when a facts are added to a person from an outside source; you didn't create the fact yourself or it isn't one of the default entries.
• For facts associated with a person
• No redundant facts... all redundant facts should be merged and standardized
• A woman's surname should be a maiden name.  Handle multiple marriages through relationships to the husbands.  There are cases where an AKA might be justified.
• Alternate names should be managed through AKA; you can have as many entries as you find are legitimate.
• The preferred name should be the name given to the person at birth.
• Nicknames should be managed through the Nickname fact.
• Titles should be managed through the Title fact.
• All facts should be biologically consistent (Timeline).  If the a date can't be proven through primary or trusted documents, or if the timeline isn't consistent, either give a "trusted" date range or set the preferred date blank and keep any other dates as alternative.
• Any questionable facts can be carried with the person, but should be flagged through action items and notes associated with the preferred fact.
• All facts should have a source.  The source should be graded using the star system in FTM.
• All place names should be in the proper form as defined by the Place List.
• For the Places list
• All place names should have use the correct naming convention for the mapping tool.  For family tree maker, this is {local address, cemetery, etc}, {city or town}, {county or shire, without the word "County" following the name of the county}, {State, skip for UK}, Country in standard form.  Use the place name resolver available with the tool to assure the place name matches the mapping tool.
• For the Media
• All media should be referenced as to source.  Credit should always be given to the source.
• All persons associated with the media instance should be explicitly linked to that media.
• Where possible, all media should be in one of the image formats (eg, .jpg) or in a PDF document.  It is best to put text documents in the Notes of the person.  Convert Word or other document app to PDF. 
• All your own media and creations should be watermarked and copyrighted.
• Don't forget that video and sound media can be associated with a person.  Record your relations' stories in their own words.

2022 Class 4: Detailed Instruction on FTM Features

 This class will run for multiple Class periods, its length depending on the amount of interaction.  I will show the function available in each Workspace and on each Menubar item.  (Menubar items change depending on the current workspace.)  Remember, many features have a right mouse button action list.  If you are on a Mac, turn the right mouse button function on or use a "normal" mouse.

• What a Genealogist's Home Workspace looks like
• Plan Workspace 
• Place Workspace
• Media Workspace
• WebSearch Workspace is the presentation.  Instructions on web clipping can be found here:  https://support.mackiev.com/801595-Using-web-clipping-to-save-information-to-a-tree-in-Family-Tree-Maker.  This is for the 2014 version, but it works the same.

I can provide a link in class to a tree you can download for practice if you don't have your own tree.

2022 Class 4: The People Workspace

 The People Workspace is the one you will use as the starting point and ending point of almost everything your do in Family Tree Maker.  It contains the list of people, the  tree diagram, and a list of all the facts associated with a person.  

I have found two YouTube videos that efficiently and thoroughly present the features of this Workspace.  Given that we are using Zoom and given that I likely would not be able to present the information on this Workspace any better, I am not going to use class time to view the two YouTubes.  You can do so on your own time using the following links (You can also access the videos using the YouTube list to the right of this blog post:

1. Family Tree Maker 2017:  People Workspace Part 1:  The Tree View Tab
2. Family Tree Maker 2017:  People Workspace Part 2:  The Person View Tab

Each video is about 30 minutes long.  They two videos were made for FTM 2017, but very little has changed in FTM 2019. 

I recommend also viewing the hour long video demonstrating the use of FTM 2019: 

https://www.youtube.com/watch?v=80aMSEXNs_4&list=PLn7SFqi9nFfzvh4FRmMvMfhIzM83CYyUa&index=6

These three videos should provide a solid understanding of FTM features.  

It is one thing to know the features, another to use them productively, creating an accurate genealogy.  In general, that can only come with practice AND by watching other YouTube videos that describe genealogy best practices.  Several such videos are in the YouTube list to the right of this post. 

I will use the class time to very briefly show the People Space features, but then I will go back to actual demonstrations of FTM use- putting the features together in productive workflows.

2022 Class 4: Thoughts on Tree Naming Convention

 You may have just one tree or you  may have dozens.  I have found that it is best to keep the size of your database below 10,000 individuals.  If you can rationalize a smaller number of individuals, that is better.  

• The advantage of smaller trees is computer performance and your ability to "get your head around the tree"
• You can always split a large tree into smaller trees by cutting the branches at according to some rule.  My rule is to cut the branches of my larger trees at a specific generation; ie a date, such as around 1870. 
• Another advantage of smaller trees and cutting branches at some date is that you can turn over management of that branch to someone else, someone that is in that branch.  (You are going to have to find someone to take over your work sometime.)
• I use the "Follow Tree" icon I made as a media item to indicate that the descendants of an individual can be found in another tree.  I use the custom "Tree Name" fact to name the tree to go to. 
• The primary disadvantage of smaller trees is that, when you find someone in a document or in a search and want to add that information, you have to find the individual.  Which tree contains that individual?  In ancestry.com, if you make a tree public, then you can do a search on ancestry for the individual using the Public Tree Search and (hopefully) your tree will find any tree you own with that person in it near the top.  I have a request in to permit search of your private trees.  
• There are ways to export tree contents to Excel.  I do have a macro that will provide a standard excel spread sheet and that can be used to find all such spread sheets and create an Excel Book for search.  This is very technical and not recommended at this time.

My personal naming convention has these features:

• I mirror all my trees to ancestry, so it keeps my master list  (of course I can always go to the list of files (I have one folder per tree on my computer.)
• My hobby started with the objective of creating an electronic version of a published genealogy, published in 1934, including all the primary sources as media, and updating the result to the present.  So my trees begin with the primary root person of the book:  B0001, Gov Leete Desc, as named in ancestry.  Every other tree associated with the book has the name Bxxxx, First Name Last Name, where the xxxx is the ancestry file number defined in the 1934 book.  
• For the ancestors of Gov Leete, I named the file B0001, Gov Leete Anc
• As I find other individuals to trace, I name the tree Txxxx, First Name Last Name and then either Desc, Anc, or nothing, indicating I'm going in both directions.  The xxxx is a sequential number and has no relation to anything other than the list of my trees. 
• The reasons for the Txxxx at the beginning include more easily recognizing my trees on ancestry and ability to use the short form of the tree name when creating reports. 
• The above rules apply to trees on ancestry.  On FTM, I add the string ftm{version}, such as ftm191, to indicate the version of FTM used to manage the tree.  (When FTM changes versions, the format of the database can change and usually the "password" FTM uses to access the database changes.  So I need to know to go through a conversion process when the FTM version changes. 

2022 Class 2 Ancestry.com and Configuring Resources

Objectives

• Overall computer preparation recommendations
• Browser Configuration, including extensions and addons, bookmarks
• User
• Password Manager
• OneNote
• Ancestry.com commercial site:
• guest or trial access
• features
• access help
• Ancestry.com library site
• Access
• Embed in FTM

Class Lecture

Lecture Notes: Configuring and Accessing Genealogy Resources