At first thank you for this great site! As the moderator of our family tree, I'm using it on a daily basis, and I would have a suggestion/question concerning the Family Photos, as this is the most visited page of our account.
The page in question (Family photos, Albums) always starts with the first album, "Recent Photos" opened. Unfortuneately, most of our (elderly) family members do not realize there are more albums at all on the left side, and they would only click on the recently uploaded photos.
Is there any way to achieve that the first album which is showed is an album of my choice? (i.e., is there any way to remove "Recent Photos" from the top?) If not, would you concider such an option in a later version? The best would be just a single starting page, showing links to all the folders we uploaded.
As you may know, your ideas are very valuable to us. As we currently are able to manually type our case sensitve information, it sure would be easier to have an automatic option such as a case sensitive merge, or, even an option to merge information in a way that would allow you to keep your upper case or lower case structure throughout your font structure. Our goal is to never stop making our research tools easier to use upon popular demand. I've forwarded your feedback to our web developers for consideration.
Having said that, feature requests are prioritized according to how many users write to support about them and how much resources and time they require of the team. Some features that seem minor may actually be related to the infrastructure and require major changes that effect many other features. Please take this into consideration.
I disagree. I am one of the 'offenders' and I have, in my opinion, a very good reason. My primary audience is not genealogists or other myHeritage users, but my family. I capitalize the first names and include titles, if any, of direct ancestors, so that it is easier for my family members to trace direct descent. This comes in very handy when parents have more than one child. Other myHeritage users are certainly welcome to the information on our 'Stamboom', but if they want to use it, they have to go through the trouble of copying it manually. I have learned never to do an indiscriminate merge or even copying job, because the one time I did, things got hopelessly messed up. Furthermore, the manual method forces one to double-check the accuracy and usefulness of the information, which is essential especially re: dates.
I do not undertand YOUR logic- if you want to make it difficult for the other users - by being determined to use uper case at the expense of almost ALL others- what do YOU gain.
I can see that YOU might want to edit each and everyone's data- but if you are confident that YOU are provideing Clean data then, logically, anyone should be able to import your illustriuos work-- but they cant becuse you have a misguided approach to impoerting data into YOUR database-
If you had correct case then others could import and atTHEIR reisk and nothing to do with your structure-
I just cant see where you get the gain- but all others are disadvantaged.
Hi, I have to agree with Ingrid. Many use the Uppercase for the first name of a person even though I dont. Many systems does not support first name indication. My name is Bo Anders and is called Anders. I hate when I get mail with "Dear Bo" since most assume that the first name in the list is the correct one.
In the nordic countries we used patronymikon naming convention to the late 1800s which mean that the last name is given by the fathers first name. So I.E a father with the name Nils Erik Johan Andersson had children with the names Peter Eriksson and Lisa Eriksdotter since the fathers first name was Erik. So by indicating this with Nils ERIK Johan Andersson is a simple way of showing this. We see many examples of errors from decendant from emigrants that dont know the patronymikon use and would use in my example the names of the children as Peter and Lisa Andersson and even worst Lisa Andersdotter. We also see Peter Nilsson and Lisa Nilsdotter. And yes, we use double s in the last names because it is Eriks son and Eriks dotter (daughter). Most emigrants droped the extra s and started to use family name when they emigrated to the US.
As you can see there will be many cases of mistakes when following up parents/children when not using the correct names.
Anders--You are absolutely correct. I hope MH does NOT force us into a straightjacket of using letter case in only one way. Just in my own family, which includes many nationalities and a good number of centuries, naming conventions vary all over the place and I should be able to 'systematize' in ways that make sense to me and my family. I also use asterisks to alert visitors that there is a lot more narrative information in a person's biographical section than can be squeezed into the various automatic categories. If that is inconvenient to non-family members or users who want to do indiscriminate whole-sale mergers or un-checked copyings, that should not be my concern. I am not denying access to information. People who want it just have to work a little in order to use it. Although, if I get more guff, I may just make the whole site completely private and not be bothered with complaints I am not interested in addressing. Over the years I have also become very careful about whom I invite to become a site member and I have disabled the automatic invitation included in the smart-match function. Those interested have to actually ask to be invited. Have a great genealogical 2014!--Ingrid.
I'm just digging through my Smart Matches. Unfortunately, I can see more and more from different family sites x-times the same familytree with exact the identical matches over and over again. I'm loosing slowly the motivation to check & click this matches and I began to kick this familytrees into the 'ignore'-bin.
It looks like many users don't realize, what an overhead they produce with this kind of creative version handling of their familytrees. It's really hard if You want to work with Smart Matches seriously.
It would be very useful, I think, if MH/Support/etc. write an info to the user community about this problematic.
I have at least one site with eight trees but he is reliable; I can confidently check the first tree and if it is right I just confirm the rest. But I had one with maybe sixteen and she made a lot of mistakes. Certainly they are a pain.
I think the issue is made because people do not understand that when they add or maodify a tree and then SAVE AS- it becomes a extra tree. I think some users are unsure if they save the NEW tree then the OLD tree has gone. So for saftey sake thay generate another tree with just a few changes.
If they saved OVER the old tree then only one tree would exixt.
There are many users who have trees numbered Trial1 trial2 or Test1 and Test2 and obvioulsy have not got a clue and sadly myheritage will not intervene - even in a role as mentor or advisor. I think myheritage COULD be more pro-active in preventing users form haveing more than one tree BUT could issue " premission: if the user could define a reason for more trees and was legitimate and not a repeat after repeat.
It would be a much more productive and uselfull resource if we could all be more attuned to the wider comunity and prevent the overwhelming passion for duplicated trees.
MyHeritage provides people with a platform to enter their family history to which we are also aware that people sometimes create duplicate family trees that can inturn provide you with many SmartMatch results however they are all the same information.
In this situation there are two options that you may try.
1. Ignore the family tree that you are being matches against by going to Family Tree > Smart Matches™. Sort the matches ‘By family trees’ (this is the default setting). View the matches that you have with a specific site. Next to each person’s name, you will see the ‘Review match’ option, which will take you to the Smart Match™. Below the match is a link to the consensus page for all of the matches for that individual.
Above the list of all the matches is the option to ‘Ignore this tree’:
2. Contact the site manager from which the matches are coming and notify them of their possibly innocent mistake and that it might be an idea to delete one or more of their duplicated family tree's.
Within the Help centre there are links to show how to delete the family tree's from both the online family web site and also the Family Tree Builder Software.
I hope this has proven useful information to you all and should you have any further inquiries, problems or questions then please contact us at support@MyHeritage.com and we will be only too happy to help.
In regard to the explanation by Team member Dean.- I think you expressed the situation extremely well.
The difficult thing (from experience) is that if you attempt to contact the user who may have ,in error, published duplicate data- and that user is no longer a valid subscriber, then the contact attempt is futile.
I would like to see MH take a more responsible attitude when circumstances like this occur, and MH should either annotate the file as - misleading, duplicated, and or user - now defunct, so although his.her data might remain, the possibilty of contact is negative and a lot of time wasted just waiting for a reply the cannot ever arrive.
Genealogy is a frustrating hobby - but could be more productive if the resources lke smart match were better managed by the only prople who can manage- the MH team.
When I see the list of "attributes" for a person on the consensus page the are many times when I can see that many of the suggestions are for another person because of the dates and/or relatives. I would like to click on one of those fields and get a page with only the records for that subset. This would allow me to confirm or deny all the records with a given set of dates or parents/wives etc.
We now have a new technology called "Record Detective™", It is the first technology of its kind to automatically extend the paper trail from a single historical record to other related records and family tree connections.
Record Detective™ generates new leads and discoveries by turning a single record into a door to more. For example, a record discovered in MyHeritage’s digital archive, SuperSearch, will now automatically include a summary of additional records and individuals in family trees relating to it, providing new information and clues to take your research to new directions.
Record Detective™ essentially turns historical records into smart objects that determine which people they are about, and it automatically conducts additional research about those people. Historical records are invaluable to everyone interested in their family history. With over 4 billion records available, MyHeritage provides a wealth of documents enabling you to make exciting discoveries.
You can learn more about any record or profile provided by the Record Detective™by hovering over its thumbnail. The summary will show a confidence score, ranging from a half star to five stars, indicating the likelihood that the historical record correctly belongs to the associated individual. Click the name of the record or person, which are links, to view them in more detail.
Hover the mouse on the record’s thumbnail to reveal a tooltip with a detailed summary of the record and the confidence score of this find according to the Record Detective™.
That feature has nothing to do with my suggestion concerning the SmartMatch Consensus page.
I oft times get 50 or 60 matches for one individule. The smartmatch function many times will try to match with 2 or more OBVISOULY different people. The birthdates are 50 years apart, the names of the parents are different etc.
I currently look to see whether there are more correct matches of more mismatches.
I then go through each entry and only confirm the good ones or deny the bad ones.
I then group deny or confirm all to take care of the rest.
If there are questionable matches then I must research them before I can continue.
If I could select the subset of records with the obviously wrong birth date or obviously wrong set of parents and deny them as a group, then select the subset with the obviously correct data and confirm them as a group then I could concentrate my research on the ones that are left.
This would increase my speed and accuracy and decrease my fustration and irritation with a function that needs LOTS of improvement.
Hi, I've tried working out how to do this and I can't so I post this in the hope that someone can advise me, or failing that to request it as a feature:
I know I can set up past events, e.g. military action at <place> on <date> for someone in my tree, but what I'd really like to do is enable that event as an anniversary event, similar to birthdays and wedding anniversaries. Obviously the 'floating balloons' image probably wouldn't be appropriate, but I'd like to be able to remind the family members who look at my tree that on date <X>, this relative was wounded in action, or killed in action, or whatever. Particularly with the 100th anniversary of the outbreak of WW1 less than a year away, I will have several such events to mark, and I'd like for people to get notice of those as and when they come up.