There has been a lot of traffic on the Legacy Family Tree Users Group email list (aka the LUG) regarding recording historical vs.current locations for a given event. As several people have pointed out, genealogical best practice is to store the location as it was at the time of the event. But others have valid points when they state that this makes for confusion when reports are generated for non-genealogist family members, hinders mapping and makes for a “messed up” master location list. (If there are multiple entries that point to the same geo-location, is it really a “master” list? Guess it depends on your definition.)
To be honest, in my own Legacy database I’ve been a little wishy-washy and inconsistent with this. Wanting to do the “right” thing, I have in some cases recorded the historical location. Other times, I have just gone ahead and put in the current location, particularly when the source I’m using records the “current” location. (Like a book of records for a church in what is now Montgomery Co, Pennsylvania but was previously Philadelphia Co., in which case some of the earliest data recorded in the record book happened in the Philadelphia Co. time period) I also have to admit that, although I have intermingled current and historical locations in the master location list, it really bothers me to do so. Why? Well there is no clear and highly visible way to distinguish historical from current. Nor is there a way to link historical to current other than adding a note – and that isn’t readily visible.
It seems to me a more logical implementation would be to allow both a current and historical location to be added to an event – and also to distinguish between historical and current locations. After all, an Historical Location is really a specialization of a Location. It has all the attributes of a Location, with the additional attributes of a date range and a pointer to the current. Of course, if Mellinnia Corp. (makers of Legacy Family Tree) were to provide something like this in the future, a user would have to go back and identify the historical locations already entered into the master list, add the relevant dates and identify the associated current location. Once that task was completed by the user, Millennia could probably provide an automated utility to go back and determine if the originally entered location was historical and if so find the associated current and make the appropriate updates in the event data record. Going forward, entering the current and historical locations (if necessary) would be up to the user.
Just tossing this out to maybe get some people thinking. It really does seem like a problem that could use a solution!
It seems that the whole genealogy community is buzzing about the recent RootsTech conference – and with good reason! I was one of the unfortunate many who could not attend the conference live, but was able to catch a bit of the excitement by watching several of the presentations that were streamed live on the internet. So here goes with some general observations.
In viewing the presentations, I also realized that I’m under-utilizing some important resources – especially maps. LegacyFamilyTree has built-in mapping based on Bing. But I have been unable to get it to work on my relatively new Windows 7 computer. The LegacyFamilyTree website says that their mapping requires IE7. I don’t use IE, but have version 8 installed on my computer. I am reluctant to go back to version 7. After seeing some of the RootsTech presentations, I’m going to look into using GoogleEarth tours and possibly some basic mapping with GoogleMaps. It won’t be integrated with Legacy, but I guess you can’t have everything. :(
While I enjoyed each and every presentation that I saw, the topic that got me most excited was the Google presentation segment on Historical-data.org. In a nutshell, this is a way to add semantic information to a web page in order for the search engines to better assess it’s relevance to a “genealogy search.” I even went so far as to start to update one of my obituary web pages by defining my ancestor Augustus Bechtel as an HistoricalPerson. I did this after the Historical-data.org schema definitions were touched upon in the Day 1 keynote address. I wasn’t sure how to define the HistoricalDates and felt vindicated when watching the Google presentation on Day 2, when the speaker said even the large companies they were working with struggled with this. They (Google, et al) are promising to add examples to the Historical-data.org blog, and you can just bet that I am now subscribed and waiting for that post! I even put in a product enhancement suggestion for LegacyFamilyTree to add this to the webpages that Legacy generates. (Crossing fingers that they at least consider.)
That’s about it for now. As I try out some of the software and concepts, I may post follow-ups!