Family Echo – Free online family tree maker
familyecho.com
familyecho.com
Sorry but if I don't understand how you make money from my data then I'm not putting my data into it
Their Data Policy (1) says nothing about how they use data you enter. Only says you can enter as much or as little and who can see th data you share.
Big nope.
Frankly, the people likely to harm me with data are those in power - the same people that privacy laws don't apply to. Randos are pretty much at the bottom of the threat stack.
https://exhibits.lib.berkeley.edu/spotlight/census/feature/j...
But such a thing would probably have a bunch of abuse scenarios that would be hard to solve for (it's "what's your mother's maiden name" as a service, for one), and I'm not sure if they're easily solved. But it'd be really cool.
It's run by the LDS Church, so there's a religious tone to their marketing. But you don't have to be a member or religious to use it.
One challenge with an authoritative tree is when a distant or non-relative creates a profile, marks it living and then that creator disappears.
A close relative shows up but the profile is locked to the creator. The actual relative has to jump thru hoops to get access to their own family.
With privacy concerns, I don't know how to handle it better. Only that folks might want to avoid creating living profiles except for close relatives.
But on the other hand, I was just a minute ago wishing that this sort of service existed publicly as a Wikipedia-like free resource, which is a strict superset of the LDS Church having it, so maybe that's unfair.
https://www.familysearch.org/en/help/helpcenter/article/what...
And I should also point out that the Church issued an apology for that particular incident, as well.
Basic things like being able to attach sources to data points (like birthday) at time of creation.
Hilarious song and a decent viz, thanks for sharing :]
Good grief yes. Families with the same surname, with kids born in the same order and in the same years. I had a 3 pack of that in one NJ town.
Man marries 3x, all named Lilly. Siblings Smith marrying Siblings Jones. Second wife adopts first wife's name as their nickname. Siblings swapping spouses (divorcing first). Parents who reuse the name of a dead child, multiple times. Aging dad who remarries daughter-in-law's mom. Women marrying men with same surname (some related, some not).
Facts are facts (indisputable for a given value of indisputable!) but you can and I think should also record anecdotes too. Mark the data as such. A generic term for facts might be "Events" ie events in a person's life. Assign a score or an attribution or whatever works for you.
The thing about facts is that they can become distorted. Human memory is a bit ... malleable and let's face it the output from our sensors (eyes etc) are open to some interpretation. That's a bit meta!
I suggest you forget about neat little trees when it comes to genealogy. Think thicket instead, really tangled thickets.
I don't like any of the options though. It's all non-intuitive and/or irrelevant info and/or lots of wasted space on a page.
Gramps Web is distributed as a collection of containers, with a provided compose file. It works really well, if you're an HN reader with a place to host some containers and an nginx proxy for SSL.
If you ever get into genealogy you will discover GEDCOM as the lingua franca. It is/was a file format developed by the Mormons. It is a bit idiosyncratic but at least it is a standard and still developed. The CofJC&LDS (Mormons) have their own reasons for getting into genealogy and they are probably not your reasons. However it is a standard and it works pretty well. You can always overload notes fields for your purposes.
We are currently settled on Geneweb as the presentation medium for the data in TMG. Geneweb is written in OCAML and I am learning OCAML as a sideline. GW is very, very fast at some calcs and reports and a bit weird in general. It will be a while before I can request a git pull. I've slapped Privacy Idea on the front to secure it.
My personal favourite self hosted app is webtrees. It's a LAMP jobbie and well supported. Go for that, if you are starting out.
Now, one of the biggest issues you face in genealogy is what to record and even how to get that data. Be very careful how you approach the living. Human relationships are frankly rather messy and memories can be rather malleable, documentation can be wrong or illegible and so on. So your recording system has to be rather flexible. Ideally you assign a confidence score to each fact, event, anecdote or whatever.
Me and my Uncle have decided on a policy of "as close to actually happened, as possible or redact and note as such, unless the object has a hissie fit". So if your fictional aunt does not want her second boyfriend of 10 years noted, then an entry is made without a name, if she gets really unhappy about it then remove the record altogether - the living get to decide what you record about them.
That brings me around to another issue: Significant relationships - what to record and why: What are they? Marriages only? Nope. Also note that the notion of sexuality and sex are rather more nuanced these days than they were. Genealogy needs to keep apace with real life.
What genealogy really, really needs is not another website. It needs some clever kids who understand the subject matter and can come up with a decent data schema - perhaps by modifying GEDCOM. This is data that needs to be textual and ideally self describing. It needs to work in 500 years time.
Help!!!