My name is Kathleen, and I have been researching my family history since I was a child. I love to go into county courthouses and smell the old books and paper... or is it dust? This blog will focus on the stories I've heard over the years and the research methods I follow. I am particularly interested in data management and cloud genealogy.

Some of my personal areas of interest include Southern Maryland and DC (Robie, Rhodes, Grimes, Lindsey), NY state (Hill, Cookingham, Flynn, Rhodes, Skinner, Wheeler, Mead, Havens, Trotter), NJ (Parcell), North Carolina and Eastern TN (Lynch, Seabolt, Spears), MO (Wilcox, Kiddell), and CA (Simi, Grady)

I am always happy to compare notes or share my experiences, so please leave a comment!

Sunday, March 17, 2013

The times they are a changin'


I am so excited to be attending Rootstech 2013 next week, courtesy of a drawing held at Nancy Shively's blog, Gathering Stories. Thanks again, Nancy!!! 

This conference comes at a perfect time for me, because I've been rethinking how I manage my genealogy research in the era of the cloud. Two issues have been particularly on my mind: first, do I even put my family data out there on the internet, and second, how do I manage the storage and citation of all the original data that I find online?

Do I even put my family tree online in the first place?

The answer to the first question has been a resounding no until just recently, when FamilySearch  opened their world family tree project to the public. I have been hesitant to join sites such as Ancestry.com and make my family tree public because of the appalling lack of citations in so many of their trees, not to mention that I would hate to have someone appropriate my work and add it to their tree without attribution. Still, I've been intrigued with the idea of crowd-sourcing ancestors, and I've read enough about the citation, discussion, and arbitration modules built into Family Search's global family tree project to think that this time someone might actually have addressed my concerns and gotten it right.  

Quite frankly, I would be embarrassed to upload my own Gedcom to a public site in its current state -- it's a mess.  I've been researching my family since I was ten, and over the years have progressed from paper files and family group sheets written out in long hand, through several different iterations of software programs.  All this took place in fits and starts while I was studying, working, and later raising a family, so consistency is not its strong suit.  I've learned quite a lot about research methodology since I was ten, but my files reflect everything I've ever done, not just the careful scholarship of more recent years.  My children are now in college and I can devote much more time to my family history, so the first thing on the agenda is a grand overhaul of my files.  If I have to clean house and start over, I'd rather do it in a way that contributes something to general knowledge rather than keep my research hidden in a file on my computer that only I can see.

That's not to say I will use the FamilySearch project for every person in my family tree.  I'm inclined to use it for the low-hanging fruit -- in other words, when the evidence is unambiguous, and there is no question about the identity of the person, my research will go out into the world wide web.  I will continue to use my Bento templates to record my research and store evidence for those situations where it is necessary to build a case to establish ancestral identities.

How do I manage digital image files from the web?

