* Record ID

[ronk]

Can the internal record ID prefix in Family Historian be other than 'I', or be exported as such? I ask because presently, since I export all data to a web application, The Next Generation (TNG), I have to edit the gedcom to change all "@I" to "@P" since "P" is the my preferred prefix on TNG. TNG displays the prefix, and "I" before a numeric "1" is not as readily distinguishable as "P".

If so could I do this outside of FH, with Notepad++? Then I wouldn't need to to remember to do this after every export.

[tatewise]

In FH the Record prefix letters are fixed.
If it is really important perhaps my Export Gedcom File plugin could change the prefix from I to P.
I'm surprised you have not mentioned it before.

How do you get around that fact that Place record ids start with P in both TNG and FH?
They would need their prefix letter changing too.

[ronk]

Mike,

TNG lets one assign a prefix, but only on data entry, not on import. It was just a long shot question. Not so important as to make a change to Export Gedcom plugin just for me. I changed to 'P' prefix a couple years ago, never thought to ask you about it. LegacyFamilyTree, my prior PC genealogy base, had fixed "I" as well.

[tatewise]

Capital I for Individual, and other letters for other record types, are suggested by example in the GEDCOM spec.
I know some products use P for People.
On closer inspection, the TNG GEDCOM does not use P for Place records, although I have seen TNG help pages that mention P for Place record id.
So, perhaps not this week but remind me later and it might be possible to convert in the Export Gedcom File plugin not just for TNG but generally. There is already a feature where for some products the O for Object record id is replaced by M for Media.

[paultt]

Mike and RonK
Before you go changing anything, I have been importing gedcoms from FH for over 15 years with 'replace all' You can set TNG to I or anything else. see

TNG settings.JPG (27.22 KiB) Viewed 4776 times

[tatewise]

Thank you, Paul. I had expected some regular exporters' to TNG would chime in.

I am in the process of updating the Help & Advice pages for the Export Gedcom File plugin.
Can you provide a little more context for that option so I can include it in the TNG Import advice.
The 'old' advice is at plugins:help:export_gedcom_file:tng_the_next_generation#import_details|> Import Details so how would the Replace All ~ Prefixes and Suffixes slot into that advice?

While discussing the plugin Help & advice, the page for each product, such the one mentioned above for TNG, has sections Introduction, (XYZ+) Full Data Export Details, (XYZ-) Brief Data Export Details, and Import Details.
Is that the best order for users, or would it be better to put Import Details immediately after the Introduction, with the technical Export Details later?

[ronk]

Mike and RonK
Before you go changing anything, I have been importing gedcoms from FH for over 15 years with 'replace all' You can set TNG to I or anything else. see

Mike, hold off changing those help areas until we get clarification and agreement on what happens in the TNG import process with the prefix setting.

Paul, but do you in fact use a prefix other than 'I' ? I also have been using TNG for about as long, and that setting you mention, in all my tests importing (just 5 minutes ago as well) , that setting does not alter incoming gedcom data to that prefix setting. I have TNG's Admin:Setup:Prefixes: set to 'P', but, setting import not only with 'replace all' , and also'cleared' the tree before import, all individuals remained as in the incoming gedcom record, 'I'.

This has been discussed in various TNG forum threads as in issue on gedcom import, unless there's something else you are doing that I am unaware of. That Admin setting, in my experience, only applies to individuals entered directly into TNG screens 'online'.

tngprefix.jpg (11.5 KiB) Viewed 4717 times

[paultt]

RonK,
Just had a look at the gedimport_people script called by the import functions and it has :

