Jump to content

Michael Hannah

Moderators
  • Content count

    2,903
  • Joined

  • Last visited

Everything posted by Michael Hannah

  1. how to set up MRINs in TMG

    A couple of alternate ideas. You could use a split memo field on the Marriage tag and enter the MRIN in one of the memo fields. You then could have a different "language" (like Teresa's Columnar language) which would generate reports that used the MRIN but that split field was not used in "normal" reports. [search the forum for columnar language for more info.] Another option might be to cite a custom Source on each Marriage tag (possibly a source called MRIN) and enter your assigned number as the Citation Reference. Hope this gives you ideas, Michael
  2. Parents of a spouse in reports

    Sorry, but there is no defined standard variable for that as of version 6. Us users can always express a "wish" for such a variable for the future by such posts as this, but at the moment the only similar standard variable is [AO] and [AOE] for the "other" principal. However, you could create a custom tag (or customize an existing tag) and assign custom roles to the parents as witnesses in that tag, for example custom roles of FATH and MOTH. Then you could use the defined standard variables of [RA:rolename] or [RE:rolename] to get their ages in your custom sentences. This might be used to accomplish what you appear to want. Hope this gives you ideas,
  3. Living Together But Not Married

    I made a custom "Marr Not" tag type within the Marriage group for people who are known to have mated (since they had identified offspring and I want to show that shared parental relationship) but are not considered married in the typical sense. I defined the sentences for the various roles as follows: Role=Male (used only with P1) Male sentence: [P] [M3] [PO] Female sentence: -- Role=Female (used only with P2) Male sentence: -- Female sentence: [P] [M1] [PO] Role=Principal [P] and [PO] [M] Role=Witness [W] witnessed [WM1] of [P] I moved the standard roles Bride and Groom to the bottom of the list and do not use them. TMG requires events in the Marriage group to exist to print reports with correct birth order sorting of the offspring of the mating. If the relationship is simple and reciprocal I use the standard Principal roles for both parties and the sentence just has their names followed by a required [M] with everything I want to say about this relationship. I choose to put the male as P1 and the female as P2. If I want to say something different from each point of view then I use a split memo. [M1] will specify the relationship from the “Female” point of view with optional Date (usually a date range) and Location and [M2] as her comment. (I have the female's split memo first as I commonly know about the mother but not the father.) Then [M3] specifies the relationship from the “Male” point of view with optional Date and Location and [M4] as his comment. Note that having both [P] and [PO] non-optional automatically produces the standard "an unknown person" text if either is not specified. [WM1] describes the relationship from the Witness’ point of view, with [WM2] for added comments. Some have suggested other separate custom tag types, e.g. "Marr Coh" for known to have cohabited (lived together), and "Marr Rel" for known to have relations (sex) but not to have lived together. Most define these in the Marriage group, but you could define them in the Other group if they did not have offspring. My “lumper” preference seems served with my one "Marr Not" tag type in the Marriage group and using the memo to describe the nature of this relationship. However, having separate custom tag types may be of value for selecting which will print. Instead of separate tag types one could define appropriate roles for various specific relationships and associated different predefined sentences all in a similar single custom tag type. Hope this gives you ideas,
  4. Changes in Place Names Over Time

    Don't forget my suggestion of creating a location "pseudo" person. This is the simplest way that I have discovered to document within TMG multiple names of a location. And if you want a given event to reference the "standard" location, the location "pseudo" person can be linked as a Witness with an appropriate role using an appropriate NameVar of that "person".
  5. Changes in Place Names Over Time

    I agree that this is an issue. My workaround is as follows (but I only use it occasionally and only for those places that have greatly changed over time). I use as the place name for a tag whatever the place was called in the source citation that provided the evidence for this tag. If I know that this place name was only in use during a specific period and not afterwards, I use the date range in the Master Place List so that it prompts me if I use it outside that date range. My real workaround involves the use of a "pseudo" location person. A single location person could be used to link together multiple “place entries” in the Master Place List that actually referred to the same location by using multiple Name-Var tags with possible date ranges to reflect when the location was known by each name. Name indices would link all these locations to this one “person”. The primary name could be the Name-Var that is the “current” name, or could be a name identifying the latitude and longitude. A tag associated with a "real" person would have the actual name of the location as of the time of the event entered as a place from the Master Place List, but the location “person” could be linked as a witness, either using the actual Name-Var for that time or the “current” name with a possible witness sentence of “This location is currently named [W]”. If a larger area was identified by a single name for a period of time and then subdivided, the larger area “person” could be the “mother” of the multiple subdivided “daughters” who were created/born at the time of the subdivision. (I choose to make all location "pseudo" people female.) You can also have a custom tag in the Birth group for the creation or first settlement of this location. Various tags are possible to associate with a location, and various reports are now possible for these location "people". I define the Given name as the specific subdivision/location (e.g. “Adams Township”) and the Surname as the complete higher level locale, comma separated, beginning with smallest (e.g. “Washington County, Ohio”). I choose to place the country in the Suffix so I can define whether to output it by selecting an alternate name style. My two location name styles (one with country in the output, one without) display these names in picklists with the name parts separated by colons since the surname can have internal commas. I also define custom labels in the name style (i.e. [Location], [Locale], [Country]) for the name parts as a data entry aid. Hope this gives you ideas.
  6. Sorry, but I can't think of a way to do it this time. Maybe someone else will have an idea. I can suggest something for next time (but that doesn't help for this reunion): You could create a custom Flag (maybe called Reunion) and set everyone whose information you shared at the Reunion to 'Y'. Now after the reunion, any time you make a change to something in a person (have the discipline to) change the flag to 'N' so you will know that there is new information to report at the next reunion. Hope this gives you ideas,
  7. Education tag

    I changed the sentences of this standard tag to a more general purpose tag, and use it instead of also using the standard Graduation tag. [M1] defines what happened (“graduated from high school”), [M2] optionally precedes the location in the sentence since I prefer the flexibility of sometimes putting the name of the school here rather than as part of a location in the Master Place List, and [M3] has optional comments. Principal: "[P] [M1]." Witness: "[W] witnessed [P] [M1]." Hope this gives you ideas,
  8. Immigration sentences for children

    I use both of the two standard tags, but have customized both to deal with possible children or any others that came as a group. I also changed the sentences of the standard Immigratn tag to make the Date and the arrival Location non-optional for the immigration so if you don't include it you get the “unknown” phrases. I use the Principal role “Head” for P1, and do not use P2, and the Witness role “immigree” for all others immigrating with the “Head” as a group. [P]<, listed as [M1],> immigrated to [L] [D]< from [M2]>< along with [R:immigree]>.< [M3]> The split tag memo [M1] optionally provides the name of the Head as listed in the immigration documentation in case it is different than any Name-Var defined for this person, [M2] optionally specifies the claimed departure location, and [M3] has optional comments. My sentence for the Witness role “immigree” is: [W]<, listed as [WM1],>< as a [WM2]> led by [P1] immigrated to [L] [D]< from [M2]>.< [WM3]> The split Witness memo [WM1] optionally provides the listed name of this immigree, [WM2] the listed relationship to the Head (e.g. “son”), and [WM3] has optional comments. The listed departure location from the main split memo [M2] is included in the immigree sentence if it has been entered. If you create ship “pseudo” people in your dataset, you could also add the ship as a witness with custom role of “ship” and an appropriate sentence. I changed the sentences of the standard tag Emigration in a similar manner to require the Date and the Location from which the emigration is taking place, with equivalent “emigrated from”sentences and the Witness role “emigree”, Hope this gives you ideas.
  9. Education and/or University

    You might look at my custom and very generic Education tag. I posted it in the new forum that discusses custom tags. Hope this gives you ideas,
  10. CensusEnum tag

    It seems that recording Census data gives rise to the greatest variety of custom tags and sentences. Here is my main custom "CensusEnum" tag and its sentences which I use in place of the standard Census tag. I have an equivalent CensusX tag for recording index and soundex data. I have CensusFind and CensusXFind to indicate that I need to locate census data, and CensusNil and CensusXNil to record what I looked for but did not find. These tags and sentences are similar to this main enumeration tag. Hope this gives you ideas. Tag Overview I prefer to have the Head of Household as P1 with their unique data in the split main memo. I put names as recorded in the census as one of the parts of their split memo, not as a NameVar tag. All members of the household have one of the three enumeration roles “spouse”, “child”, or “Witness” (or the equivalent conclusiion roles "spouseAssumed", "childAssumed", "assumed") to this one tag with their data and their relationship to the HOH in their separate witness memos. The full actual census record is attached as an Exhibit. P2 is required to link to a "pseudo" census person. I do not use separate tags for each year as I use [P2F] for the year in the sentences, and most variable information is in the memos not the sentences. This is usually the only census tag I include in normal narratives. I cannot include the term “child” or “children” in the parents' sentences since TMG (currently?) provides no way to know if there are multiple people assigned to a (child) role, so I use the generic term “offspring”, and the sentences assume that individuals assigned the role “child” are offspring of both the head and the spouse. These sentences use the role variables (including [R:Witness] ) when I want a specific group, and [WO] when I want all witnesses regardless of role. I prefer to have the details of the focus person only print with that person and only identify the spouse and offspring with their specific roles. The nature/relationship of the other members of the household, and the details of all other members, are in their own narratives via their witness memos. Example narrative output might be: (two different years as HOH, one as a Witness) Joe Smith was enumerated in the 1880 Census in Chicago, Illinois, on 3 Jun 1880 as head of household with his wife Mrs. Mary Smith and his offspring Robert Smith, Mary Sue Smith, and George Smith, details: W, M, 29, Tanning, 3 months unemployed, born- Ohio, parents born- Ohio. His household also included Mrs. Mary Jane Roe. Emil Ring and Albert B. Conger were included in the household and listed as lodgers. Joseph J. Smith was enumerated in the 1900 Census in Chicago, Illinois, on 11 Jun 1900 as head of household with his wife Mrs. Mary Smith and his offspring George Smith, Louise Smith, and Susan Smith, details: White, Male, age 48 born Oct 1863 in Ohio, married 23 years, father born- Ohio, mother born- Ohio, occ- Bar Tender, rents house. 24 year-old Mary Flannigan was also enumerated with the household as a servant. The 1910 Census in Chicago, Illinios, enumerated J. J. Smith as a father-in-law in the household of Robert P. Jones and Mrs. Mary Sue Jones, details: 59, M, W, widow, b- Ohio, occupation- county surveyor. The tag elements have the following data: P1 -- Head of household, assigned the role “Head” P2 -- Census "pseudo" person identifying this census date and location, assigned the role “Extract”” since I either have a transcription or image for this household attached as an exhibit. These "people" have a naming convention of the Given name identifying the kind of census data, including the year, and use the Given name sentence variables (e.g. [P2G] for what it is, and [P2F] to get the year) of this pseudo person in sentences. The Surname identifies the full location covered by this data, comma separated, beginning with country down to the location detail of this data. I can use Surname name variable in sentences for large to small, and the normal location sentence variables for small to large. Finally, the suffix identifies the range covered by this type of census data. With Given name beginning with the year, and Surname the ordered location from largest to smallest, reports of these "people" can be sorted either by year (by Given name) or by location (by Surname). Example: Given="1920 Census" Surname="USA, Ohio, Washington County, Adams Township" Suffix="EDs 103-105" Date -- Only entered if you have an exact actual enumeration date, otherwise left blank Sort Date -- If no actual date then I use “Jun” of census year because of the sort dates I use for the other types of census tags Location -- as specified in the census, detail depends on how full you want your Master Place List to be, maybe street address? I choose to lump for the Place List and show location details like the street address only in the Citation Detail. Main memo -- name of head recorded in census||phrase of the head’s specific census data||sentence of other information to be included only with the head, such as a list of others enumerated but not linked as witnesses||sentence to be appended with head and all Witnesses spouse role Witness memo -- name recorded in census||phrase of the spouse’s specific census data||optional information about the spouse to follow the word ‘ as ’||sentence of extra information about this spouse of the head of household. The term “wife” or “husband” is generated automatically in the sentence based on the SEX flag of this witness. child role Witness memo -- name recorded in census||phrase of this child’s specific census data||required text about the child to follow the word ‘ as ’||sentence of extra information about this child of the head of household. The text about the child (following the word "as") is usually “ a son ” or “ a daughter ” as enumerated (which sometimes proves to be in error and is entered “ a daughter [sic] ”). generic Witness role memo -- name recorded in census||phrase of this person’s specific census data||relationship of this witness to the head to follow the word ‘ as ’||sentence of extra information about this witness. Entering relationship text in the memo precludes the need for separate roles/tags, example text: “ his mother-in-law ”, “ her uncle ”, etc. spouseAssumed role Witness memo -- name recorded in census, or just ‘ him ’ or ‘ her ’ if unnamed||phrase of the spouse’s specific census data||phrase of the census data that makes you think this is the spouse to follow the word ‘ as ’||sentence of extra information about this spouse. The term “presumed wife” or “presumed husband” will be based on the SEX flag of this witness. For the relationship data enter a phrase like “ one of the five unspecified family members ” to show count, “ the female 20 to 30 ” to show age category, etc. There will usually be either [WM2] or [WM3] but not both. childAssumed role Witness memo -- name recorded in census, or just ‘ him ’ or ‘ her ’ or ‘ a child ’ if unnamed||phrase of this child’s specific census data||phrase of the census data that makes you think this is a child of the head to follow the word ‘ as ’||sentence of extra information about this presumed child of the head of household. In this relationship portion of the memo enter a phrase like “ one of the five unspecified family members ” to show count, “ one of the 3 females under age 5 ” to show age category, etc. There will usually be either [WM2] or [WM3] but not both. assumed role Witness memo -- name recorded in census, or just ‘ him ’ or ‘ her ’ if unnamed||phrase of this person’s specific census data||phrase of the census data that makes you think this person is enumerated in this household to follow the word ‘ as ’||sentence of extra information about this witness. In this relationship portion of the memo enter a phrase which will follow the word “ as ”, e.g. “ one of the five unspecified family members ” to show count, “ one of the 3 females under age 5 ” to show age category, etc. There will usually be either [WM2] or [WM3] but not both. Witness Roles: spouse or child or Witness Used for all people named and enumerated with this Head of Household (could use picklist to select all at once then go back and fill in their memos and set their roles). The role “child” is for children of both this head and this spouse, otherwise use “Witness” with appropriate text. For sentences to work, link using the Name-Marr for any women married at this time and enumerated with their married name. If person is only implied by the data (e.g. U.S. census records prior to 1850), use one of the appropriate “assumed” roles instead. childAssumed or spouseAssumed or assumed For census enumerations where some aspect of the people in the household is described, but they are not named (e.g. 3 males under age 5), or where they are named but the relationship is not specified (possibly left blank), these custom witness roles are used to link those individuals you believe are the ones enumerated in this household and/or you assume to have these relationships. The role “childAssumed” is for children of both this head and this spouse, otherwise use “assumed” with appropriate text. Head (P1) sentences Male: [M1] was enumerated in the [P2G] in [L]< on [D]> as head of household< with his wife [R:spouse]>< with [R:spouseAssumed] who is presumed to be his wife>< and his offspring [R:child]>< and his presumed offspring [R:childAssumed]><, details: [M2]>.< His household also included [R:Witness].>< His household is also assumed to include [R:assumed].>< [M3].>< [M4]> Female: [M1] was enumerated in the [P2G] in [L]< on [D]> as head of household< with her husband [R:spouse]>< with [R:spouseAssumed] who is presumed to be her husband>< and her offspring [R:child]>< and her presumed offspring [R:childAssumed]><, details: [M2]>.< Her household also included [R:Witness].>< Her household is also assumed to include [R:assumed].>< [M3].>< [M4]> Extract (P2) sentence [:CR:][:CR:][BOLD:][P2F] Census Enumeration[:BOLD] of the household of [BOLD:][M1][:BOLD] in [L]< on [D]> linked to [P1]< and to [WO]> spouse role sentences Male: The [P2G] in [L]< on [D]> enumerated [WM1] in [P1S] household as her husband< as [WM3]><, details: [WM2]><. [WM4]><. [M4]> Female: The [P2G] in [L]< on [D]> enumerated [WM1] in [P1S] household as his wife< as [WM3]><, details: [WM2]><. [WM4]><. [M4]> child role sentence The [P2G] in [L]< on [D]> enumerated [WM1] as [WM3] in the household of [P1]< and [R:spouse]><, details: [WM2]>.< [WM4].>< [M4]> generic Witness role sentence The [P2G] in [L]< on [D]> enumerated [WM1]< as [WM3]> in the household of [P1]< and [R:spouse]><, details: [WM2]>.< [WM4].>< [M4]> spouseAssumed role sentences Male: The [P2G] in [L]< on [D]> enumerated [WM1] in [P1S] household, presumably her husband<, as [WM3]><, details: [WM2]><. [WM4]><. [M4]> Female: The [P2G] in [L]< on [D]> enumerated [WM1] in [P1S] household, presumably his wife<, as [WM3]><, details: [WM2]><. [WM4]><. [M4]> childAssumed role sentence The [P2G] in [L]< on [D]> enumerated [WM1] presumably as a child of head of household [P1]< and spouse [R:spouse]> < as [WM3]><, details: [WM2]><. [WM4]><. [M4]> assumed role sentence [W] is assumed to be [WM1] who was enumerated< on [D]> in the [P2G] in [L]< as [WM3]> in the household of [P1]< and [R:spouse]><, details: [WM2]><. [WM4]><. [M4]>
  11. Enhancement Request - Last Edit Date

    I can understand the desire for this enhancement, but I would suggest that the only meaningful enhancement was a special toggle that would simply turn on/off the automatic updating of the "Last edited" information. Not something I can currently think of using, but at least that would provide total control. As two possible customizations, have you thought about both a custom flag and/or a custom tag. I have a custom flag (actually a couple) that I use for editing "work in progress". I can set values of "E=needs to be edited", "P=partially complete, in progress" and "Y=yep this person has been edited", or other values like "N=not really edited" or "R=really edited, the edit date is for real". I have also seen suggestions of a custom tag in the Other group for every person, called "Last edited" or other similar names. The date of this tag can then be set manually to whatever you wish with the memo describing the last thing you edited, and you can deselect the tag from output reports. You can easily give everyone such a tag with the TMG utility. It is added work to manually change the date of such a tag yourself, but at least TMG does have the flexibility of a "work-around" way to accomplish this. Whether this added work is worth it is a matter of how important such information is to you. Hope this gives you ideas,
  12. report names by birth month

    The filter mentioned will only look for Birth tags. In case you have some people who only have Baptism tags in the Birth group and do not have Birth tags, it would be more complete if you changed the filter line: Tag Type... Label = BIRTH AND to: Tag Type Group is BIRTH AND Since TMG puts the standard Baptism tag in the Birth group, and uses that date for birth in the absence of a Birth tag, you might have some people with only that data. Otherwise, with the previous filter you might miss these people. You might also check out John Cardinal's "On this day" utility that prints events associated with a given date. www.johncardinal.com/otd/ There might be ways to use his utility to produce reports that may interest you.
  13. Mills Source Categories

    To me one of the best characteristics of TMG is its ability to be customized to work "My Way" . Those who want to "lump" into a few source types can, and those who want to "split" into multiple source types can . What seems to be the issue is what is provided as source types "by default" for a project or dataset, i.e. you at least start out by having this list of source types in your Master Source List (MSL) that are not currently used or needed in your dataset, or are not how you would want them. My wish is to have NO source types by default in a brand new dataset, but to have an easy facility to import pre-defined source types into the MSL from a file. That way the possibly thousands of Mills source types, or the relatively few Lackey source types, could be provided in files, and could allow you to scroll through them to select those that you wished to import into this dataset. You would then even be able to choose some from one type and some from the other! With a matching easy way to export your own customized source types you could maintain your own "master" list for multiple datasets you have, and easily share with other users. It would even provide a way for authors like Mills and Lackey to develop and provide their own "official" TMG examples of their source types. Anyone share my wish?
  14. You are most welcome, Jim. To be able to document something that such a knowledgeable user as yourself didn't know makes me quite pleased with myself
  15. Immigration/emigration

    I also use both of the two standard tags, but have customized both. I changed the sentences of the standard Immigratn tag to make the Date and the arrival Location non-optional for the immigration so if you don't include it you get the “unknown” phrases. I use the Principal role “Head” for P1, and do not use P2, and the Witness role “immigree” for all others immigrating with the “Head”. [P]<, listed as [M1],> immigrated to [L] [D]< from [M2]>< along with [R:immigree]>.< [M3]> The split tag memo [M1] optionally provides the name of the Head as listed in the immigration documentation in case it is different than any Name-Var defined for this person, [M2] optionally specifies the claimed departure location, and [M3] has optional comments. My sentence for the Witness role “immigree” is: [W]<, listed as [WM1],>< as a [WM2]> led by [P1] immigrated to [L] [D]< from [M2]>.< [WM3]> The split Witness memo [WM1] optionally provides the listed name of this immigree, [WM2] the listed relationship to the Head (e.g. “son”), and [WM3] has optional comments. The listed departure location from the main split memo [M2] is included in the immigree sentence if it has been entered. If you create ship “pseudo” people in your dataset, you could also add the ship as a witness with custom role of “ship” and an appropriate sentence. I changed the sentences of the standard tag Emigration in a similar manner to require the Date and the Location from which the emigration is taking place, with equivalent “emigrated from”sentences and the Witness role “emigree”, Hope this gives you ideas.
  16. As Jim suggested, many of us have a separate Project that we have created where we run tests. From previous tests that I have run, a Max Surety is computed for each category [12DPM] based on the highest surety value in any source citation for that category that has been entered for a particular tag, whether the citation has been excluded or not. If the tag prints, the printing of a citation is then based only on whether it is an excluded citation, not on its surety. If the surety threshold has been set, and the Max Surety for all categories is less than the threshold, the entire tag and its citations will not be printed. However, if some category meets the threshold but other categories do not, then the event will print but those categories that do not meet the threshold will not print. For example if the Max Surety for Principal1 meets the threshold but Date and Place do not, the tag will print with the Principal1’s name, but the sentence will operate as if the Date and Place were blank, i.e. if they are non-optional sentence variables they will produce the “unknown” text. So in your case, if you have the Surety threshold set to one, the tag will print and the Principal1's name will print, but the Date will operate as if blank. Hope this helps,
  17. Family View Problem

    As Virginia pointed out, Version 6 has added considerable flexibility to the TMG views by providing a way to customize multiple versions of layouts. Earlier she mentioned Terry's Tips, and I would recommend http://tmg.reigelridge.com/layouts.htm as it describes the Version 6 layouts. While Version 6 now allows other subwindows (e.g. flags, Focus Group, etc.) to also share screen space with your FGS type Family View, if you want to almost duplicate the old Version 4 view, you can. Select the Family View for the Details subwindow, close any other subwindows, and from the "Window" menu item be sure that the Children subwindow is also selected along with Details. Now move and/or resize the Details to cover the top half of the TMG window, and the Children to cover the bottom half, resizing the columns in the Children subwindow to your preferences. Then save this custom layout with a name of your choice as described in Terry's Tips. Whenever you want this view, you can now select your custom layout from the "View >> Layouts" menu. Hope this gives you ideas,
  18. Family View Problem

    The three "views" only change what you see in the "Details" window for a given layout. Person view gives you the primary parents in a subwindow with the primary name, and then the tags. Tree view will give you multiple generations, with no extra information about the ancestors. Family view will give you person, their "currently viewed spouse", and the two sets of primary parents, with BMD information for these six people, and only a count of the children. Any other windows, like Siblings, Children, Flags, etc. are dependent upon what other windows you chose to include in this layout and do not change or disappear by selecting a different "view". Under the main menu item "Window" click to turn on or off any of these other windows, arrange them as you wish, and then save this layout with an appropriate name. Now that layout can have whatever other windows you want, like Children, and the Details window can be whichever of the three views you want.
  19. Research Log Question

    But, Jim, I don't understand. I don't see the need for these extra steps in order to get the List of Tasks report to show the Principals for a task linked only to an event. Further, you can only link to one person, whereas the task can have two Principals. My tasks are only linked to events, I have never linked to a person. When I edit any of my tasks it shows Event assigned, and Person, Source, and Repository "Not assigned yet". Even in the Research Log itself, when you highlight a task the "Subject" it displays is the event ID and name followed by the Principals, and when you edit the task the Principals are listed following the Event assigned. In the Person View of a person, if I click on the Research Log icon it lists all the tasks that are assigned only to events but for which this person is a Principal for those events. I don't find a circumstance where the Principals are not listed. So I still don't understand Joan's problem.
  20. Research Log Question

    Joan, I cannot duplicate your situation. All of my tasks are assigned only to events and my List of Tasks report outputs the Principals that are set for that event tag. What are your options for your List of Tasks report set to? As an example, I have my "Sort By" tab set to "Task Name" and the "Names" tab set to "Surname caps" and "ID Number". When I set the Subject of the report to "All Tasks" and print to screen each task gives the Task Name on the first line. It then prints the Tag Type name on the second line followed by the tag date if there is one, then the names of the Principals with their surnames capitalized and their ID number, and finally the location entered into the tag. Do you not see this? Are you looking for names of Witnesses to your event tags? These do not show on the List of Tasks.
  21. Searching TMG for people by place

    Of course, if you simply want people associated with a certain type of event in that city or state, you could have something like Birth Group... City Contains [?] END
  22. Report of all sources with unknown value

    You might get close with a List of Sources with a filter for all the source element groups that appear on the Source Definition General Tab that are empty. The non-people source element groups are: Title, Short Title, Subtitle, Short Subtitle, Record Type, Date, Second Date, Location, Second Location, Publisher, Publisher Location, Series, Edition, Version, Volumes, Pages, File Reference, Record Number, Film Number. For example: Title Is Empty ORShort Title Is Empty ORSubtitle Is Empty OR... The "people" source element groups (Author, Subject, Compiler, Editor, Second Person) are specified slightly differently: Author-ID... Is Empty ORSubject-ID... Is Empty OR... There is a maximum number of filter lines for a single filter, so you may have to run multiple reports to check all source elements. Of course, for a given source a particular element may not even be defined, so you will be listing those when you do not need to, so this may lessen the value of such a report. It would probably be more useful to restrict the report to a particular type of source and only check for the source element groups that you have defined for that source type, e.g. Source Type is Census, Federal (Filmed) AND( Title Is Empty OR Short Title Is Empty OR Subtitle Is Empty OR ... ) END Hope this gives you ideas.
  23. Searching Tag Types

    A more complex filter for a List of People that would find people with missing "-bio" parents but had some kind of parent relationship tag might be: Mother* Is Known ANDMother-Bio... ParentID = Equals 0 END just in case you have some that are not "-fst" but something else.
  24. WishList - Witnesses in multiple locations

    Clever idea, Teresa, and useful for a lot of purposes. For other workarounds, you could simply write a custom main tag sentence and/or memo to say exactly what you want. Of course Teresa's idea will automatically let the special information show associated with the Witness name in the main tag sentence. I usually don't put these details in the main tag sentence, but reserve these details to only print in the Witness sentences and use split Witness memos and appropriate Witness sentence structures. Thus that Witness person's sentences mention other information unique to them, like their location, age, etc. I could see this wish adding extreme complexity to the main tag sentences, especially if multiple people are assigned to a generic Witness role or to a custom role. What would you have [W] or [WO] produce, especially if all or part of the location and/or age were missing/not computable? Or a whole new set of [Wx] variables like [WL] for names and locations, [WA] for names and ages, [WAL] for names and ages and locations in that order, and matching [WOL] etc. ...???? I have often thought it might be nice if the Witness memos, including the split Witness memo parts, could be referenced in the main tag sentence, as a more generic solution to this wish. But I could not get my mind around the complexities to even figure out how to propose a solution, especially in the light of multiple people assigned the same role, each with their unique Witness memo. If I were Bob, I would probably file this wish in the "too hard to even figure out how to do" folder, but then Bob has surprised us with features that I previously thought were too hard to do, so you never know. At least there ARE workaround ways to output what you want with the current software, just not as easy or quite as automated as your wish might imply.
  25. More questions

    For surnames with various spellings, some have chosen to add a non-primary custom tag in the Name group (e.g. NameStand) for every person whose primary name tag is a different spelling. Adding this tag identifies the standard spelling of the surname that they choose to use in their database. By having this custom name tag, all such people in the database will sort within that standard surname in lists like the Project Explorer as long as you do not limit the list to primary names only. Of course, since it is a separately named tag you can selectively choose whether to include it in various reports. Another method I have heard about is to create a custom tag in the Other group (e.g. Surname) with P1 this individual and P2 a "pseudo" person entered into the database. This "pseudo" surname person would have their primary NameVar tag with just the surname and a suffix of "SURNAME". This "person" could then have tags, such as all the various NameVars for that surname, and documentation about that surname, linked in this single place to document all the information you have found about this surname and its variations. The Details view of this person will also show all the people you have linked via the custom tag, and if you use the "real" person's birth as the date for the tag they will show in chronological order. Of course, since it is a separately named tag you can selectively choose whether to include it in various reports. And if you use a flag to distinguish this person as "pseudo" from "normal" people, you can choose whether to include this person in various reports. Hope this gives you ideas,
×