I'm doing research about my wife's family in Kenya, most of who are/were (nomadic) pastoralists. Clan & tribe are two very important concepts when relating to each other. How can I add those in Family Tree Builder?
I'm also wondering how to enter age groups, as a (male) individual always belongs to an age group that follows him through life (and also helps in estimating year of birth, since that often is unknown).
I'm still in the process of deciding if Family Tree Builder/MyHeritage is the best software for this job. I don't need to be able to search any online databases, virtually all the data will come from living persons. So basically I only need software to enter that data myself, and preferably either via web, desktop or mobile app (all of which MyHeritage/Family Tree Builder has).
Clan & tribe are two very important concepts when relating to each other. How can I add those in Family Tree Builder? I'm also wondering how to enter age groups...
Custom Facts would probably work for this. The function is described briefly on p. 107 of the User Guide (access it in FTB from Help > User Guide) but is not in the FAQ (except to say that "FTB 4.0 supports custom facts").
For any individual, open the record, click the Facts tab>New Fact>Enter a Custom Type. You would create a custom fact for Clan, another for Tribe, a third for Age Group. Then for each individual, you could enter the data for each fact.
Unfortunately, Custom Facts can't be accessed in a Custom Report, which means that you can't sort or group your family by Tribe etc. I'm not sure if Custom Facts appear in ANY report or chart. It's not mentioned in the Guide or FAQ and I've never checked in my own work.
Another possible workaround is Facts Tab > New Fact > General. There you will find "generic" fact fields called Fact 1, Fact 2, Fact 3.... You could use these for Clan, Tribe, and Age Group respectively. These generic fields are available for custom reports (but only the Date and Place, so be sure you put the Clan etc. name in the Place field).
You might try renaming "Fact 1" as "Clan". It will remain that way in the individual record, but you will have to rename it for every individual. The custom report will still say "Fact 1". However, it's easy to rename the column in your spreadsheet so that's minor.
There is the possibility for tremendous power in these generic and custom fields but MyHeritage has not yet put them in a form where they are as useful as they might be, and they are totally overlooked in the documentation (as far as I could find).
I'll use custom facts then. Although it feels odd to use Place for clan, tribe or age group. I suppose I rather wait for MyHeritage to add those fields to custom reports. At least I can see the custom fact in most default reports and I can filter by the fact when creating a custom report.
But indeed, more customization possibilities for custom reports would be a very important addition.
At least I can see the custom fact in most default reports and I can filter by the fact when creating a custom report.
Whoa, careful there. You can't filter by a custom fact when creating a custom report. I've tried it, it doesn't work (to my great frustration). Custom "facts" are not recognized as facts by the system. That's why I suggested using Place, which is recognized as a fact in custom reports, so you can filter and sort by Place. It may feel strange but I think it will work.
This is an example of hazy and confusing nomenclature by the MH developers. The "custom facts" are more like "custom text". We can only hope that they fix this in a future build so that Custom Facts are facts to the system and available in custom reports.
Aha ok, I actually never tried filtering by custom facts, just saw that it's available.
I'm also weary to use Place for custom facts that are not places for the reason of integration with other genealogy tools. That is, a GEDCOM export should recognize the fact in a way that can also be imported to other software. But maybe the GEDCOM standard hasn't come that far yet, or other software might not know how to interpret it anyway.