GenoPro Support Forum

Thanks for the tip !

Edited: Monday, September 25, 2006 by IainTait

IainTait (9/26/2006)

---

I have just noticed an interesting side effect of my tag removal as now my tree is saved much quicker than when I had  the 300+ tags !

Previous versions of GenoPro were creating a lot of custom tags because the import module was unable to import inline objects.  For instance:

In the past, GenoPro would have created a custom tag BIRT.SOUR.PAGE and DEAT.SOUR.PAGE.  Now, the PAGE is now imported as a tag of the Source object rather than a tag of the Individual.  If you re-import some old Gedcom files, you will notice the number of custom tags has been greatly reduced.


Edited: Wednesday, September 27, 2006 by GenoProSupport

As Dan has mentioned above, he has made improvements to the Gedcom import routine, so now many of these tags are imported into standard GenoPro fields instead of being held as Custom Tags.

So so for those of you like me who have already imported Gedcom data prior to GenoPro 2.0 Beta 18d, I have discovered a method to take advantage of the improved Gedcom import without having to reimport the original Gedcom files. Simply export your existing GenoPro data to (pseudo) Gedcom format using GenoPro's File/Export mechanism, edit the output .ged file and delete '1 TAGS' and subordinate records (i.e level 2 and 3 records following the '1TAGS') and then open the resulting .ged file using GenoPro (N.B. Open not Import). You will then find that Custom Tags such as birth.source.PAGE and birth.source.QUAL have now been incorporated into a new source citation record referencing the original source and they no longer appear as Custom Tags and you have not lost valuable information from the Gedom import and you retain all additonal information, positioning etc. that you have added after the original import. You can then save the file as a standard .gno file.

A couple of examples :-

The "AFN" tag had "F945C1953C1DD843A743E12DFAEBC97B297E" what does that mean ?

The "_UID" tag had the same thing and there were several CHAN.DATE which only had the date of the last info input which has no pertinance for the tree for me.

Then there were the series _FA2.DATE and _FA2.Place up to 13, then ADDR.ADDR1 etc!

250 is far too many as there were duplicate  and hundreds of entries like this @S003663@

in lots of tags which has no meaning for me.

This is why I remove most of the tags and only keep those such as BAPT.DATE etc.from where I transfer the info into it's rightfull place in the birth tag etc.