GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 

GenoPro Support Forum




Error in Export to Gedcom file

Click to view RSS...
Author Occupation details exported incorrectly
Posted Sunday, March 30, 2014 - Post #33371
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Wednesday, December 7, 2016
Posts: 27, Visits: 303
Data stored under Company/Employer/Organization gets exported as part of the ADDR tag even though there is no address information included.

The ADDR tag should contain data stored in the Work Place field.
Posted Saturday, April 5, 2014 - Post #33403
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: 9 hours ago
Posts: 3,337, Visits: 25,588
Thank you for bringing this to my attention.

Having revisited the Gedcom 5.5 standard it is abundantly clear that the AGNC tag is the correct place for the company/employer/organisation content.  

AGNC tag content (responsible agent) definition: 

RESPONSIBLE_AGENCY: = {Size=1:120} 
The organization, institution, corporation, person, or other entity that has authority or control interests in the associated context. For example, an employer of a person of an associated occupation, or a church that administered rites or events, or an organization responsible for creating and/or archiving records.

I will fix this shortly and post a revised skin.

Update: version 2014.04.05 has the fix.


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


Edited: Saturday, April 5, 2014 by genome
Posted Tuesday, April 8, 2014 - Post #33413
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Wednesday, December 7, 2016
Posts: 27, Visits: 303
Thank you for Version 2014.04.05 which has fixed the reported problem.
However, this level no longer produces output of the form

1 EVEN
2 TYPE Lost Cousins
2 DATE yyyy

for the Lost Cousins census tag which was introduced in Version 2013.05.05

Please can that code be reinstated?
Posted Thursday, April 10, 2014 - Post #33421
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: 9 hours ago
Posts: 3,337, Visits: 25,588
I have compared the two versions and cannot find any code present in 2013.05.05 that is missing from 2014.04.05

There is a facility introduced in 2013.07.30 that allows additional Gedcom event and attribute tags to be output from specially formatted Occupation entries.

So for example if you create an Occupation entry for an individual with a job title of  |EVEN|Lost Cousins and start and end dates of say 1961 then the output from the Export to Gedcom skin will indeed have

1 EVEN
2 TYPE Lost Cousins
2 DATE 1961

as you require.


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


Edited: Saturday, April 12, 2014 by genome
Posted Saturday, April 12, 2014 - Post #33431
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Wednesday, December 7, 2016
Posts: 27, Visits: 303
Many apologies Genome. I have now been told that my copy of Version 2013.05.05 had been modified before I received it.

I doubt that you would wish to include these extra lines of instructions in the Gedcom.js file of the GenoPro product but would you consider the inserton of a 'dummy' Include file which could then be modified by users to avoid a repetition of what has just happened?
Posted Thursday, April 17, 2014 - Post #33479
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Wednesday, December 7, 2016
Posts: 27, Visits: 303
Another error has been noticed in the same process . . .

Not all CENS and RESI records are being included in the gedcom file.
Primary residence facts are stored within the Contact tab but do not always get exported.
Similarly, some Source tab facts are marked as Census records but do not always get exported.

What are the selection criteria if not all instances are to be output?
Posted Friday, April 18, 2014 - Post #33480
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: 9 hours ago
Posts: 3,337, Visits: 25,588
My 'Export to Gedcom' Report skin attempts to map as much of the GenoPro data as possible on to equivalent Gedom tags.  

Occupancy data within a Contact entry is only treated as a Census entry when the Configuration Parameters setting for Census records is set on and  the single Source field of a Contact points to a Source/Citation entry with 'MediaType' set to 'Census'.  Note that entries under the Contact's Sources tab are not checked.

If these criteria are not met then the occupancy data is exported under a RESI tag.

If you think I have overlooked something then please provide a sample .gno file and the required/expected Gedcom output.


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Posted Friday, April 18, 2014 - Post #33482
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Wednesday, December 7, 2016
Posts: 27, Visits: 303
Thanks for the explanation Genome. Part of the problem was that I was expecting both RESI and CENS records to be created for the same instance. Sometimes Residence is shown for a long period with widely spaced Start and End dates. A Census is normally conducted on a single date within such a period of residence.

I will come back with further details if I find that your explanation does not match what is produced.

Please will you confirm (or deny) that the matching of Source identifier between Contact and Source records only goes as far as the first blank character? Sometimes I select the Source within the Contact tab from the drop down list but information following a blank seems to be ignored, or treated as a comment.
Posted Saturday, April 19, 2014 - Post #33485
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: 9 hours ago
Posts: 3,337, Visits: 25,588
I see the problem here.  If there are two sources for residence/occupancy info then you should not have to record the place twice in Contacts and there is a case to RESI and CENS tags to be generated.

A potential problem is that the Source/Citation record in GenoPro does not have an event date, only date of publication which for a Census is not the same thing.

A work-around is to use the Source/Citation 'Edition' field to record the date for the Census, either just the year or alternatively the actual date on which the Census was conducted, in Gedcom format e.g. 3 APR 1881 for UK 1881 Census.

There is I believe an existing problem with the current Export  If the Contact has more than one Source (i.e. via Sources tab) then then Census record includes these sources but generally the additional sources refer to the residency or contact details (e.g. RESI Gedcom tag. 

Therefore I propose to change the script to work as follows:

If a Config Param Census option set AND Contact entry has an occupancy place AND any Source/Citation with MediaType 'Census' AND either Source edition set or occupancy start and end dates identical then:
  1.  generate a CENS gedcom entry with subtag DATE set to Source 'Edition' if present otherwise occupancy Start/End date and a reference to the Source.
  2. If occupancy start and end dates are not identical OR there is more than one Source/Citation reference then also generate a RESI gedcom entry without a reference to the Census Source.
Otherwise if an occupancy place present generate a RESI Gedcom entry as normal



footnote: I can neither confirm or deny your postulation regarding Source identifier matching.  My input and knowledge of GenoPro code is limited to Report Generator skins only.  Only Dan knows the internal workings of GenoPro.exe.


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


Edited: Saturday, April 19, 2014 by genome
Posted Saturday, April 19, 2014 - Post #33486
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Wednesday, December 7, 2016
Posts: 27, Visits: 303
I think that I understand what you are proposing to do but am confused by Source/Citation 'Edition' field. Is that the one marked "Citation Reference (where in source)"? I currently use that field to record "Piece xxx, Folio yyy, Page zzz" information relating to the census.

Although Publication Date is not strictly correct for a census, that is the only date field present and I have used that to record the date of the census when Source Media Type is set to Census.

In order to avoid blanks in the "Source Title / Source Name" field for census sources I have this recorded in the form "RG10/587/11/21" to allow matching with the corresponding Contact details.

Is that compatible with what you are proposing?


Similar Topics

Click to view RSS...
Expand / Collapse

Reading This Topic

Expand / Collapse