Administrators Customers Important Contributors FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: 7 hours ago
Posts: 3,443,
Visits: 26,652
|
A few Gedcom Import problems.
GenoPro assigns all individual event sources (e.g. BIRTh, EDUCation, OCCUpation, RESIdence) directly to the individual when they should only be assigned to the event itself. In the example below showing the imported gedcom on the left and resulting XML on the left only Source s1i should be assigned to Individuals's Sources. The partial handling of Gedcom tags gives confusing and sometimes incorrect results. e.g. Only the occupation title is taken from the OCCU tag and the subtags other than SOUR are not processed. But the title is only taken from the last OCCU tag, any earlier ones are thrown away, other OCCU subtags such as DATE and PLAC are moved to custom tags under a occupation custom tag and SOUR is removed. Unfortunately subtags from different OCCU tags can get mixed under single occupation custom tag. In the example below the XML tag occupation has DATE from the 1st OCCU and PLAC/ place from the 2nd OCCU tag. I find it strange that the BIRT tag can be processed but not EDUC, OCCU or RESI when the structure is similar with common tags like DATE, SOUR and PLAC.  I suggest that if GEDCOM event tags cannot be processed in their entirety then the event tag and all subtags should be copied to custom tags. I also cannot see the point of renaming some unprocessed Gedcom tags and leaving others. e.g. OCCU renamed as occupation, PLAC as Place but EDUC, RESI and DATE are left unchanged. It would be clearer if the custom tags retained their GEDCOM tag names, unless the subtag was converted to a standard GenoPro tag e.g. SOUR to Source with a reference to the related SourceCitation, DATE to Date and recognised as a GenoDate object, PLAC to Place with a generated reference to a created Place object. Also if multiple occurrences of event tags cannot be processed (e.g. OCCU in the example, but also EDUC, RESI etc.) then a warning should be given in the log regarding the lost/omitted data. But I suggest subsequent tags could simply be given a suffix, e.g. OCCU, OCCU_1, OCCU_2 etc. The GenoPro XML for a 'half-way house' towards full support for Gedcom import could look like: <Individuals><Individual ID="I1"> <Name>Source Bug <Display>Source Bug</Display> <First>Source</First> <Last>Bug</Last> </Name> <Sources>s1i</Sources> <Position BoundaryRect="-242,231,-158,155">-200,200</Position> <Gender>M</Gender> <Birth> <Date>~2001</Date> <Source>s1b</Source> </Birth> <OCCU> <Date>~2013</Date> <Source>s1o</Source> </OCCU> <OCCU_1> <Place>place00003</Place> <Source>s2o</Source> </OCCU_1> <RESI> <Place>place00002</Place> <Source>s1r</Source> </RESI> <EDUC> <Place>place00001</Place> <Source>s1e</Source> </EDUC></Individual></Individuals><Places><Place ID="place00001"> <Name>1st School</Name></Place><Place ID="place00002"> <Name>residence</Name></Place><Place ID="place00003"> <Name>2nd occupation place</Name></Place></Places><SourcesAndCitations><SourceCitation ID="s1i"> <Title>individual source</Title></SourceCitation><SourceCitation ID="s1b"> <Title>birth source</Title></SourceCitation><SourceCitation ID="s1o"> <Title>1st occupation source</Title></SourceCitation><SourceCitation ID="s2o"> <Title>2nd occupation source</Title></SourceCitation><SourceCitation ID="s1r"> <Title>residence source</Title></SourceCitation><SourceCitation ID="s1e"> <Title>education source</Title> |
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|