* add the same fact to multiple Individuals

[jimlad68]

Is there a simple way to add the same fact to multiple Individuals, say from a named list or a selection from a query or the individual records window, rather than copy/paste for each via the Property box.

The reason I am asking this is because of the way FH uses Flags. In TMG a Flag can have a value, e.g. The Living Flag can be Y,N,? or a custom flag could have many optional values, all of which could be filtered for. As I understand it, a FH Flag is either On or Off.

So, if there was an easy way to add the same Fact to a selection of people, that could be used like flags, also, it would be Gedcom exportable. It is easy to delete Facts, so that side of the equation would be nearly as easy as using Flags.

Would there be any downsides to using this method instead of Flags/ Named lists, which would still be better suited for "temporary" work? I'm sure it would not be as fast as Flags and would "bulk up" the Gedcom file. It would also mean developing queries, not too difficult, rather than simple Flag/Named list selection.

I suspect I will use simple Flags or Named Lists, but I could see other situations where adding the same fact to multiple users might be useful, even if some were individually amended afterwards.

[Jane]

It's a dead easy plugin to do that, just prompt for a list of individuals and then write the fact to all of them. Longest job would be defining what you need to add in the fact. Take a look at the Ancestors and Descendant count plugin for an example, it does everyone, but could be easily changed to do a table of people from the record select prompt.

[tatewise]

Jim, you are not specific about what type of Fact you would choose to add, but you do say it needs to have a value.

So I guess you mean an Attribute, which in FH means the custom _ATTR tag, unless you propose to 'borrow' a Standard Attribute.

As discussed elsewhere, the _ATTR tag does NOT export to other programs in GEDCOM format.

_ATTR must be converted to the EVEN tag that does does NOT support values in Standard GEDCOM, although some programs do support such EVEN values.

So your suggestion that "it would be Gedcom exportable" is NOT guaranteed.
Similarly, FH Flags are NOT GEDCOM exportable either.

[jimlad68]

Jane,
looks very interesting, probably too advanced for me at present, but I could probably manage to create a default Fact for everyone, then amend/delete as required from queries or search and replace, but that would not be anywhere near as slick as Flags/ Named Lists.

Mike,
Although ATTRibute is the obvious choice, like you say, it would be non standard Gedcom, so I would probably want to go with and EVENt. If it were easier to create an ATTRibute, that could then be converted to and EVENt. But then the _ATTR tag can be exported as an EVENt with your routine.

Something for me to think about while I am probably without internet for the next week.

[tatewise]

I think you are misunderstanding some of the details.

If in FH you use a custom EVENt then it CANNOT have the values you wanted, because no values are allowed at all.

So we are back to a custom _ATTRibute, which when exported via my Plugin as Standard GEDCOM 5.5 creates an EVENt with the value in its local NOTE.
It is only for some non-standard GEDCOM program formats that the value remains with the EVENt tag.
These include Family Tree Maker 2014, Roots Magic, and The Next Generation.

So the exportability is somewhat restricted.

[jimlad68]

Mike quick reply, when I say value that is "my" value in place of a flag, I would use the text/memo of an EVENt which I am sure can be filtered for, I'm sure I just did it on a custom EVENt I imported from TMG.

Terminology can be tortuous, but I agree very necessary.

[tatewise]

OK, understood, but I think the benefit is getting marginal.

It might be just as easy to have a set of Flags where each Flag 'name' represents each 'value'.

So instead of an EVENt with various 'values' you would have a set of Flags with various 'names'.

The adding and removing of Flags is then easier than fiddling with EVENt values.

However, it depends on exactly what the intended use is.
In most cases I come across, the condition that the Flag (or EVENt value) signals can be just as easily represented by an expression, which has the advantage of automatically signalling the condition without the manual intervention of setting/clearing Flags.
See how_to:using_flags_and_icons_and_expressions|> Using Flags and Icons and Expressions.

[jimlad68]

I suspect for many instances I will just use Flags/Named lists for speed, however I already use custom events for flagable type information. E.g. I have a "Root" EVENt for the Root persons for trees, this has structured text that can be filtered for various family situations, and the text field can also include an explanation of the root.

The main Flag type scenarios I will have are the usual Living and Private, however in order to keep track of who is Living, Deceased, Probably Living, and Probably Deceased etc, and ensure everyone had a "Living Status", I would need at least 4 Flags to keep track, whereas with my EVENt text method, the EVENt text caters for all those 4 scenarious with 1 of 4 letters L,D,I,E (or whatever).

There are various options, just a matter of choosing the most efficient for the given scenario.

[tatewise]

The Living states might be a case where an Expression automatically returns the values. Then you never need to manually update the states.
e.g.
Deceased is the state if there is a Death/Burial Event with a Date,
else if there is a Birth/Baptism Event with a Date,
then Living is the state if Age today is < 50
else Probably Living is the state if Age today is < 111
else Probably Deceased is the state.
In all other cases the state is Unknown.
There are several Functions (EstimatedAgeAt, EstimatedBirthDate, EstimatedDeathDate) that would probably give improved results.

[jimlad68]

Mike, I love automation and the above you suggest sounds good, "I can just see your mind whirring", but there are also instances where there is a need to at least check things manually as well.

Just another related thought for your wonderful Search and replace. That it works from a Flag/ Named List/ Query result (inc Facts).

With that thought I will now be packing the car and be very occupied with 2 American grandchildren for the next week and then exhausted!

thanks for everybody's suggestions.

[Jane]

It's not current possible to access "Named List/ Query result (inc Facts). " from Plugins