* Create Named List from External File

[Bill Deverell]

I have recently converted from Generations to FH5.

I originally had a lot of records with FLAGS such as Privacy but these do not transfer.
But I have been able to create a report from Generations
listing the Names and IDs for a named flag in TAB separated fields.
Is there a way of creating a named list from such a file?

Then I could set the FLAGS in FH5 from the named list.

Bill

[tatewise]

I don't think that is possible, but here are some other ideas.

(1) Can you export a GEDCOM containing just the Individuals with a particular FLAG?
This could be imported into FH V5 and everyone given the Flag.
Then this GEDCOM and your master GEDCOM could be merged using File > Merge/Compare File.

(2) Some FLAGS could be replaced by Expressions.
If the condition signalled by the FLAG is derived from GEDCOM data, then in FH V5 it is often more effective to use an Expression rather than remember to add the FLAG for every new case.
See how_to:using_flags_and_icons|> Using Flags and Icons and Expressions.

(3) If reasonably computer literate you could write a Plugin.
This would read the tab separated list of Individuals and set a Flag for each one in your GEDCOM.

(4) [EDIT] Alternative methods of maintaining Privacy.
If the purpose of your Privacy Flag is to hide details of living Individuals when published publicly, then there are other methods:
(a) fhugdownloads:contents:res_privata_-_gedcom_privatisation|> Utility ~ Res Privata - Gedcom Privatisation
(b) how_to:delete_data_for_living_people|> Delete Data For Living People
(c) Plugin Clean Living People

[Bill Deverell]

Mike

Thanks for the suggestions.
Some of the flags were set based on Date of birth or baptism for Individual or spouse.
Others were set manually for various reasons.

I've looked at your suggestions but the only one that appeals is a Plug-in but I'm a newbie to FH.
There are about 6400 individuals with PRIVATE flag so I need an automated approach.
It is not urgent as I don't intend to publish my tree in the near future although my current web tree dates from 2009.

The main flag I use is PRIVATE but another useful one is MERGE which I created to flag people that also occur in my wife's tree which makes joining the trees easier to manage.
I can handle the MERGE flag manually as there are only 22 of them.

How to I raise add a plugin to the wish list?

Bill


Bill

[tatewise]

It sounds as if you have ruled out option (1) as an automated approach.
Is this because you cannot create subset Gedcom from Generations?

Those based on Date of birth or baptism for Individual or spouse should succumb to option (2).

Many users find option (4) works for publishing privatised trees, without needing a manually assigned Flag.
What are your reasons for rejecting this option?

Many users prefer to manage just one merged tree, and use FH features to publish sub-trees when required.
This avoids the duplicated effort in updating duplicated entries abhorred by database practitioners.
This approach would probably eliminate the MERGE flag.

Option (3) allows you to write your own user Plugin.
Check out the plugins:index|> Family Historian V5 Plugins for advice.
Alternatively, another FHUG member may volunteer to write a Plugin for you.
But you need to provide clear details of the format of the tab separated file, and how its contents relate to your Project.
e.g.
Are its Names and IDs identical to the FH Gedcom Names and IDs?
Which Flag do you want added - the built in FH Private Flag or some other?

[Bill Deverell]

Mike

I am going to try option 1 but it's all new to me.

Bill

[Bill Deverell]

Mike

Option 1 has done the job.
I was wary because the Generations equivalent would have created problems
because it generates duplicate spouses for merged individuals.

Thanks for your advice.

Bill