The second question, how to manage the digital image files that are proliferating on my computer, has also been hard for me to resolve until fairly recently. As more and more original records are made available online, the process of managing them on my computer was getting awkward:  I would download a file, rename it, make sure I had the correct citation attached to each file, and only then add it to my Bento research management system (and forget about adding it to Reunion... it just wasn't happening).  


Capturing and citing sources has to be fast and easy. I've recently started using two clipping apps, which allow me to save and annotate images on a web page together with their URL. 

 "Tree Connect" is an app that saves online data as a source in FamilySearch. You can drag the bookmark button to your toolbar, surf the web, and when you find a website with data on an ancestor, click the button and that page is automatically saved in FamilySearch. You can then go in later and attach the source to the appropriate individuals in your tree.  

Obviously, the tricky part of research -- and the one area that traditional family tree software does not handle well -- are all those bits of data you find that may or may not relate to your ancestors. You can't attach them to someone in your tree, but you still need to keep track of them for building a case later.  You can certainly save such information as unattached sources in FamilySearch, but that's kind of like putting it in a shoebox under your bed -- you can't easily access the material when you need it.  I use  Evernote together with my Bento templates for research on these "potential ancestors." Evernote's webclipper, which resides on my toolbar and lets me clip data from the web, annotate it, and send it to Evernote, is the other app I'm turning to more and more as part of my online research routine.  Once in Evernote, I can then migrate the data to Bento.

Technology is changing everything in genealogy these days, so you can see that I am really excited to head out to Salt Lake City for Rootstech 2013!  I'm curious, though -- do any of you use these tools for your research?  I'd love to hear about your experiences. Anyway, if you will be at Rootstech, look me up and say hi.  Send me an email, or you can find me on Twitter as @100h2ofan.  









Monday, March 11, 2013

A postcard from your ancestors

I am very excited about a website I've been exploring this week:  Old Fulton Postcards.  It is an amazing source of digitized newspapers throughout the state of New York.  I've known about it for a long time, but never really explored beyond the home page because the title made me think it focused on the town of Fulton.  My ancestors came from another part of the state entirely, so I didn't go further -- shame on me!

Small town newspapers are especially great sources for reporting on the comings and goings of people.  I learned that one of my 2nd-great grandmothers seemed to be a local Florence Nightingale, helping out whenever people were sick.  I learned the married name of her sister, too, when the paper reported that she was visiting from Albany.  This kind of social reporting can be an absolute gold mine for providing the small details that can help knock down brick walls.  A little gem like this:


.....helped me realize that there was still a connection between distant families two generations beyond the only other one I knew about (an indirect mention of a sister-in-law in a census entry more than 30 years earlier).  I still need to work out details (first names would be a nice start) to help me identify the proper New Jersey family, but this tells me they exist.

Sometimes you can get a glimpse of an ancestor's personality.  My great grandfather comes across as a very energetic guy.  He was a horse dealer and was constantly in the paper, either advertising his horses, running them in a race, or coming up with new ideas for making sales -- too bad he didn't live in the internet era or he might have been the one to invent ebay!


And then there are those things you read about that make you cringe, and give thanks that we live in a less dangerous age:


So if you have any ancestors who are from New York.... or even visited New York.... check out this wonderful resource!


Monday, February 25, 2013

Now the bad news....

I've told you so far all the wonderful things that Bento (and the Genealogical Research System templates) can do for your genealogy research.  Now for the things it can't do....

  • Bento is not really a relational database.  It mimics the functions of a relational database with its related data fields, which allow you to link information you store in one library to related information stored in a different library.  Because it does not use sophisticated relational programming, these related data sets are essentially just "look-up" tables for information only and not for manipulating within the library that contains them.  One immediate disadvantage is that these related data fields aren't included in printouts, so you have to take extra steps to ensure the information is where you want it to be.
  • Bento is not good for producing reports.  You can export data into a spreadsheet or a tab- or comma-delimited file, but that's about it.  You cannot choose to print only certain fields in a set of records, although you can select a subset of records in any given library.  In addition, Bento is not designed to make files that are easily imported into family tree programs.  If I want to move data from Bento into Reunion, for example, cutting and pasting is the method of choice. 
  • Bento does not allow you to resize the screen horizontally.  There is so much original data online nowadays, and it would be wonderful if you could make transcriptions or notes directly from data in one screen to Bento in another.   Unfortunately Bento only allows the screen to reduce by a small amount vertically.  I get around this by switching back and forth between screens, but that leaves a greater chance for transcription errors.  If the material allows, I cut and paste data between the data and Bento, or I transcribe material into a spreadsheet or a document and then load it into Bento.  When I am researching online, I tend to have several screens open at once so I can easily switch between the internet, Bento, Pages, and Numbers.  It works, but I'd like it to be simpler.
  • Rather obviously, Bento is not a family tree software.  But boy, wouldn't that be wonderful.... it would not be too difficult to add code to existing programs that will link sources to evidence, evidence to proofs, which only then can be linked to an individual in a family.  Doesn't it make sense to have software that recognizes that you have to do the research before you can make any conclusions about a person's place on your family tree?  Don't we have the responsibility to do thorough research before we send our GEDCOMs out to take their place on the world family tree?

So.....If Bento is not a perfect tool, why do I continue to use it?  The answer is simple -- I want to track my research process, and I cannot do that adequately within current family tree software programs.  I've come up with some workarounds to make Bento work for me, but they aren't all perfect.  I'm waiting for the day that the software developers wake up to this pressing need.


Friday, January 25, 2013

Adding names to Bento from Reunion

Before you can start using Bento to record your research, the first thing to do is to establish a library of people you are researching.  The easiest way is to transfer all the names you have stored in your family tree software into the GRS "Genealogy_people" library.  I've had a few questions about how to do this.  It isn't difficult, but it does involve a few steps, so I thought it would be a good idea to show you how to do it.  I use Reunion for Mac, but the process should be similar for other products.

Reunion allows you to export data on all the people in your file or just a few specific individuals, but to keep things simple, I will explain how to export all people.  Since the "Genealogy_people" library primarily serves as a look-up table, it only contains enough data to distinguish one person from another:  that is, names, birth/death dates, and the unique "Person ID" number Reunion assigns to each individual.  It makes sense, then, to limit the data you export from Reunion to just those fields.

In Reunion, you export a text file by going to File=>Export=>Export TXT.  Select the people you want to export ("all people") and select "comma" as the field separator.  Click the + "Add Field" button to select the fields you want to export from the drop down menu:


  • Under the heading "Names," select "Last Name" and "First and Mid Name"

  • Under "Events," select "Birth-Death"

  • Under "Numbers," choose "Person ID #"

When you are finished, click "Export."  A window will open to select your destination file, which will be in a .txt format (even though you selected commas to separate the fields in your export!)  Note that Bento will not import files with a .txt extension.  However if you change the .txt to .csv (comma separated values), Bento will import the file without a problem (and it won't affect the integrity of your file). 

To add this file to Bento, open the GRS and click on File=>Import=>file and follow these steps:
  • Choose the file (the .csv file you just created)
  • Choose a target library ("Genealogy_people")
  • Set up the import (make sure that the data fields you are importing are the same as the ones in the Bento library, so the data maps to the correct field), click "import" and your "Genealogy_people" library is now populated.


As you use Bento in the course of your research, you will inevitably come across new people to include in your family tree.  It would make sense that you could reverse this process and seamlessly export new people from Bento back into Reunion.  

You can, but it isn't easy or seamless, so I'd better tackle that another day.  


Saturday, January 19, 2013

Use the smart collections!

So all your research data is recorded in Bento -- how do you get it out?

I love the basic search function, which quickly retrieves any word or word combination you enter into the search box (located in the upper right corner of the page).  This actually takes care of most queries, and will easily locate all the entries that include the search term somewhere.  You can search on word fragments, too, which allows you to pull up spelling variations.  Here, I entered "lind" to pull up both Lindsey and Lindsay.  When I enter data into Bento, I try to be consistent and include both spellings in the keyword field, but sometimes I forget, and using truncated search terms covers me.  To tell you the truth, Bento's search feature is so useful that I've stopped using the keyword field entirely.


Sometimes, though, you want to focus your search with more precision.  Command F will bring up the advanced search option, which allows you to pinpoint the field(s) you want to run your search in. You can specify if all search terms must be met ("and" search) or if the term can be present in any one of them ("or" search).


And....then there are the searches that you run all the time.  Smart collections are a great feature in Bento, allowing you to save the queries that you use most often.  The "smart" part comes when you add new records to your database.  If they match the query you've set up -- they are automatically added to the data set you see when you open it.  Smart collections are very easy to set up, too.  Just select Bento > File > New Smart Collection, and type in the search parameters you wish to use and give it a title.

One important note:  it may seem obvious, but a search in Bento (or any other database) will only return the information you put into it.  In other words, if the smart collection queries a particular field and you haven't entered information in that field, that data will not show up in your search.  This is why I have put all the various checkboxes in the data entry pages!

Now for a rundown of the Smart Collections I've set up in the Genealogical Research System:

I.  Sources Library
  • Finding Aids:  returns any record that I have identified as an index (via a checkbox on the source entry form).  I think it is very helpful to keep copies of all indexes that I transcribe, even after I have found the records they keep track of.  You just never know when something that once seemed irrelevant suddenly takes on a different meaning in light of new information.  I just like to have a quick way to retrieve my finding aids.
  • Online Sources:  returns sources (of any kind) that are found online.  I like to use this as a research log of my online activities.  If you use the GRS, you can do this by setting the smart list to sort by date of search (when you are in the "online sources" smart list, click on the small downward arrow to the right of the "date of search" field header in the spreadsheet view, and click on "sort descending;" this will order your data set with most recent on top).
  • Hardcopy Sources:  this smart list was designed to serve as a research log for trips to libraries or other repositories, and is already set to order the data by date of search and name of repository.
  • Sources without Evidence:  returns all sources that do not have evidence linked to them.  This is a good way to double check your work.  I don't know about you, but much as I want to, I can't always devote full time to my research.  Sometimes I'm on a roll -- I find wonderful sources, and download or transcribe them into Bento, but then run out of steam somewhere before I get around to thinking about what it all means.  I don't want to rush at this stage; it's so important to give the evidence a lot of thought.  But all too often my attention is shifted to something else in my life before I get around to it.  The "Sources without Evidence" smart list is so helpful when I am able to get back to my research.  I just open it and I'm instantly reminded of what I was working on last so I can turn my full attention to the work of evaluating the evidence (this is another smart list that you might want to click on "sort descending" in the "date of search" field).
II. Evidence library
  • Census evidence:  returns all evidence that comes from the census (assuming the appropriate data was entered on the "evidence citation" form in the Evidence library.)  A great way to see at a glance all the census evidence you have for a particular individual or family is to run a secondary search on the name from within the Smart Collection.
  • Flagged evidence:  I use this as a way to quickly identify the records that I want to re-examine or re-evaluate in some way.  It functions much like the "sources without evidence" smart collection in the Sources library.  
  • Need to find non-derivative sources for this evidence:  returns all records that are not original sources.  I use this list as a tool to identify weaknesses in my data and find better quality versions of these sources.
  • Uncertain connections: returns all evidence that I am not yet able to attach to a known person in my family tree.
  • Need to enter data into family tree software: returns data that I feel confident is "proven" sufficiently to include in my family tree (how this is done and whether I do it will be the subject of a future post!)
  • Needs further definition of research parameters:  returns records that have been identified as "needs further research." 
  • Evidence that relates to a current research theory: returns records that have been identified as "relevant to a current research question."  
  • Export text:  identifies records that I have entered text in a field called "export text."  This tells me that I have prepared data in these records that I can cut and paste and add to my family tree software in the notes field for a particular individual.  If this sounds a little cumbersome.... it is. 
Next time I will write about tasks that I find Bento to be.... well, less than useful.


Friday, August 24, 2012

DNA: a recovered past

I've been away for nearly a month on a wonderful adventure with my family, and I have lots more to write about my Genealogical Research System (and photos will be posted on my art blog)..... but all that will have to wait until I get over jet lag and clear the backlog of stuff  that always accumulates after a trip.

I do want to share an amazing thing that just happened, though.  Just before I left, my father agreed to submit a DNA sample to see what we could learn about the deep history of our paternal line.  When I returned, there was an email saying the results were in, and oh, by the way, you have an exact match.  I was pretty excited, especially since this line is a fairly common surname and represents my "brick wall."

So (jet lagged or not) I contacted the match, asking if we might be related, and she responded almost immediately with a resounding YES!!! As it turns out, Carol is my second cousin once removed, and while we didn't resolve our brick wall, now there are two of us working on it, and it doesn't seem like such a lonely job anymore.

But the real wonder and miracle of this is Carol's story.  You see, she never knew her blood-surname.  There was a family dispute in her grandparents' generation in which one parent betrayed another, and the betrayed one vowed never to have anything more to do with the other.  She took the children, forbade the father from ever having contact with them, and changed their surname.  How she managed that in the small town they lived in is a mystery to me, but Carol's father grew up not knowing his family, although they surrounded him silently, unable to reach out.  Years later, when he learned the truth, he discovered that one of his aunts had even been his school bus driver.

Carol and I spent a long time on the phone, sharing our family stories.  I was startled, but not surprised, to hear that deep blue eyes are a strong feature in her family, because that's something that stands out in my family, too.  As we talked, it was clear that for Carol, making this connection was more than just finding another name on the family tree -- this was about personal identity and belonging.

One reason I am so passionate about genealogy is because family itself is so important.  Knowing our family -- for better or worse -- places us in a context.  The "I am" statement cannot exist in a vacuum.  Things we think of as ours alone (that singing talent, the academic propensity, even our blue eyes...) more often that not are rooted in our genes.  We pursue those deep genetic ties because we realize that at some point, we are all related, we are all one family.

Post Script:

I sent this post to Carol to read before I published it, and she replied with a poem she had written a few years ago:


Daddy said he loved me as he held my hand.
He told me to always remember my family and never forget who I am.
I said, I will never forget Daddy.
He smiled at me and we walked.
Mommy said she loved me as she moved a stray hair from my head.
She told me to be brave and always look for goodness and never forget to forgive.
I said, I will never forget Mommy.
She smiled at me and we walked.
They died that day, on that walk.
But I never forgot.
I never forgot.
I looked up at the sky and smiled as I walked.

Carol Ehrenreich

Saturday, July 21, 2012

Using the GRS to record evidence, assertions and proofs

I'm assuming that anyone reading this is already familiar with the work of Elizabeth Shown Mills, and especially her gold-standard reference work on analyzing and citing evidence: Evidence Explained.  If you are not, drop everything and read it!  She is one of the most respected scholars in the field of history and genealogy, and has worked for many years to raise the standards of research in genealogy to match or surpass those in any other academic field of study.  

The Genealogical Research System of templates for Bento is a tool that helps you enter your research data in a manner consistent with the requirements that we track the quality of our data and not just the quantity.  It also provides a framework for analysis -- it won't do the work for you, of course, but it does  provide the outline, and that will often make the difference between doing the work and skipping it.

Like everything else in the GRS, evidence analysis is designed to be accomplished in stages.  The first step comes when you are entering basic information about your source in the Sources library.  Data reliability rests heavily on the type of sources you use, so it is important to record information about the physical nature and quality of the source in the "source evaluation" form:

    1. Choose from a list describing the type of media you are consulting, whether it is a book, document, digital image, and so on.  
    2. Describe the type of source you are examining, whether it is the original form of a document, original index, official copy, transcript, abstract, index, etc.
    3. Describe the category of information provided by this source, such as newspapers, wills, land records, burials, etc.
    4. In the notes field, include any other thoughts you have about this source: physical condition, legibility, missing pages -- anything that may affect its reliability.

    When you are ready to enter all the evidence from a source into the Evidence library, you will be asked to record additional information about each separate piece of evidence it contains -- keeping in mind that you may repeat this exercise for many different pieces of evidence from the same source:

    1. Check the box marked "direct evidence" if this evidence provides a specific statement that answers a research question.  In the example shown above, the source (a daybook written by the brother of an ancestor) directly stated that Rachel Grimes died on 18 June 1852; an indirect piece of evidence might have been a simple note that he went out to buy mourning clothes.
    2. Check the box marked "primary informant" if this evidence is from a source that had first hand knowledge of the event.  In this case, I assume that Thomas Grimes knew for a fact that his niece had died, because of their relationship and physical proximity.  I would not have checked the box if he had written that a Mr. Lindsey had told him about the death of a mutual acquaintance in Kentucky.
    3. Check the box marked "original source" only if you are using a source closest to the original as possible.  In other words, do your research and make sure that the source you are using is the one closest to the original.  I've embedded the Sources library as a related data field at this point, so information about the source you used is readily at hand. Obviously if you looked at an abstract or compiled data of some sort, this will remind you to seek out and review the original. (Following Dr. Mills' guidelines, I consider a digital image of a document from a reliable online provider to be equivalent to an original source, but rely on the notes that you make when you are looking at the source when deciding whether to check this box.)
    4. Discuss the nature of the source and your conclusions in the text fields.

    The Assertions & Proofs library contains a further step in the process of analyzing your data.  In this library, you identify a research question, and assemble the evidence that you have gathered.


    What this template does is give you a framework for looking at a particular research question, and seeing the arguments for and against your hypothesis together in one place.  This way, you can keep tabs on the current status of your research at any given time.

    Of course, all this works only if you think of these templates as an active part of your research process and not just a place to store your data..... but I'll write more about that another day.