Preciso reportar dificuldades no uso so aplicativo, versão premium, quanto às qualificações, especialmente dos cônjuges e "Bugs" na sua publicação.
Não existe uma qualificação que exprima o "Companheiro" como cônjuge; Não existe qualificação adequada para cônjuges (Pai e Mãe) que decidiram ter filhos, mas não casaram, ou seja não tem relação a não ser que são pai e mãe de um filho "Somente";
1 pessoa casou, teve filhos, separaram-se, um dos cônjuges se uniu (companheiro) a outra mulher, tiveram filho e se separaram, mas ao publicar no site My Heritage e mãe eex-companheira foi qualificada de "namorada" o que absolutamente não é, causando desconforto na familia, o que me parece um bug;
A propósito não existe a qualificação "Namorados" para definir um relacionamento reconhecido pela familia e isso é comum no Brasil, onde namorados até convivem, mas não se consideram companheiros ou noivos;
A qualificação de sobrinhos quando decorrentes de segunda relação de um dos pais, sai publicado como "parente" causando desagrado a todos, pois os filhos de irmãos do primeiro relacionamento de um dos pais está correto, ou seja "Sobrinho";
Os filhos de segundo relacionamento de um dos pais é qualificado de "meio-irmão", mas isso além de não ser correto, não é bem visto pelos familiares e a legislação brasileira não permite essa diferenciação, então proponho de o sistema pelo menos permita alterar, sugerindo ao administrador confirmar como quer qualificar a pessoa;
Nas informações pessoais, quando informado o apelido, este quando é puublicado, é inserido automaticamente depois do primeiro nome o que não é adequado. Assi proponho que o administrador seja consultado se deseja incluir ali mesmo ou logo ao final com a informação de que se trata de "Apelido. Obrigado e aguardo retorno das minhas observações e solicitações, ao tempo em que me coloco à disposição para esclarecimentos adicionais.
Indeed you are right - males can change their last names as-well, and I understand why it could be important for you to perhaps change the phrasing. However it could also be quite confusing for people who are used to "Maiden" and "Married" names instead of the suggested.
We work by the status quo of genealogists, and so making such a change will be hard to implement social-wise.
However, I suggeted this to the appropriate department and hopefully your suggestion will get through.
Whenever I generate a family book, my sources with notes generate as pages of code rather than the details I typed. Also, when I add long notes to people (usually the content of obituaries) it ends up formatted strangely in the book no matter how many times I try and fix it.
I would also like to see options to customize the family book like you can with charts. I was disappointed to see that the images I attached to the sources weren't included when I generated the book. I intend to edit the PDF to add them once I'm done with the tree, but that will include changing all the page numbers, ect. Just an option to generate it without page numbers would save me hours!
The Family Book is a third party software that we license a version of. It is well loved by many.
In regard to your issue with notes showing up as pages of code, a new version of the Family Book software will be released very shortly that should take care of this problem. In order to prevent this in the future, try pasting your notes into notepad first to remove any hidden code and then paste into the tree.
About customizing the Family Book, the level of customization you are looking for is simply not available in the version of the Family Book we offer. Honestly I am not sure it is available in the full version either, but you are welcome to learn more about the full version of the Family Book (Complete Genealogy Reporter) here.
"In most European (and Europe-derived) cultures, the given name usually comes before the family name (though generally not in lists and catalogs), and so is known as a forename or first name; but the family name traditionally comes first in Hungary, parts of Africa and most of East Asia (e.g., China, Japan, Korea and Vietnam). In China and Korea, even part of the given name may be shared among all members of a given generation in a family and the family's extensions, to differentiate those generations from other generations."
Currently the names are displayed in English order, but this is VERY disturbing.
Please fix this bug, so when the Language is Hungarian, the name ordering should change to "Family name Given name".
I agree and fully support this request, it's strange that the developers published a hungarian version of this site and - I bet - they didn't even know about this problem. Fix it soon, or you probably lose some 10-15 million hungarians in this site.
Thank you for writing us regarding the product suggestion. I would like to inform you though that we already have these options in the Family Tree Builder by going to Edit > Search (or shortcut Ctrl F on the keyboard).
You have there comprehensive searching abilities which let you have much better control of what you are exactly looking for.
Please let me know if you still need more information about it.
I too seem to have difficulty in query writing- Perhaps you could Actually demonstrate HOW I can solve this issue
In pawing over my data recently I discovered that there were females that did not have a married name assigned. Just over 800 to be more accurate.
To prepare a list of those individuals requires a query like:
Sex MATCHES: FEMALE
Marriage date: EXISTS
Married name: DOES NOT EXIST
Quite a simple query really- but WHERE can I use it?
Similarly I discovered that when I imported my GEDCOM file into Myheritage FTB from its original form in Personal Ancestral File (PAF) I had often used a date determined filed that represents the condition that exists for a large part of my research In South Australia and uses the published Death Index which conclude in 1972.
Thus I had some death dates as After 1972.
So to find those entries and seek to either update or amend them- requires a Query thus:
Death date: contains AFTER.
Quite a simple query really- but WHERE can I use it?
So to get around this problem- I had to export a New GEDCOM out of Myheritage FTB - create and import that GEDCOM in PAF and write the queries-.
THEN in parallel- with both Myheritage FTB AND PAF open- edit my through the list.
Am I missing something here- or is Myheritage just not quite up to query involvement?
Your theory of CTRL F and inputting your requirments does not seem to cope with what I need.
I understand that you have some difficulty with our system, and so I've included some screenshots to make it a little bit clearer for you. The red circles are the first steps you should do (and the first screen you will be presented as if you go to Edit > Search).
If you change the Fact type on an existing Fact from say Settlement to a custom Fact, say Electoral Roll, any attached photos/documents attached to the fact become detached after selecting OK. The photos/documents then have to be reattached to the fact, which is a pain if you have a lot to change as I did.
When saving a tree with a differnet name, the SmartMatches are NOT saved!!!! It would save MONTHS of work if that would be done. If I want to publish my NEW tree (saved with another name) and the SmartMatches were also saved I didn´t have to confirm ALL former matches again. In my tree it is about 100 000 matshes thas are lost.
You are right in that if you use the "save as" function in FTB, you create a new project with a new ID. When this project is later published to the MyHeritage site, it will be treated as a new tree and new Smart Matches will be calculated for it.
A possible workaround for your problem is to use the "rename" function instead. Go to File > Close project, and then to File > Manage Trees. In this menu you will be able to rename your tree without changing its ID.