Re: Multiple evidence of event
Posted: 08 Mar 2019 14:53
David, regarding your earlier points about FH & GEDCOM.
In the All tab, drag the header border between Record and Record Id to widen the first column.
Then each ... ellipsis expands to a more descriptive field name.
You can move the Note on the All tab as usual by using the up/down black arrows top right.
The NOTE hangs of a SOUR tag, which links to the SOUR record.
That is similar to the NOTE tag, which links to the NOTE record, but can also have local subsidiary tags.
That is also similar to a Media OBJE tag, which links to the Media OBJE record, but can have local subsidiary tags.
I guess the tag could have been named CITE instead, but that SOUR tag is the citation and links to the Source record.
%INDI.BAPM.SOUR.NOTE[1+]>% does honour the [1+] looping index, but only if no other looping index exists.
The workaround is to have multiple Text Scheme Items with data references such as:
%INDI.BAPM[1+].SOUR.NOTE[1]>%
%INDI.BAPM[1+].SOUR.NOTE[2]>%
%INDI.BAPM[1+].SOUR.NOTE[3]>%
Note records cannot have attached Media images, because the GEDCOM specification does not allow it.
Yes, FH could make a special exception and allow them, but they would not export to any other product.
I have recently been resolving a similar problem where Legacy allows Address fields to have Media attached.
But that is invalid GEDCOM and imports into FH as UDF, and a Plugin must move them up to the Fact.
However, as I mentioned before, why all those data gymnastics just to avoid split Sources?
In the All tab, drag the header border between Record and Record Id to widen the first column.
Then each ... ellipsis expands to a more descriptive field name.
You can move the Note on the All tab as usual by using the up/down black arrows top right.
The NOTE hangs of a SOUR tag, which links to the SOUR record.
That is similar to the NOTE tag, which links to the NOTE record, but can also have local subsidiary tags.
That is also similar to a Media OBJE tag, which links to the Media OBJE record, but can have local subsidiary tags.
I guess the tag could have been named CITE instead, but that SOUR tag is the citation and links to the Source record.
%INDI.BAPM.SOUR.NOTE[1+]>% does honour the [1+] looping index, but only if no other looping index exists.
The workaround is to have multiple Text Scheme Items with data references such as:
%INDI.BAPM[1+].SOUR.NOTE[1]>%
%INDI.BAPM[1+].SOUR.NOTE[2]>%
%INDI.BAPM[1+].SOUR.NOTE[3]>%
Note records cannot have attached Media images, because the GEDCOM specification does not allow it.
Yes, FH could make a special exception and allow them, but they would not export to any other product.
I have recently been resolving a similar problem where Legacy allows Address fields to have Media attached.
But that is invalid GEDCOM and imports into FH as UDF, and a Plugin must move them up to the Fact.
However, as I mentioned before, why all those data gymnastics just to avoid split Sources?