GenoPro Support Forum

The problem here is that the Gedcom standard does not have tags for godparents and witnesses and therefore the question is how to convert such items into Gedcom format.

One solution that has been used elsewhere is to include the information in a NOTE tag. This seems to be the only sensible route. I want to avoid any non-standard tags as there are so many of them and are usually exclusive to a particular package. Please feel free to offer any alternative approach. I suggest a separate NOTE for each entry e.g.

I'll put together an interim version to implement this soon but perhaps it is time I revisited the Gedcom export.  I would like to add the same Configuration Parameters interface as the Narrative & Descendants Reports. I can also utilize the Gedcom ASSO(ciation) tag to include emotional relationships and also social relationships between individuals. Social Entities and their relationships cannot be included as there is no way to represent a Social Entity.

What I propose is to implement ASSO in the Gedcom Export for social and emotional relationships between individuals. This will include the 'godparent' relationship. I will need to add 'Subject and Object forms in the Dictionary for SocialConnection enumerations for use in the RELA tag. e.g.

The existing godmother/godfather text fields will be implemented as NOTE as previously suggested. Therefore it would probably be better to convert these to relationships. To avoid cluttering the GenoMap the line can be set to transparent, meaning all maintenance would be via the Table Layout for Social Relationships.

No promises but hopefully I can get this working over the next week.

p.s. can't see where TYPE INDI is defined in Gedcom with ASSO tag ?

Having burnt a bit of midnight oil (well almost) I now have something ready (see attached). This also fixes an ongoing issue with hyperlinks and a problem when children order is set manually.

Only tested with the ubiquitous Harry Potter but loads OK into TCGR and only complains about http located pictures. I noted that TCGR translates Unicode back to ANSI which could be a problem for some.

I probably need to review Relationship texts - suggestions welcome for all.

Also added processing of 'NarrativeStyle' custom tag in Narrative Report to allowing reporting of these relationships. This tag provides the suffix for the PhSR_xxx phrase used. Thus a custom tag value of Cousin on a relationship with no 'Connection' value will expect to find a phrase PhSR_Cousin in either Dictionary.xml or as a GenoPro 'Document' custom tag. (I'm working on some revised documentation to illustrate customization options)

I tried TCGR 2009 Beta and was very impressed, but a bewildering choice of options

I think it is a case of 'horses for courses' with Genealogy products, each has its strengths and weaknesses. Being able to move the data around via Gedcom means you can pick and choose according to the task in hand.