Family Historian User Group

Thanks Mike for the clear explanation. I'd been playing around with sets, but didn't get the syntax quite right! One criticism I would make of much of the patterns material I have read recently is that it gets too complicated too quickly. Lots of practice with simpler examples like this first! My fi...

Thanks Mike, it was a few days before I was able to sit down and have a go at this, but it turned out to be quite a good first learning example! I've now got a simple script that updates most of my media records perfectly, but fails where the title is more complex. For a general media title, "Event ...

This is timely, as I was looking at Lua for updating my media records. I have a large number of undated media records (images of source records) imported from FTM , and I want to add dates to aid reporting and sorting. My media titles are very structured, so I was thinking of two different scenarios...

This is quite an old thread now that has probably run its course, but for completion I include below my final crib sheet for my FTM - FH migration. It is slightly high level rather than detailed "how to" instructions, and parts will be specific to my recording style and use of Excel as a GEDCOM proc...

One final refinement - I have split out the source splitting and general format tidying into two separate workbooks, as they perform different functions and the latter is purely optional (a neat and tidy import to FH rather than hundreds of comments in the log files). The source splitting is now com...

Indeed - as somebody who's only a couple of pages ahead of you, my impression so far is that FH is strong on GEDCOM compliance, flexibility and transparency of its data structure, but that adherence to GEDCOM comes at a cost, as GEDCOM is not a proper database language so does not handle duplication...

Thanks Mike - I was aware of the All tab of course, as it is clear on screen and frequently referred to in the documentation, but I still don't like the fact that the summary shows one note without alerting the user to the extra detail available there, and doesn't refresh after editing. So it is not...

PS - In principle, it should be possible to generalise the code, such that it reads the input GEDCOM file, presents the user with a list of all the lumped source titles (GRO Birth, Probate Calendar, etc), and asks which ones should be split. Food for thought later......

Hi David, Unfortunately, Excel macro code only works in "proper" versions of Excel, so not Open Office, not LibreOffice, and even not Excel for the iPad!! I've been away from this project for a few days as I've been busy with other things, but before I fully commit my data to FH and regard that as t...

Indeed - in the absence of more precise data, my entered birth date is usually just a "best guess", and always qualified by "about". Death is generally the month of burial (unless very early in the month), and again always qualified with "about". I started out leaving both of these blank if I didn't...

A related thought - for direct ancestors a certificate is essential, but for more distant relationships I do cite the index entry to support an Event, particularly if there are other corroborating data. My problem is how to record the Event date. For marriages, there is no issue as the event is reco...

Sorry, was being slightly lazy, as I was doing the Forum on the iPad and couldn't remember what the plug-in was called :) . I was thinking of List All Citations for a Source . If there were hundreds of entries to check, it might be useful to flag where Where Within Source is the same, but Text From ...

I understand what is happening now. It's mentioned in the Knowledge Base, but worth highlighting as it is a fundamental difference compared with FTM that could trip up the unwary migrant (me, for instance :) ). When any citation from a lumped source is used in more than one "Fact", each citation is,...

Worth commenting that I've been experiencing similar issues using Microsoft's OneDrive recently (albeit not in FH yet). There's probably a general "beware" message there regarding real-time synced backups that are dependent on an external network connection.

It did raise a more fundamental question in my mind about how FH manages sources, but I'll do some experimenting over the weekend to explore. If necessary, I'll start a new thread in the general FH use bucket, as it is not specific to importing or macros...

Mike, Thanks for the detailed comments. It wasn't my intention to produce a universal script that would be useful across many different record keeping conventions, but really just to tidy up my own data prior to importing into FH . I suspect that for the experienced plug-in author, that would be the...

Helen, Yes, images came across fine. A typical entry is shown below: As exported from FTM as a lumped source: 1 CENS Retired Policeman, age 62 2 DATE 31 MAR 1901 2 PLAC Walpole St Peter, Norfolk, England 2 SOUR @S7@ 3 PAGE RG13/1557 folio 22 p1 (#1) 3 DATA 4 TEXT Appleton Croft, Walpole St Peter, NF...

Thanks for the quick reply, Mike. Indeed, plug-ins and the transparency of the data storage in standard(ish) GEDCOM were two big pulls towards FH. I wanted to give FH as clean a dataset as possible in order to minimise dead time from reworking old data, and concentrate on playing with the fun new to...

Full place names (e.g. Wolverhampton, Staffordshire, England) are great for removing ambiguity in external connections such as Ancestry/FMP hints, but they get a bit tedious seeing them repeatedly in printed trees and reports (as well as taking up a lot of space!). Family Tree Maker had an option to...

Having just migrated to FH from Family Tree Maker as a result of recent changes with the latter, I was faced with having to change around 700 or so detailed census records from the “source lumping” that is at the heart of the way FTM is structured (and generally does a pretty good job with) to “sour...