* Source: Event Type Responsible

[dbnut]

This tag probably doesn't get used very much, but it seems to have its uses if one source/citation is also linked/edited for another fact (or even another individual, etc.).

With a census I noticed the ALL drop-down had many rows, a lot more than the relatively few in what I take to be the corresponding ENUM for individual events showing 23. My understanding in this area is very sketchy and I'd appreciate some advice.

Obvious questions are:

• Are GEDCOM ENUMs a mandatory constraint?

• If so, has FH broken that?

• If so, could we be allowed to override combo values with user-defined events names?

I do understand that the question can apply to other fact types, for both Individual & Family, but that's not my concern right now.

[tatewise]

Could you be a bit more precise, giving actual commands you are using, because I don't understand the details of whatever you are talking about.
I know about Event Type Responsible (which IMO is only available because FH supports 100% GEDCOM features).
But it is not well supported and I suspect nobody uses it.

However, I don't understand what you mean by ALL drop-down and corresponding ENUM.

[dbnut]

Could you be a bit more precise, giving actual commands you are using, because I don't understand the details of whatever you are talking about.

Sorry to make you cross. I hope the following clarifies my shambolic first attempt.

I know about Event Type Responsible (which IMO is only available because FH supports 100% GEDCOM features).

But it is not well supported and I suspect nobody uses it.

I take your word for it about FH level of support, but the intentions were good. With shared events it was meant to give precedence to the principle event owner for reporting purposes (and who knows which other potential scenarios).

However, I don't understand what you mean by ALL drop-down and corresponding ENUM.

The "Properties window All tab's tree". Dumb shorthand, I suppose, in a rush it just seemed an obvious reference.

To give an example, an available attribute for FAMC is STAT (Status) which FH offers in a drop-down with just 3 values. Those options are defined in GEDCOM as an "ENUM", a limited set of legal values (which the combo entry method respects and enforces).

That particular property is most valuable for tagging with level of proof.

[tatewise]

Reading between the lines, I think you are discussing the details presented in the All tab of an Individual Property Box.
However, the concepts are the same for every type of record Property Box All tab.

The details shown by expanding the [+] button indicate what is currently held in the GEDCOM for that item.
If you right-click any item, the menu indicates what further items can be legally added.
I guess this is what you refer to as the ENUM list. The options are mostly the same for every type of Event and Attribute.
However, some items such as Name, Sex, Parents family, Spouse family, Custom Id, etc, are not Events/Attributes so have different options.
Some All tab options only exist to satisfy the FH claim to be 100% GEDCOM compliant, but otherwise are poorly supported, not just in FH but typically in other products too.

You seem to be comparing the details shown against a Census Event versus other Individual Events.
I imagine you were looking at Birth, Occupation, Death, etc.
If that particular Census Event has 23 rows of details and other Events have fewer, then that simply shows that the Census Event happens to have more information recorded than the other Events.
All such Events have the option to record all the same details if you wish.

If you post a screenshot of the expanded Census Event versus another Event with fewer details I can give a clearer explanation.

The example you give of the Marriage Status ENUM is something rather different where a single field is only allowed a limited set of values.