The pedigree view you currently have is important for seeing more than the direct lines; however, it is equally important and more efficient to see a horizontal chart with direct ancestors of your matches. The ability to see that first and then go to the chart as you currently have can speed up the hunt for a common ancestor. It saves much time.
I would love to see a filtering system for smart matches similar to what we have for PedigreeMap. In PedigreeMap, we can select a person of interest and the filter by their "Extended Family", "Immediate Family", "Ancestors" or "Descendants". This would be incredibly useful for Smart Matches and Record Matches as well. If I'm currently focusing on a particular portion of my family tree, it would be great to see all the smart matches which are relevant only to that section (without having to check the matches for each person individually).
Source Citations matched through Record Matches populates on an individual's profile page. This clutters the profile and would be more helpful if an option was created to match the citation to single or multiple events (i.e. birth, marriage, death, etc).
The Tree Consistency Checker report is FANTASTIC. I would like to see something similar for Smart Matches and Record Matches. What I am envisioning is a report which reviews all of the Confirmed matches and identifies those which are inconsistent with your tree. For example:
Birth Year differs by more than 10 years (possibly merging a parent and their similarly named child)
John J Smith was born in 1874 in your tree, but in 1861 in a confirmed match with Bill Jones' tree
Mary Smith is the daughter of Tom Smith and Ellen Smith (born Frank), but the daughter of Tom Smith and Mary Smith Sr (born Collins) in a confirmed match with Frank Smith's tree
This would be helpful for identifying any of the following situations:
You have a single person in your tree who is matched to two different (but very similarly named people) in other trees
You approved a match based on consistent data but have since made changes to your tree based on new records and the match is no longer consistent
You approved a match based on consistent data, but the person whose tree you matched with has since made changes to their tree based on new records and the match is no longer consistent.
Smart Matches and Record Matches are WONDERFUL, but they can also be very overwhelming especially when your tree gets large. I would like the ability to either hide (or approve en masse) all matches where there there is no new/different information between my tree and the matched information. This way, I can focus my attention only on those matches where there are "New", "Improved" or "Different" pieces of data that I want to do something with.
I commonly see cases where I'll add a person to my tree and get 50 smart matches. Once I've reviewed, approved and copied over the data from the first 2-3 of them which are true matches, then the other 47 are all redundant and it is tedious to go through and approve them all.
Venho por este meio fazer 2 sugestões que me parecem uteis.
- Tenho 2 irmãos casados com 2 irmãs e não existe forma de as ligar, obrigando a repetir a irformação de um dos irmãos, da cunhada e dos descendentes no ramo familiar delas.
- Quando há divórcios, poderiam colocar uma opção para sinalizar se o cônjuge retirou o nome de casada ou não, permitindo construir o nome de forma correta e não perdendo a informação dos nomes de solteira e casada.
Agredecendo desde já a atenção dispensada, cumprimentos
Finding location logic a bit strange, i.e. Bedford, Cape Province, South Africa, finds a Texas location, Google finds this location correctly. Logic seems to look for street address first, as if it cannot find it seems to map elswhere even if the correct country exists. Lots of locations in historic documents no longer exist or have been renamed, generally the country names are constant, so logic should look at this first?
Now that you are offering DNA tests, it really would make much more sense to offer a horizontal pedigree view (i.e. descendants on the left, ancestors on the right instead of the bottom and the top of the screen) so that when I go to look at somebody else's tree, I can see their ancestral lines much easier. Currently it is usually the case that a match's ancestral lines are so far off the edge of the screen to the left and the right that it is essentially impossible to see their ancestral lines.
It is SO MUCH EASIER to view a pedigree horizontally rather than vertically when all you really want to see is the ancestral lines.
I made this same suggestion to Family Tree DNA previously, and they have now implemented it. Ancestry has always had the horizontal view available.
I work preferably in English, however whenever I am back in The Netherlands it switches to Dutch. It would eb great if you could select your preferred language in your profile to avoid having to toggle it depending where you are in the world.
'Huwelijk' is the same as 'Marriage'. Nevertheless I have records in my tree where the tag 'Huwelijk' is used in addition to 'Marriage'. Would be great if 'Huwelijk' is recognised to be the same as 'Marriage' to avoid duplicates and avoidable suggestions.
It good be nice to see in the tree whether all the matches have been reviewed. For example green if all are reviewed, yellow if some are reviewed and red if none are reviewed. Same applies to smart and record matches.
Would like to compare my tree against another tree to find smart matches. I know the system runs smart matches and sends me hundreds of possibilities, but there are times when I'm looking at a potential relative's tree and would like an instant search for a connection. Thanks.
Verifying Smart Matches and Historical Record matches is work. It's work that benefits MyHeritage customers and MyHeritage.
Provide an incentive for those who only use free MyHeritage accounts to do that work, and increase the value of MyHeritage data for paying MyHeritage members. Provide credits to those who do work to verify or reject matches.
Allow those who only use free MyHeritage accounts to use those credits to contact other members of MyHeritage.
What I find needed is cloud integration since there's no document center. A document center can be created by using cloud integration similar to DocHub or any other cloud drive. Even though this is commonly everywhere we're linking to our backweb especially since there's domain mapping. We have bylaws, ordinances, finance docs etc that's necessary. Typically this is done outside on another network, but the blood-line integration is necessary.