Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
  • Location
    Short Pump, Virginia
  1. Citation suggestions for ftDNA matches

    My point is that ftDNA does not use kit numbers, other than as your own login. I suppose I could email her and ask for her kit number, but that's not anything that can be searched on in the match list.
  2. Boy, do I miss the Rootsweb list! Hope everyone has migrated over here in the meantime. I've been having a fairly unproductive conversation on the Family Tree DNA group on Facebook about citing a Family Finder match in my DNA Match tag. What I do for Ancestry matches is to include the URL to the person's match screen or their profile screen. Ancestry doesn't make it easy to find people again (especially those distant cousins that are 30 pages in), the "Favorite" star notwithstanding. So the URL is the only way I can easily get back to a person. For Gedmatch, I include their kit number. But as far as I can tell, Family Tree DNA doesn't use any kind of ID or kit number, and I'm at a loss for how to include a match locator in my citation. For right now, the person I'm working on is front and center on the first page of my match list, so she's not likely to get lost, yet. But in years to come, who knows, maybe more close cousins will test and she'll drop to the second, third, page, etc. I realize that this locator is only for me. Other people aren't going to be able to find my matches just by searching on whatever I decide to use for a locator. But I'm considering adding a screenshot as an exhibit. I don't normally use exhibits due to my perception that my .pjc file would balloon in size, but this seems like a no-brainer. Have any of you encountered this and come up with a solution that works for you? Robin in Short Pump
  3. Privatizing gedcoms

    Thanks Jim, I agree. And I have no problem with my own data, but since I manage multiple family members' tests who may not feel the way I do, I think it's prudent to at the very least, get their birthdates/places out of there. Guess I missed that suppress details check box.
  4. Privatizing gedcoms

    This is a message I tried to send to the TMG-L list which may be down, I don't know. I think I know the answer to this, but I’d like your confirmation. I would like to privatize living people’s information in a gedcom export for Gedmatch. I poked around in the export and in the help, but I’m not seeing anything specifically related to that. Is this possible in TMG or do I just need to edit the gedcom file? My gedcom only shows my direct ancestors, so there aren’t many living people left on it: me, my husband and my parents, so this is not a problem. But I do manage several DNA tests, so I would have to do this multiple times... Robin in Short Pump
  5. v9.05 Error message

    Thanks Jim. This won't renumber my people will it? Just want to make sure...
  6. v9.05 Error message

    I had a computer crash the other day and ever since then I’m getting a seemingly benign error message when I input into and tab out of a date sort field that the repeat.fpt file is missing or invalid. In fact the file is where it has always been and a hit of the ignore button makes it go away until the next time. Is there an easy fix? Right now, it’s just annoying. Robin in Short Pump
  7. Using Age Variable in Sentence Structure

    Regarding the use of <[AE]>, I discovered that it returns an age when the death date is a "before" date. So it reports the principle died at "age 64 years" when the age actually is not known, just that the person was deceased when an event occurred, like a spouse who predeceases the other one. So obviously the answer is "don't use it in these cases." I would like to use it in my default death tag sentence (in conditional brackets), but I really don't know how many death tags I have in my database with "before" dates that would have to be manually changed to <[A]>. Opinions? Robin in Short Pump
  8. Best practices--Narrative reports

    I just ran into a complication. Nothing I can't live with, but I'd prefer to fix it if I can. My original Obit tag had a "Survivor" role. I forgot about that when I set up my new obit tag, so when I used TMGU to change from the old tag to the new one, I lost all my survivors (on about 350 obits). These roles aren't anything I ever intended to show on reports, it was just for my own research purposes. I haven't deleted the old tag, I just renamed it. Is it possible to reclaim those survivors if I change back to the old tag? Or are they just gone?
  9. Best practices--Narrative reports

    Thanks Jim, that worked splendidly!
  10. Still using v7.04. Years ago, I created a custom tag called "obit". I put it in the death group. Now I'm much wiser and realize I want to be able to make both deaths and obits primary. Is there a way to get "obit" out of "death" and put it in "other"? That would solve my problem, wouldn't it? Or would I have to create a new obit tag and then re-enter everything? So, if that won't work, I'll have to decide how to live with narrative reports that are either "primary events only" or "all events." The latter shows every birth-alt date and I don't want that. Can I exclude all the non-primary birth-alt or other redundant events? I looked in the help and see exclusion markers for memos, but not for tags. I believe this is controlled in the report options, but it's all or nothing this way. Basically, what I want in my narrative reports are the normal primary BMDB events and the text of obituaries that I have transcribed over the years. Once I get this figured out, I can take that knowledge and decide if there are other tags I also want to include, like occupation. Or whatever. I'll eventually upgrade to v9, would doing it now help me with this problem? I read Terry's TMG Tips all the time, and I'm not seeing anything that looks like a new feature in this regard. Thanks for your help. Hope Rootsweb comes back up soon so we can commence with the list. Robin in Short Pump
  11. Thanks for the explanation and I can see many applications for using accent colors. However, I don't think they'll help much in my situation. The reason I wanted an LOC report was to see at a glance which tags had the offending source. With just accenting the person, I'd have to go through all the tags manually, looking for that source. So what I ended up doing is running an LOC to Excel, where I sorted by subject 1 and then filtered the citation detail with some unique text. Then I filtered by the most common surname, coming up with 8 pages of tags to fix. After they're all done (and it's going pretty fast thanks to ctrl-I, I already have half of them done) I'll then filter by the rest of the surnames and hopefully there won't be much left to fix. Maybe someday the programmers will see fit to add a flag filter to the LOC report. Or maybe I'm just the only knucklehead who has to pay dearly for setting up sources in the early days without thinking about how they'll be used years later. Well, at least I have sources! Thanks again, Michael.
  12. I've never worked with accent colors, so bear with me. So, using your method, I won't ultimately be working with a report, I'll see these accents in the project manager? Will it just accent the person? Or will it accent the tag containing the source?
  13. Picklist madness

    Yes it would. I use the expanded picklist. Didn't know about the shortcut. Thanks Virginia.
  14. Picklist madness

    I'm running v7.04 and the picklist is driving me crazy. I'm cleaning up sources and citations and I want to look people up by their ID numbers. I can't get the dropdown to STAY at ID number as I go from person to person. It usually reverts back to the first choice on the list (surname), although once in a while it doesn't. Is this a bug? Really, I think the dropdown choice I select should stay there until I change it. Is this fixed in version 8? Robin
  15. I'm cleaning up 25 years of sources and inconsistencies and have a source with 3300 citations. I would like to work on these in an organized and manageable fashion, one family line at a time. Is this one of those situations where I have to run a report first that sets a flag and then run the LOC report on the flag? If so, I could use some guidance on how to set these up. Thanks! Robin