Correcting issues with templates imported from RM9
Gary <gary.gauthier@...>
For some reason, FH7 does not understand some RM9 template functions such as ":Year" when importing.
An example is the following RM9 template code: <[Year]|[Date:Year]> (I realize this is confusing, but that is how it was coded) The first instance of "Year" is a text field containing just the year. The second instance of "Year" is actually a function that extracts the year portion of the preceding field called "Date". Could someone tell me how one would extract just the Year from the citation field containing the full date? I believe the FM7 "=Year()" function is used, but I having issues with getting it to work. Regards; Gary |
|
John Hanson
Gary I am not an RM user but if that feature is new to RM9 then it may take FH a while to get it added to the import functionality
Regards John Hanson FSG
From: family-historian@groups.io <family-historian@groups.io> On Behalf Of Gary
Sent: Wednesday, March 22, 2023 11:09 PM To: family-historian@groups.io Subject: [family-historian] Correcting issues with templates imported from RM9
For some reason, FH7 does not understand some RM9 template functions such as ":Year" when importing. |
|
Gary, The first thing to do is use the Create Source Template Definitions plugin to create global definitions that you edit to update the templates. Then you use the Tools > Source Template Definitions… command to modify templates. Checkout the Help button for advice.
In your example, <[Year]|[Date:Year]>, I don’t think it is the Year qualifier that is the problem but the or | separator that FH does not support.
The two options for extracting the Year from a Date metafield are: {Date:YEAR} qualifier which only works for ‘simple’ dates. {=Year(%SOUR.~DT-DATE%)} function which works for ‘simple’, ‘period’ & ‘range’ dates. The %SOUR.~DT-DATE% metafield data reference shortcut is described in the FH Help for Understanding Data References.
Assuming the Year metafield and Date metafield never both have values together the following will work: {Year}{Date:YEAR}
If both can have values then a more complex expression could be used. Will you need that?
|
|
Gary <gary.gauthier@...>
John
The RootsMagic template language really hasn't changed in about 3+ versions, so I think this is just something that requires tweaking in FH7. Gary |
|
Gary <gary.gauthier@...>
Mike;
Based on what I'm seeing elsewhere, FH7 actually does understand the "|" (OR) symbol. The date field (eg. Feb 13, 2023) is in the citation portion and I'm trying to use it in the bibliography. I tried entering just the simple constructs you suggested and none would print anything. I'm not yet familiar with the FH7 documentation, but I suspect the issue could be more subtle. In RM9 templates, one has a display title and a data variable. I tend to use the display title in all-caps and blanks changed to underscores for my variables. FH7 almost looks as if it took the display title and added underscores, because I don't see both types in the definition. I'll have to look at this a bit more. Wish I could find a concise template language document. Bouncing around via hyperlinks makes it hard to understand the grammar. |
|
Gary <gary.gauthier@...>
Mike I still need to work on the symbols used to prevent printing of local data; that is the "!" symbol. However; I don't think that is affecting this issue.
Footnote France, database with images, Archives départementales de l'Eure, Etat civil (https://archives.eure.fr/search?preset=80 : accessed February 13, 2023) > search: Heudicort (Eure, France), 1900, Naissances, Registres > cote 8 Mi 5625 > image 376, Heudicort, acte no. 12 (26 July 1900), Patte (Marie Vitaline), born 25 July 1900; ! Local ref: Genealogy__Patte_(Marie_Vitaline)__IE__BIRT_1900-07-25__001.
FOOTNOTE FORMAT: {Collection_Creator}, {Collection_Title}, <{Collection_Type}|database with images>, {Website_Creator}, <<i>{Website_Title}</i>> <(<{Item_Address}|{Website_Address}> : <{Access_Type}|accessed> {Access_Date})> {Path}, {Item_Of_Interest}; {Credit_Line}.<! Local ref: {Local_Ref}>.
Short Footnote France, Archives départementales de l'Eure, Etat civil, Heudicort, acte no. 12 (26 July 1900), Patte (Marie Vitaline), born 25 July 1900.
SHORT FOOTNOTE FORMAT: {Collection_Creator}, {Collection_Title}, {Website_Creator}, <<i>{Website_Title}</i>>, {Item_Of_Interest}.
Bibliography France. Database with images. Archives départementales de l'Eure. Etat civil. https://archives.eure.fr/search?preset=80: >.
BIBLIOGRAPHY FORMAT: <{Bibliographic_Topic_item}|{Bibliographic_Topic_site}>. {Collection_Creator}. {Collection_Title}. <{Collection_Type}|Database with images>. {Website_Creator}. <<i>{Website_Title}</i>>. {Website_Address} : {Access_Date}>. |
|
Ah! Unlike RM, the FH Citation-specific metafields cannot be used in the Bibliography Format. This has been discussed at length in the FHUG Forums. (Sorry, I was wrong about the or | separator which FH does support.)
The FH Tools > Source Template Definitions… support a Record Title Format, Bibliography Format, Footnote Format, and Short Footnote Format. The Help button Source Template Definition Editor advice explains those and links to Source Template Formats that explain the template grammar.
Think how long it took you to grasp all the RM features, and spend some time getting to grips with FH features as there is too much to learn in just a few days.
|
|
Gary <gary.gauthier@...>
Mike;
No need to apologize. I gather that FH7 has made some significant advances in accommodating RM imports. One can't remember everything with a program this complex. You're correct about it taking some time to understand. Being an "old-school" software engineer, I'm more used to printed manuals. However; I'll adapt. Right now; I'm doing the "crash course" to make sure I'm not spending the rather stiff price for Crossover + FH7 on something that doesn't work for me. I am asking more questions than I otherwise would, because the time-limited trial isn't that long and there's quite a few checks to do. So far; everything seems to be OK and I'm highly likely to switch over from RM9, but there are a few minor issues:
|
|
|
|
Gary <gary.gauthier@...>
Thanks, Mike.
As noted the issues are minor. They are not sufficiently severe to preclude my buying the package and in some cases have procedural workarounds. With reference to your numbered notes:
Gary |
|