function getIndividualRecord( $personID, $prevlevel ) {
global $link, $people_table, $children_table, $events_table, $families_table, $tree, $admtext, $citations_table, $assoc_table, $pciteevents;
global $savestate, $lineinfo, $custeventlist, $notelinks_table, $stdnotes, $notecount, $lineending, $branchlinks_table;
global $today, $lnprefixes, $lnpfxnum, $specpfx, $currentuser, $newprefixes, $orgprefixes, $tngimpcfg, $pciteevents, $prefix, $burialtype;

$personID = adjustID( $personID, $savestate['ioffset'] );

$prefix = "I";
$info = initIndividual();
$prifamily = "";
$changedate = "";

where it is forcing the prefix to the 'I'.
As I don't ever add new persons directly into TNG, I have not had to change the prefix from anything but the default in the config files.

I was just worried that Mike would make a change in the Export Gedcom File Plugin which could potentially cause me and others relatively large editing!

[ronk]

Hi Paul,

But without a TNG script modification (which appears to hardcode 'I' and not use the Admin setting variable), and with a setting of 'P', TNG will still leaves unaltered, the incoming gedcom 'individual records' as 'I', or whatever they might be. I have posted a code suggestion on the TNG forum that the prefix setting also be apply to imported records.

But, it gives me an idea to possibly create a 'mod' to that php script to have it respect the TNG setting. I will run a test, altering that one line of code.

So, to confirm, you have not tried, within TNG, tried setting to a prefix other that 'I', right?

Edit:Update

I ran a test in TNG, altering that code in gedimport_people.php to have that variable prefix set to 'P', and it still failed to assign the prefix of 'P'. Need more testing.

[tatewise]

Two things.

1. If I modified the Export Gedcom File file to use P instead of I it would be a user-configurable option.
   I am disappointed you would think otherwise.
2. Regarding the online Help & Advice, I was asking for your opinion on the order of the sections, not their content.
   They help will get migrated and updated into the Plugin Store regardless.
   Any necessary changes to the advice can be corrected at any time.

[ronk]

With confirmation from TNG's author, the problem was resolved on the TNG side, apparently, by TNG v13, released this fall. I missed a item in the version enhancement list which indicates a new tick box option was provided in Admin:Setup:Import Settings to have the Admin:Setup:Prefix setting assigned to imported gedcom records. I will test this to confirm, but if true, there is nothing need be done on the FH side. (and I don't have to edit gedcoms anymore ).

[ronk]

Two things.

1. If I modified the Export Gedcom File file to use P instead of I it would be a user-configurable option.
   I am disappointed you would think otherwise.

Are you addressing Paul, or myself? I don't believe I gave any reason for disappointment, did I?

[tatewise]

It was Paul who said, "I was just worried that Mike would make a change in the Export Gedcom File Plugin which could potentially cause me and others relatively large editing!"

[ronk]

I ran a test and confirmed the new prefix assignment to import option in TNG 13 works. The import process successfully altered all person records from 'I' to 'P'.

[paultt]

I have not gone to v13 of TNG yet on any of my websites yet- been too busy - so haven't picked up that change, not that it will affect me. With two other upgrades of software to contend with at the same time, throwing a third into the mix could make it difficult to determine which was the cause

[tatewise]

Could you guys give an opinion on my question 2.

The plugin Help & Advice page for each target product, such the one mentioned for TNG, has sections Introduction, (XYZ+) Full Data Export Details, (XYZ-) Brief Data Export Details, and Import Details.
Is that the best order for users, or would it be better to put Import Details immediately after the Introduction, with the technical Export Details later?

[paultt]

Mike,

Clicking the Help & Advice button in the Plugin, and then the Export Gedcom File Basic Options Tab followed by The GEDCOM Export Mode advice describes the features offered for each target product and how to use the GEDCOM and Media files. takes me to:
https://pluginstore.family-historian.co ... ode-advice

which returns a page not found..... or am I going down the wrong route?

[ronk]

Is that the best order for users, or would it be better to put Import Details immediately after the Introduction, with the technical Export Details later?

I guess in sequence of process, it should be after the Introduction. But in planning, the export details need be studied before importing. So, six of one, half dozen of the other I suppose, but I would put import details ahead of the technical Export Details, and after the Introduction.

Perhaps add a note on TNG v13's Prefix enhancement (actually, a correction in TNG13 for something that was overlooked when ability to configure prefix was added, IMO) which optionally swaps in the TNG user configured prefix to record ID numbers for incoming gedcom 'individual' records.

[ronk]

Mike,

Perhaps still an FH7 work in progress, but in the Plugin Store for the Export Gedcom File, this link returns an error:
(+) Full Data and (-) Brief Data offer two levels of data export as explained in the GEDCOM Export Mode advice.

[tatewise]

Yes, that is because I'm editing the Help pages.
Unfortunately, while a Help page is edited or a Plugin is being published, they vanish from public view.