Michael Hannah
-
Content count
2,915 -
Joined
-
Last visited
Posts posted by Michael Hannah
-
-
Some users define "Family Group" Flags as alternative to a "Connected" Flag. Flag "FamA" is set to 'Y' for everyone in that family group, and 'N' for everyone else. Then there is a "FamB" flag for that group, etc. etc. Using separate family group flags allows a person to be in multiple groups. Or you could simply have one Flag with multiple values: A,B,C,... But then a person could only be in one family group.
Hope this gives you ideas,
-
You "could" do that, Judy, and I am sure Terry will also respond, but I would want to be able to easily identify later which people are related and which are not. For example, I may want to exclude the unrelated people from some reports, or produce a report of only the unrelated people, or exclude them from my Second Site web pages, etc. If you ever want to be able to separately identify all these unrelated people it is much easier to mark them when you add them, than trying to identify them later. So the "downside" which I see is a matter of the ease of separately identifying these people later.
Hope this helps,
-
Hi, Judy,
I agree with Terry that these people should be included within your main project and dataset. In addition I strongly agree with Terry's recommendation that you mark these people as a separate group by using a distinct Flag value. For an excellent example see Terry's article about his Connected Flag:
http://tmg.reigelridge.com/connected.htm
As he suggests in that article, you "could" just create the Flag in your existing family dataset before you start adding the unconnected family, and set the values to "Y,N" so that all your existing people are marked by default as 'Y' (connected). Now edit and change the defaults of this Flag to "N,Y" so that the new people you add are marked by default as 'N' (unconnected). When you are done adding be sure to change the Flag default back to "Y,N" so that subsequent people will be marked connected by default. I would also modify the Add Person template to be sure to include this Flag in that template so you can override the default if desired when you add someone. I also second Terry's suggestion to use this Flag to set an accent color for these people.
However, since you indicate that this separate family tree is "many generations" it may be quite a large number of people? If you think that adding them may be a lengthy process, and (more importantly) are likely to only do a few at a time, while also still working with your main family tree adding people to it as they are discovered, then I would recommend adding this family as a multi-step process. I would actually add them into a separate temporary dataset in your main project. However, note that Flags are unique to a dataset, so what you do with a Flag in one dataset does not affect any other dataset within that same project. I would create a same-named Connected Flag in both datasets, but define the Flag defaults appropriately opposite in each dataset. Then when you have finally completed adding the new family tree with all its generations, simply merge the temporary dataset into the main dataset, and delete the temporary dataset.
For merging I recommend you review Terry's Tips both about datasets and the merging of datasets:
http://tmg.reigelridge.com/merging.htm#datasets
So long as you have a Flag of the same name (e.g. Connected) in both datasets with the same possible values, even though their defaults may be different, the values already set for the merged-in people will be retained. While you are still in the midst of adding this family bit by bit you don't have to think about the proper Flag values as you go back and forth working in both datasets. Each dataset will set an added person to the appropriate default value. Once merged the unconnected family will be in your main dataset but each person flagged as unconnected without further action.
This trick allows you to "slowly" add this new family while continuing to work with your main family, but always with the understanding and goal of ultimately merging the unconnected family into your main dataset.
Hope this gives you ideas,
-
A problem with Soundex sorting is a known remaining bug in the program. Soundex sorting does not group as is clearly implied by the title of the sort. For example, the option of the three level sort of:
Given name soundex code, surname, birth date
actually sorts as if it were a four level sort of:
Given name soundex code, given name, surname, birth date
For more details see this entry in my on-line list of outstanding bugs:
Soundex sorting does not group as implied by the title of the sort
Sorry, but there is no way to avoid this inappropriate extra level of sort in either the Picklists or Project Explorer. As noted in the workaround in the entry above, a filtered List of Names report can be generated and sorted on appropriate columns, one of which would be a Soundex code, to get the desired sorted list. That report does sort correctly.
Hope this gives you ideas,
-
You might also be interested in my comments about how I use Repositories in TMG. This very much depends upon how one chooses to structure the three TMG source templates for a source. As described in the Source Templates chapter of my book, my personal preference for these templates is to range from output of the least to the most detail, from Short Footnote through Full Footnote to Bibliography. My principle is for the Short Footnote to be just barely enough to refer back to the Full Footnote (or maybe find the entry in the Bibliography which I always produce), and the Full Footnote to be just enough to clearly identify the source and find its more complete Bibliographic (Source List) annotated entry.
One can have many citations for a given source, but will have only one bibliographic entry for each source. For this reason I only include the Repository source elements in my Bibliography templates to avoid duplicating that information throughout the citations. However, if you choose not to output a Bibliography then I would suggest including them only in the Full Footnote template.
Details of my use of Repositories is in the Source Guide chapter which also includes examples of my repository abbreviations. If a book is one that others may be able to obtain, as Terry suggests I would also probably try to cite a more publicly available repository, if such exists. However as my notes show, I do choose to define a repository for my own private holdings, and for private holdings of specific individuals such as other family members. These are usually family items or records which do not exist anywhere else.
Hope this gives you ideas, -
Marlene,
Back in 2014 you were having problems generating GEDCOM files due to your McAfee's 'Real TIme Scanning' interfering with TMG. Did you remember to turn this off? As also discussed back then, do you have the 0 TRLR end-of-file tag in the GEDCOM file.
-
Hi Roz,
Yes, the Name-Marr tag type could easily be used with a 1901 date, a note in the memo, and cite the 1901 census as the source.
If the tag is left as a non-Primary name tag, then it can produce a sentence in your narratives if you include this tag type. As its default sentence includes the date variable and the memo variable, you can explain this situation in this tag memo. That should explain the situation to anyone reading your narrative reports.
However, I prefer to generally not include any Name-Marr tag types in my narratives but still define them for the sake of indexes. For that reason I have added some custom Name tag types to use when I want to describe something unusual for a person. One example is my very general purpose Name tag called Name-Comm, where I can include whatever I want about the situation in the memo, such as a date. See the description of that custom tag type in my book here, and it sentence here.
Hope this gives you ideas,
-
First, how do you know that this End Note is citing this tag for this person?
Second, is it possible you have an embedded citation ([CIT:]srcnum;cd[:CIT]) to this source within the memo of this tag?
-
I have added the Memo variable to both the standard Milit-Beg and Milit-End tag type sentences, but like Terry also created a MilService custom tag type which basically is nothing but the Memo variable. For my examples see the sentence templates for these three tag types in my book.
-
Have you done a set of Optimize / Validate File Integrity / Optimize lately?
-
If your goal is Ancestry trees, then I would second Jim's suggestion to think about RootsMagic in the future. Personally I am sticking with TMG for now and would recommend upgrading to Version 9, but several users have switched to RootsMagic since it has the ability to import TMG directly using the TMG database files. The RootsMagic document "Moving data from TMG to RootsMagic" describing importing directly from TMG states:
"The recommended TMG versions to use for import are 7.04, 8.08, or later."
so you could convert your existing 7.04 database.
Also you may not be aware that John Cardinal has written a new program GedSite which is becoming as powerful as SecondSite, his companion program for TMG. GedSite will accept as input a GEDCOM file exported from several programs, including RootsMagic, permit adding customizations for the narrative sentences, and then produce a complete set of web pages for a genealogy site. GedSite is in its early stages right now, and John is actively adding features weekly, but it is already capable of creating extremely full featured web pages from data exported from programs like RootsMagic.
Hope this gives you ideas,
-
Bob,
Since you referred to my book, you can look in the Source Templates chapter here which does have the default "Lineage Application" source type included in alphabetical order. (I don't have a link to it at the top of the chapter since I don't use it myself.) Further, my custom source types of LDS Patron Sheets and LDS Pedigree Resource are extremely general purpose and could be used as examples for creating a custom source type to use for these applications.
Hope this gives you ideas,
P.S. Oops... I now notice that I have the notation (an '*') on the Full Footnote and Bibliography templates for the Lineage Application source type which indicates I customized those templates in the past but then decided not to use them. I completely trust Terry's post above specifying the original templates to be correct.
-
Bob,
There is a report (other than the Ahnentafel - Direct Line report) which will show a direct line between two people: Relationship Chart.
You can "somewhat" limit the amount of output to get "close" to only having the names. You will still get the BMD dates, but you can delete those if you want. To get this report close to "bare-bones" use the following Report Options with the Report Destination to an unformatted Text file:
Names tab: Identifiers=none
Places tab: Use selected place fields but uncheck all fields, preposition=blank
Miscellaneous tab: Check Closest relationship only
That will produce three extra lines for the ancestor (b. d. m.) and two for their spouse (b. d.)
By deleting just those extra lines you should get what you were describing.
Hope this gives you ideas,
-
I agree with the previous post, to get what you describe sounds like a bare-bones Descendant Indented Chart with the Report Destination to an unformatted Text file.
I say "bare-bones" because to have only the names you would have to set the Report Options to exclude most information:
Sources Tab: none
Memos Tab: none
Sort By tab: birth date
Tags tab: untick all boxes
Names tab: Identifiers=none
But again you cannot specify the beginning and end person for this report type, as this is not a direct line report. You can only specify the Number of generations on the General tab of the report options. I can't think of a way at the moment to get a direct line report with only the names as you describe.
Hope this gives you ideas,
-
Hi Judy,
First go to the "mother". Note the ID number of fhe daughter.. Now delete the daughter tag so she is no longer a child. Now you should be able to change the SEX flag to Male. Finally add a Child tag and enter the daughter's ID number in the tag to relink her as "his" daughter.
-
No. The folder where TMG writes the backup file should be on the local disk and not either be in the Cloud or be in a folder being backed up to the iCloud. Only when TMG has completed creating its backup file should you then copy or move that TMG .sqz backup file to where it can be synced to the iCloud.
What are the pitfalls of,doing this?If any other program, whether a backup sync program or an antivirus monitor, is monitoring the folder where TMG is creating the backup then that other program "could" interfere with TMG writing the file and cause it to be corrupted. Will it always interfere? No. But enough users have noted that it "sometimes" will interfere that avoiding the possibility altogether is the only sure way to get an uncorrupted backup.
Let TMG do its thing on its own. Then move the file so the sync program can do its thing on its own.
Do the same thing in reverse when you restore. Retrieve the backup file from the iCloud to a non-TMG folder, then move it to a local TMG folder and have TMG restore it from there. This is the best way to keep each program from interfering with the other.
-
Exclude all the TMG program and data folders from automatic backup by any software. Use TMG to create a backup within a TMG folder. Only then copy or move the TMG .sqz backup file to a folder which the cloud software will back up
-
Judy,
Maybe it would help to say it another way? First the phrase "children carried forward" means those children who will be repeated (carried forward) as the Subject of their own separate Journal section later in the report. But children get their own later separate section only if they in turn have children. That separate Journal section will include all the tags specified to output for the Subject of a person's own section. But if a child does NOT have their own children, a separate Journal section will NOT be produced later for that child. (That is the definition of a Journal report.) The only place child-less children and their events will be output in a Journal report is within their parent's list of children.
The typical setting for the Report Option "abbreviated events" is "Only children that are carried forward" (i.e. children with children). Since these children will be repeated (carried forward) in their own Journal section in the next generation where they are the Subject of their own section, most people choose to have only "abbreviated events" in their parent's children section to avoid duplicating the output of all the event tags for this child in both the parent's children section and in that child's own section.
But most users do not choose "All children" because that also would abbreviate the events for those children who are not carried forward. Since the parent's list is the only place events for such children will be output, any events for such a child other than the specified abbreviated events will never be output in the Journal report with that setting.
As Terry suggests, some users will choose "All children" to avoid the output from lots of events for all children who have no children. But that is usually a special case.
Of course if the number of generations is limited and this is the final generation, the children of this last generation are a special case since their separate section would be in the "next" generation which will not output. Thus such children will not be "carried forward" to get their own section with all their events, whether or not they have their own children, so their events will output within the parent's list of children as specified for children not carried forward.
Does this help?
-
By the way, Judy,
Perhaps? what you really want to add are both the spouses and any genetic descendants of those spouses but who are not genetic descendants of the ancestor, e.g. children of a spouse by other partners. If so, when you finish above, click the Select All button again, and click the Add Others again. Now the count will include "family" descendants who are not direct genetic descendants since a child of a spouse by another partner has no genetic relationship to the ancestor of interest.
Hope this gives you ideas,
-
Judy,
Best way I know for that is to "begin" to create a Focus Group. First if there are people in the current Group when you open the Focus Group window make sure the Group is empty by clicking Remove All. Also for getting only the count be sure the Name variations box is not ticked. Then add one individual, the ancestor of interest. Next tick the Descendants box and set the number of Generations desired, e.g. 99. and also tick the Spouses box. Now click Add Others. Finally click the Select All button, and click the Add Others again. This will give all descendants and all their spouses. I think that is what you want? You do not need to save this Focus Group, just read the count of names in this group at the top.
-
Hi Judy,
If you only want to list the Principals linked to your Immigration tags, Terry's suggestion will work very nicely, and you can ignore the rest of this post.
However, if you (or others reading this post) want to list all Principals and Witnesses who are linked to a tag (e.g. an Immigration tag), that takes more steps, is more complicated, and the subsequent report which is required to output the date and/or location data from this tag is more cumbersome.
First you will need to create a temporary Flag, perhaps named MYTAG, with default N, and other value Y.
Now run a List of Events report with a filter of:
Tag Type... // Label // = Equals // {name of tag} // END
But in the Report Options, Secondary Output tab, choose the "Change Flag" option for "All Witnesses" to set the MYTAG Flag to 'Y'.
Once you run that report everyone linked to this type of tag, whether a Principal or a Witness, will have that Flag set.
Now you will run an Individual Detail report to output the results. Unfortunately this will output a separate page for each person, but is the best I could think of to get all the desired output about the tag. To select only these Principals and Witnesses of this tag type use a filter of:
MYTAG // = Equals // Y // END
In the Report Options, Sort By tab, set the sort as desired, probably by ID Number.
In the Report Options, Tags tab, set the Selected tag to output only (or at least) this one tag, but be sure to select "All events and witnessed events".
I also recommend on the Miscellaneous tab to only set the options for Parents Primary only, and Roles to minimize the output. Your choice whether to select the option to include Sources associated with this tag on that option tab. If you wish to output the sentence memos for both these Principals and Witnesses, on the Memos tab I would include Embedded, and Include memos from witnessed events, and also set Embed sentence [M]emo on the Miscellaneous tab. However, if you use split memos, note that this report will only output the first split memo part of either the Principal or Witness memo.While this produces a less than optimal report output, at least it is restricted to the tag of interest, outputs almost everything about this tag, and includes both Principals and Witnesses linked to these tags.
Hope this gives helpful ideas,
-
FGS
Employment 2016 sampson industries, iongmont, colorado; He also worked at [L1} on the date of [DD} for years after.
The sentence template is not being used, and variables are not being "filled in" on this report. You get the tag type Name, the Date text as entered, the entire Location text as entered, and the exact text of the Memo as entered. The output is the text you entered.
JOURNAL
[P] began employment .
2016, test Person (2655) began employment at sampson industries, longmont, colorado. He also worked at sampson industries on the date of 2016 for many years after.
This is also as expected since the sentence template is being used. First your sentence template says to output all parts (unqualified variable: ) of the entire Location. Then the sentence template says to output the entire Memo (). That memo contains a variable for one of the Location parts ([L1]). So the value for that variable is filled in and the memo is output, exactly as the template specifies.
It is perfectly fine to use variables within the text of the memo. Their values will be filled in. But if you also use those variables in the sentence template itself, you will get duplication. I suspect that Terry's sentence templates do not include the variables which he uses within the memo text.
As for the FGS, you do not use variables or sentence templates to control its output. You use the Report Definition Options. For example, the Places tab in the Report Options allows you to select which place fields will output. But that selection will be used for all tags. You cannot control the output of a specific tag.
As for the Journal, the sentence templates mostly control the output, but the Report Options can also have an effect. For example, the Places tab in the Report Options allows you to select which place fields will output. But that selection will determine what will output when filling in the unqualified [L] variable for all tags. If a specific location part variable is specified in the template or memo of a given tag, that is what you will get for that tag.
Hope this helps explain,
-
Hi Joe,
As Terry mentioned, variables are only resolved in narrative reports where sentences are used. The two reports you mention intentionally print out the actual text entered in fields such as the memo. That is by design so you can see what you have actually entered in such fields without having to go to the person and open the tag.
In Narrative reports you can locally modify the sentence template to only use the place parts you wish. So instead of a sentence with the unqualified location variable:
[P] was born
you could modify that sentence template perhaps to:
[P] was born
Which would give as output something like:
Person was born in 1945 in Addressee in City in State.
To get rid of the automatic extra "in" prepositions, use the option of leading spaces in the conditional variables:
[P] was born in
Person was born in 1945 in Addressee, City, State.
Note both the leading space and the trailing comma within the conditional markers.
If you do not include either the unqualified variable [L] in the sentence template, or those specific part variables, then you could enter data in [L2] and/or [L4] but it would not output in the sentence.
Again this would only affect sentences in narrative reports. Is this what you were asking?
Hope this gives you ideas,
-
Adding unrelated family
in The Master Genealogist v9
Posted · Report reply
Not really., Judy By your questions I suspect? that you have not used Flags before? In my opinion they are one of the most powerful and useful features of TMG. Perhaps it would be worth your time to begin by reviewing (again?) Terry's Tips about Flags here. Then review Terry's descriptions of both his Related-by Flags and his Connected Flag mentioned earlier. I also have an entire section on Flags (including several ideas for custom Flags) in the Style chapter of my on-line book.
The "Family Group" Flag concept (described by several users over time) is similar to Terry's two Flags mentioned above but slightly different, and is only one of many ideas for custom Flags used regularly by TMG users. As I suggested earlier, there are two main definitions which I recall being mentioned by users, but are likely many more. How you "set" the values of these Flags involves the same basic actions as how you set any Flag.
Definition one: Separate Flag for each family group.
Multiple custom Flags are created each with a unique name indicating a specific family group. Values are (N,Y). For example, you might have groups for Jones, Smith, and Baker, so you might define three separate Flags: JONES, SMITH, and BAKER. A person belonging to a given family group (however the user chooses to define "belong") has that group's Flag set to 'Y'. All other people by default are 'N'.
Advantages: a person can potentially "belong" to multiple family groups, i.e. they could have more than one of these Flags set to 'Y'. This multiple assignment ability helps when family groups intermarry.
Disadvantages: the user has many more different Flags to ensure each one is set appropriately.
Definition two: Single Flag to identify the one family group to which this person belongs.
A single custom Flag is defined with a name indicating its purpose (e.g. FAMGRP). The default value is '?' but multiple possible values are defined for this one Flag, each unique letter identifying a separate family group. For example, you might have lines for Jones, Smith, and Baker, so you might define the Flag values as: ( ?,J,S,B ). A person belonging to a given family group (e.g. Jones) has this Flag set to the value of their family group (e.g. 'J'). All unassigned people by default are '?'.
Advantages: only one Flag needs to be set to identify that person's membership in their one primary family group.
Disadvantages: the user must choose which one group a person "belongs" to in light of an intermarriage.
How to set Flags
These actions are the same no matter what type of custom Flag is defined. The set of defined Flags in a dataset exists for all People, but each person has their separate value assigned for each Flag. When the Flag is created, or when a person is added, each person has their Flag(s) set to its default value. Either the user changes the default value(s) of the Flag(s) one-by-one for each person, most likely when the person is added, or some method is used to identify a desired group of people and then a report is run filtered for that group to set the Flag to a specific value for all people in the group all at once.
Groups can be identified by selecting people on the Project Explorer possibly using a filter, or adding people to a Focus Group possibly using its ancestor/descendant feature. Once a group is identified, the Secondary Output of a List of People report filtered for that group can set their Flag to a given value at once for all those people. A group can also be identified by appropriate filters on a List of Event reports, whose Secondary Output can set their Flag to a given value for people associated with those events. It may take multiple actions to define all members of a group: one action may only be able to identify some, other actions identify more to be added to the group, etc.
Conclusion
There is no magic shortcut to setting Flag values. You must identify to TMG the appropriate people, and either set their Flag to a given value individually or as a group. It is because there is no magic shortcut that I suggested setting any appropriate Flags when you add the people, as that action is already dealing with each person so setting the Flags for each person becomes easier.
Hope this gives you a better idea of what Terry and I are suggesting concerning defining and setting Flags.