I have an idea that I would like some feedback on. In my tree I have a lot of people and for most of them, I don't actually have their birth, death or marriage certificates. Instead, I have other documents with varying degrees of surety. For the people that I am closest to, I would like to get the certificates when I get the time and money to do so, but in the meantime I want a method in TMG to identify which certificates I have and which I don't have. To do this, I was thinking of creating three new tag types. These would be direct copies of my standard Birth, Death and Marriage tags, but with the suffix of '-C' so 'Birth'-C'. They would function identically to their corresponding tag, but would indicate that I had the certificate for this event. Then I could run reports on my project that showed me which certificates I still had outstanding for my ancestors. I could also see at a glance on my TMG person screen if I had the certificates for that person by looking for the '-C' suffice on the BDM tags. All my certificates are stored in the same place, so it shouldn't be an insurmountable job to change the tag types... ... But before I go ahead I would be interested in hearing if people could point out the flaw in my plan or suggest a better way. Thanks, Tim from Melbourne
I would suggest a custom flag instead. It would be easier to add/remove that designation. Constance On Fri, Feb 15, 2019 at 3:46 PM Tim Hill <timandpolly@gmail.com> wrote: > I have an idea that I would like some feedback on. > > In my tree I have a lot of people and for most of them, I don't actually > have their birth, death or marriage certificates. Instead, I have other > documents with varying degrees of surety. > > For the people that I am closest to, I would like to get the certificates > when I get the time and money to do so, but in the meantime I want a method > in TMG to identify which certificates I have and which I don't have. > > To do this, I was thinking of creating three new tag types. These would be > direct copies of my standard Birth, Death and Marriage tags, but with the > suffix of '-C' so 'Birth'-C'. They would function identically to their > corresponding tag, but would indicate that I had the certificate for this > event. > > Then I could run reports on my project that showed me which certificates I > still had outstanding for my ancestors. I could also see at a glance on my > TMG person screen if I had the certificates for that person by looking for > the '-C' suffice on the BDM tags. > > All my certificates are stored in the same place, so it shouldn't be an > insurmountable job to change the tag types... > ... But before I go ahead I would be interested in hearing if people could > point out the flaw in my plan or suggest a better way. > > Thanks, > > Tim from Melbourne > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/tmg@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >
This would be an excellent situation to use roles. For example, you could add a role of "certificate" or "need certificate" to each of the existing tags using the same sentence as the principal role. You can then run a list of people with a birth (or marriage or death) tag where role equals whichever variation you desire. There would be no need to copy tags and you can easily adjust the role once you obtain the certificate. Alternatively, you could set up new flags for death-cert (? = default; Y = have the cert; N = need the cert) and run reports or create focus groups based on the flags. A similar flag could be used for the marriage and death certs. Nancy > -----Original Message----- > From: Tim Hill <timandpolly@gmail.com> > Sent: Friday, February 15, 2019 2:45 PM > To: TMG@rootsweb.com > Subject: [TMG] BDM Certificates > > For the people that I am closest to, I would like to get the certificates when I > get the time and money to do so, but in the meantime I want a method in > TMG to identify which certificates I have and which I don't have. > > To do this, I was thinking of creating three new tag types. These would be > direct copies of my standard Birth, Death and Marriage tags, but with the > suffix of '-C' so 'Birth'-C'. They would function identically to their > corresponding tag, but would indicate that I had the certificate for this > event. > > Then I could run reports on my project that showed me which certificates I > still had outstanding for my ancestors. I could also see at a glance on my > TMG person screen if I had the certificates for that person by looking for the > '-C' suffice on the BDM tags. > > All my certificates are stored in the same place, so it shouldn't be an > insurmountable job to change the tag types... > ... But before I go ahead I would be interested in hearing if people could > point out the flaw in my plan or suggest a better way. > > Thanks, > > Tim from Melbourne
Tim Hill wrote: > I have an idea that I would like some feedback on. > In my tree I have a lot of people and for most of them, > I don't actually have their birth, death or marriage certificates... > in the meantime I want a method in TMG to identify > which certificates I have and which I don't have. > To do this, I was thinking of creating three new tag types... Hi Tim, Others have suggested a custom Flag, or Roles on the Standard tags, which are good ideas. But in this case I prefer separate tag types as you are thinking of doing. However, in my case I do the reverse of what you choose to do. I have BirthAssume, Marr Assume, and DeathAssume for people where I do not have what I consider definitive citations. But as you note one can easily change such a tag type to the Standard name when one is able to cite better documentation. Whichever way one indicates the difference, an advantage of using a separate tag type is that they can be color coded to be different than the Standard tag types. I find that even easier to spot than to just have a different tag name. I have even gone to the trouble to customize TMG so that the BDM Hotkeys will invoke these "Assume" tags for new tags and will be used for new people. (Ask how if you want to also do that.) I can then use the Secondary Output on reports to set Flags for people who have "Assume" tags of interest, but also Filter on some other criteria to focus my research. Of course one could Filter based on a combination of Flags. But I find colored tags more "in my face". Hope this gives you ideas, Michael
Hahaha Tim, I agree with your comments re: time and money... I am similar to Nancy and find flags the way to go. Andrew from Melbourne. -----Original Message----- From: Tim Hill <timandpolly@gmail.com> Sent: Saturday, 16 February 2019 7:45 AM To: tmg@rootsweb.com Subject: [TMG] BDM Certificates I have an idea that I would like some feedback on. In my tree I have a lot of people and for most of them, I don't actually have their birth, death or marriage certificates. Instead, I have other documents with varying degrees of surety. For the people that I am closest to, I would like to get the certificates when I get the time and money to do so, but in the meantime I want a method in TMG to identify which certificates I have and which I don't have. To do this, I was thinking of creating three new tag types. These would be direct copies of my standard Birth, Death and Marriage tags, but with the suffix of '-C' so 'Birth'-C'. They would function identically to their corresponding tag, but would indicate that I had the certificate for this event. Then I could run reports on my project that showed me which certificates I still had outstanding for my ancestors. I could also see at a glance on my TMG person screen if I had the certificates for that person by looking for the '-C' suffice on the BDM tags. All my certificates are stored in the same place, so it shouldn't be an insurmountable job to change the tag types... ... But before I go ahead I would be interested in hearing if people could point out the flaw in my plan or suggest a better way. Thanks, Tim from Melbourne _______________________________________________ Email preferences: https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&data=02%7C01%7C%7Cfa81bac5ef174cbfedc908d69386a316%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636858603795414084&sdata=VFaGp9MnzW1Wwfu%2BFRw7nbPU9y0u83GNrPS9hwq8Df0%3D&reserved=0 Unsubscribe https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Ftmg%40rootsweb.com&data=02%7C01%7C%7Cfa81bac5ef174cbfedc908d69386a316%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636858603795424092&sdata=HbeC6UQGQ7q1LBslDaYf9pYsfOHWdB0kQ3ixA8FPkBY%3D&reserved=0 Privacy Statement: https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&data=02%7C01%7C%7Cfa81bac5ef174cbfedc908d69386a316%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636858603795424092&sdata=%2F9ke0gqV3UvM7EmQkgtsuYZvKDrPokN6AdHheOUl4HQ%3D&reserved=0 Terms and Conditions: https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&data=02%7C01%7C%7Cfa81bac5ef174cbfedc908d69386a316%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636858603795424092&sdata=j6NucsCYZTz0zAgziejiDl0Fn9BsCKiHrRq3nEKInVc%3D&reserved=0 Rootsweb Blog: https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&data=02%7C01%7C%7Cfa81bac5ef174cbfedc908d69386a316%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636858603795424092&sdata=ODdC8BHKlVaxceIWkdnvvWpNqF31%2F6yXxhN3vsDfH34%3D&reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community