Create global private fact?
|
Terry Fitzgerald
In Family Tree Maker, I could mark an event/fact as Private at a global level. I can see in FH where to see the item as private at an individual person level. I've tried searching various places for if there is a way to set globally in FH and I may be missing it if it does exist. Can anyone advise?
Thanks! Terry |
|
|
|
Terry, In what context do you wish to make it a global Private fact? I can only think of Reports, because in Diagrams you would simply omit the fact from the Text Scheme. In most Reports, the Options allow any fact to be easily excluded which has the same effect. For Narrative Reports you can set the Tools > Fact Types… definition of the Sentence Template to {blank} which has a similar effect.
|
|
|
|
Terry - do you want to set the Private flag to everyone in your project all in one go? There are several methods, such as add everyone to a Named List then assign the Private flag to everyone in that named list.
|
|
|
|
Trevor, he does not ant the Private Flag on Individuals at all, just on one Fact Type.
From: family-historian@groups.io <family-historian@groups.io> On Behalf Of Trevor Rix
Sent: Friday, March 24, 2023 11:19 AM To: family-historian@groups.io Subject: Re: [family-historian] Create global private fact?
Terry - do you want to set the Private flag to everyone in your project all in one go? There are several methods, such as add everyone to a Named List then assign the Private flag to everyone in that named list. |
|
|
|
Terry Fitzgerald
I use several custom events to manage DNA tracking and other specialized stuff. Today because I use FTM and sync to Ancestry, I mark those events are private globally so that they do not sync to Ancestry. If I begin to fully utilize FH, at some point, I will want to do an updated tree on Ancestry via gedcom and I don't want that stuff up there. I also extract and maintain a TNG website. Bottom line is that I would like to figure out a way, if possible, to have an FH fact set globally. If there is not one, I can potentially handle it manually (just a pain). In one instance, I have already converted a custom "project" event to appropriate record flags. So that custom event is no longer a concern. Does that help or make sense? Terry
On Friday, March 24, 2023 at 03:30:48 AM PDT, Mike Tate <post@...> wrote:
Terry, In what context do you wish to make it a global Private fact? I can only think of Reports, because in Diagrams you would simply omit the fact from the Text Scheme. In most Reports, the Options allow any fact to be easily excluded which has the same effect. For Narrative Reports you can set the Tools > Fact Types… definition of the Sentence Template to {blank} which has a similar effect.
|
|
|
|
The simplest solution would be to use the File > Project Window > More Tasks > Copy Project command. Then in the copy use the File > Split Tree Helper… command to delete all unwanted Facts in one go and remove any unwanted records too. Follow that with the Export Gedcom File plugin with its settings for FTM or ANCestry and for TNG.
If you use that route for direct GEDCOM upload to ANCestry then the ‘hints’ will get reset to scratch on each upload. To retain the Ancestry ‘hint’ status you must either go via FTM or use the RootsMagic route which only supports a subset of your facts sufficient to maintain ‘hints’. So it depends on what your objectives are as to the best option.
Another strategy is to write a Plugin to add the Private flag to a specified set of Facts. However, you still need to go through the File > Import/Export > Export > GEDCOM File… command to Exclude ‘private’ Facts before applying the Export Gedcom File plugin to the resultant GEDCOM file.
|
|
|
|
Terry Fitzgerald
thanks for all the options. I think I will go the old fashioned manual route! Terry
On Friday, March 24, 2023 at 08:22:07 AM PDT, Mike Tate <post@...> wrote:
The simplest solution would be to use the File > Project Window > More Tasks > Copy Project command. Then in the copy use the File > Split Tree Helper… command to delete all unwanted Facts in one go and remove any unwanted records too. Follow that with the Export Gedcom File plugin with its settings for FTM or ANCestry and for TNG.
If you use that route for direct GEDCOM upload to ANCestry then the ‘hints’ will get reset to scratch on each upload. To retain the Ancestry ‘hint’ status you must either go via FTM or use the RootsMagic route which only supports a subset of your facts sufficient to maintain ‘hints’. So it depends on what your objectives are as to the best option.
Another strategy is to write a Plugin to add the Private flag to a specified set of Facts. However, you still need to go through the File > Import/Export > Export > GEDCOM File… command to Exclude ‘private’ Facts before applying the Export Gedcom File plugin to the resultant GEDCOM file.
|
|
|