|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.0
Last Login: 59 minutes ago
Posts: 1,595,
Visits: 32,482
|
The basic information in a census record is name, birth information, location (address) and occupation. When this is put into GenoPro and exported as a gedcom some information seems to be missing. Looking at one individual the Contact field is blank and under Occupation the Source field is missing. It is present for Birth, where all fields are correct. I realise that the gedcom can refer to more than one Source which presumably complicates things. Similarly Contact and place of birth are referred to using PLAC although here different places are needed for birth.
Is it a question of extending Gedcom.js or other files involved? I had a look at the listing and, never having got involved in Java, shuddered. However with a few pointers I think I could work this out.
Any thoughts anyone?
I have now found that the xml toolkit converts RESI tags to Contact. However it does not seem to take note of the SOUR information - except in the original import of birth data
Edited: Wednesday, December 19, 2012 by
appleshaw
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 9:23 PM
Posts: 3,464,
Visits: 26,854
|
I have attached a revised version of 'Export to Gedcom' skin with should fix the missing SOUR tags for EDUC, OCCU and RESI (from Contact) tags.
Confusingly the .gno files have both 'Sources' and 'Source' tags. For an Individual, the Birth Source is copied to the Sources tag. I naively assumed the same was true for Occupation, Contact and Education entries but this is not the case. the skin now checks both. I do not understand what you mean about missing Contact tag in gedcom. The export converts Contact Occupancy data to RESI tags as Gedcom has no Contact tag as such. GenoPro is very poor at importing certain Gedcom tags, e.g. OCCU, RESI, CENS, EDUC etc. It tries to copy them to Custom tags but doesn't cater for multiple tags of the same type. For this reason, in my opinion, data from these tags on a Gedcom import cannot and should not be relied on. Let me know how the revised skin works for you and if successful I'll update the main 'Export to Gedcom' topic.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Gedcom_2012.12.19.zip
(112 views,
32.17 KB)
|
|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.0
Last Login: 59 minutes ago
Posts: 1,595,
Visits: 32,482
|
Ron
Thanks for the update and it does do what you say.
My problem is senility; I mixed up import/export differences. The export now creates the relevant ged tags but the import does not understand some of them. The RESI tag is imported as a Custom tag, which your xmltoolkit re-assigns. However SOUR tags are added to birth data but not to the others and extra Custom tags are not created. The attached export has two sources and when imported into PAF they are recognized in the correct places. In GenoPro the SOUR tag seems to be added to birth but if removed it does not cascade to another field.
As this is a GenoPro problem, not reporting, I will add a separate post.
0 HEAD
1 SOUR GenoPro®
2 VERS 2.5.4.1/2012.12.19
2 CORP GenoPro Inc.
3 ADDR http://www.genopro.com
1 DATE 20 DEC 2012
1 SUBM @subm1@
1 GEDC
2 VERS 5.5
2 FORM LINEAGE_LINKED
1 CHAR UTF-8
0 @ind1941298864@ INDI
1 NAME John Thomas /Steer/
2 GIVN John Thomas
2 SURN Steer
1 SEX M
1 BIRT
2 DATE ABT 1860
2 PLAC Lower Norwood,Surrey
2 SOUR @source00109@
1 DEAT Y
1 OCCU Plasterer
2 SOUR @source00110@
1 RESI
2 PLAC 17 Church Path,Croydon,Surrey
2 SOUR @source00109@
0 @source00109@ SOUR
1 TITL 1911 census
0 @source00110@ SOUR
1 TITL RG14
0 @subm1@ SUBM
1 NAME GenoPro User
1 ADDR Not
2 CONT Disclosed
0 TRLR
|