Following my data files conversion from RootsMagic to FH7 I have a great many events/attributes (thousands of undefined "Residence" tags for example) which remain undefined. I've been attempting to resolve them using the Change Any Fact Tag plug-in, but the <UDF Tags> list never shows up. I'm probably doing something wrong, but I don't see what it could be.
Any suggestions will be greatly appreciated.
Robert
* Change Any Fact Tag plug-in
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
-
tatewise
- Megastar
- Posts: 27078
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Change Any Fact Tag plug-in
The approach needed depends on your objectives and exactly what data has imported from RootsMagic.
Facts (Events & Attributes) that are undefined are NOT necessarily Uncategorised Data Fields (UDF).
They may be perfectly valid custom facts that don't have a Tools > Fact Types... definition yet.
If those "great many events/attributes (thousands of undefined "Residence" tags for example) which remain undefined" are listed on the Facts tab of the Property Box then they are valid facts that just need a Tools > Fact Types... definition.
I can explain what you need to do to create those definitions if you want to keep your custom facts.
However, you may want to convert those undefined custom "Residence" tags to standard Residence facts.
The Change Any Fact Tag plugin will do that.
Such undefined custom facts will need Source Tag Set set to either <Custom Events> or <Custom Attributes>.
Then your custom facts will be listed in Source Tag Name.
The Target Tag Set would be Standard.
If you really do have fact level UDF then they would be listed as part of the <UDF Tags>.
Other types of UDF need a different approach, starting with the UDF List plugin as explained in the KB article Handling Uncategorised Data Fields.
Facts (Events & Attributes) that are undefined are NOT necessarily Uncategorised Data Fields (UDF).
They may be perfectly valid custom facts that don't have a Tools > Fact Types... definition yet.
If those "great many events/attributes (thousands of undefined "Residence" tags for example) which remain undefined" are listed on the Facts tab of the Property Box then they are valid facts that just need a Tools > Fact Types... definition.
I can explain what you need to do to create those definitions if you want to keep your custom facts.
However, you may want to convert those undefined custom "Residence" tags to standard Residence facts.
The Change Any Fact Tag plugin will do that.
Such undefined custom facts will need Source Tag Set set to either <Custom Events> or <Custom Attributes>.
Then your custom facts will be listed in Source Tag Name.
The Target Tag Set would be Standard.
If you really do have fact level UDF then they would be listed as part of the <UDF Tags>.
Other types of UDF need a different approach, starting with the UDF List plugin as explained in the KB article Handling Uncategorised Data Fields.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
Re: Change Any Fact Tag plug-in
Dear Mike,
Conversion to the standard fact is exactly what I want for "residence." Unfortunately both my residence and residence (fam) events show up just as undefined "residence" in the FH7 fact types list. If I define one of them, FH7 creates a new undefined residence. The created version, which I place in a custom fact set doesn't show up in the Change Any Fact plug-in in any fact set.
The upshot is that I cannot change the individual residence fact into the standard FH7 residence fact and if I try to get FH7 to recognize the family residence fact it doesn't pick up the data and creates a new undefined residence fact.
Similar difficulties arise with some of the other family facts converted from RootsMagic — for example, immigration.
If I can't solve this problem I may have to abandon my effort to convert to Family Historian.
Conversion to the standard fact is exactly what I want for "residence." Unfortunately both my residence and residence (fam) events show up just as undefined "residence" in the FH7 fact types list. If I define one of them, FH7 creates a new undefined residence. The created version, which I place in a custom fact set doesn't show up in the Change Any Fact plug-in in any fact set.
The upshot is that I cannot change the individual residence fact into the standard FH7 residence fact and if I try to get FH7 to recognize the family residence fact it doesn't pick up the data and creates a new undefined residence fact.
Similar difficulties arise with some of the other family facts converted from RootsMagic — for example, immigration.
If I can't solve this problem I may have to abandon my effort to convert to Family Historian.
-
tatewise
- Megastar
- Posts: 27078
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Change Any Fact Tag plug-in
Robert, please don't give up so easily.
The first thing to do is to locate those Tools > Fact Type... definitions you created and delete them, as they only serve to confuse.
Remember I said, "I can explain what you need to do to create those definitions if you want to keep your custom facts."
The thing is you don't use the New... button.
Please confirm that your "residence" facts appear on the Facts tab of the Property Box for Individuals.
If they are not listed there then they are not facts.
Then use Tools > Fact Types... and drag the dotted bottom right corner of the Fact Types dialogue to make it much bigger.
Now tick the Show Hidden option on the right and click the 5th column heading Fact Set near the top middle.
That should list all your imported facts as Fact Set <none> and Visible <undefined>.
Select one of those facts and click the Edit... button and OK the warning message.
In the Create Fact Definition dialogue type RootsMagic or Robert into the Fact Set box to identify your custom facts.
Click the Create button and OK any warning message that may popup.
In the Fact Definition dialogue just click OK for the time being the details can be refined later as necessary.
When you come to Edit... subsequent facts, RootsMagic or Robert will be on the Fact Set droplist.
For custom facts that you want to retain in FH that is all you need to do for now.
It may sound a bit longwinded, but it is very quick once you get into the swing.
When you have achieved the above, then we can deal with converting some to standard facts using the plugin.
The first thing to do is to locate those Tools > Fact Type... definitions you created and delete them, as they only serve to confuse.
Remember I said, "I can explain what you need to do to create those definitions if you want to keep your custom facts."
The thing is you don't use the New... button.
Please confirm that your "residence" facts appear on the Facts tab of the Property Box for Individuals.
If they are not listed there then they are not facts.
Then use Tools > Fact Types... and drag the dotted bottom right corner of the Fact Types dialogue to make it much bigger.
Now tick the Show Hidden option on the right and click the 5th column heading Fact Set near the top middle.
That should list all your imported facts as Fact Set <none> and Visible <undefined>.
Select one of those facts and click the Edit... button and OK the warning message.
In the Create Fact Definition dialogue type RootsMagic or Robert into the Fact Set box to identify your custom facts.
Click the Create button and OK any warning message that may popup.
In the Fact Definition dialogue just click OK for the time being the details can be refined later as necessary.
When you come to Edit... subsequent facts, RootsMagic or Robert will be on the Fact Set droplist.
For custom facts that you want to retain in FH that is all you need to do for now.
It may sound a bit longwinded, but it is very quick once you get into the swing.
When you have achieved the above, then we can deal with converting some to standard facts using the plugin.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
Re: Change Any Fact Tag plug-in
I can do that. some of the undefined facts appear as both "event" and attribute." How should I deal with those?
-
tatewise
- Megastar
- Posts: 27078
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Change Any Fact Tag plug-in
That is Ok and the dialogue will raise a warning saying you have both an Event and Attribute with the same Name.
Just click OK.
You will probably want to convert them to all be Attributes or all be Events using the Change Any Fact Tag plugin.
We can deal with how to do that later, as there is a special trick to differentiating the two identical Names.
Just click OK.
You will probably want to convert them to all be Attributes or all be Events using the Change Any Fact Tag plugin.
We can deal with how to do that later, as there is a special trick to differentiating the two identical Names.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
Re: Change Any Fact Tag plug-in
Dear Mike,
Again, thank you so much. Order is beginning to emeerge from chaos. As you suggested, I've defined all my undefined facts but one, and placed them into a fact set.
The one remaining is a problem. It's a residence tag. When I define it and place it in a my fact set it does not register or affect some of my residence data facts. A new undefined residence tag immediately emerges. When I look at some — not all — of the residence facts in my data the template sentences still show the default "John Smith experienced residence, etc."
I deleted one of my residence facts and re-established it as "residence." The re-established fact used the sentence template from the residence fact in the standard fact set.
Once I have this residence tag fixed I can proceed to paring down the facts which appear as both attributes and events under the same name, as you suggested.
Should you have any suggestions for dealing with the recalcitrant residence tag I'd be most grateful.
Robert
Again, thank you so much. Order is beginning to emeerge from chaos. As you suggested, I've defined all my undefined facts but one, and placed them into a fact set.
The one remaining is a problem. It's a residence tag. When I define it and place it in a my fact set it does not register or affect some of my residence data facts. A new undefined residence tag immediately emerges. When I look at some — not all — of the residence facts in my data the template sentences still show the default "John Smith experienced residence, etc."
I deleted one of my residence facts and re-established it as "residence." The re-established fact used the sentence template from the residence fact in the standard fact set.
Once I have this residence tag fixed I can proceed to paring down the facts which appear as both attributes and events under the same name, as you suggested.
Should you have any suggestions for dealing with the recalcitrant residence tag I'd be most grateful.
Robert
-
tatewise
- Megastar
- Posts: 27078
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Change Any Fact Tag plug-in
If I understand correctly, you've defined a custom 'residence' fact and that is correctly associated with some of your facts.
Then in Tools > Fact Types... there is still another Fact Set <none> and Visible <undefined> 'residence' fact.
That suggests that you have more than one variant of similarly named custom 'residence' facts, but each slightly different.
Maybe Events and Attributes or maybe Individual and Family facts.
Use the same method to Edit... each such variant <undefined> 'residence' fact.
BTW: When you deleted your custom 'residence' fact and added a standard Residence fact you were performing a similar conversion as the Change Any Fact Tag plugin, but it repeats it automatically for every matching fact.
Anyway, you now have several similarly named facts, i.e. those multiple 'residence' facts and Event and Attribute pairs.
Now the trick to differentiate such similarly named facts is to use Edit... and change the Label field.
So for an Event and Attribute pair, you could add " Event" to the Label of the Event.
For each 'residence' variant add some distinguishing text to their Label to make each one unique.
When you run Change Any Fact Tag set Source Tag Set to your Fact Set name RootsMagic or whatever you chose.
The Source Tag Name droplist should offer all your custom facts and they should all have different Labels.
So you can for example select the Event of an Event and Attribute pair and in the Target settings choose the Attribute.
For one of the Source 'residence' variants, in the Target settings you would choose Standard and Residence.
Then click the green button on the right under the Target settings to perform the conversion.
All the above was performed on the Individual Records tab for Individual facts.
You can repeat the process on the Family Records tab for Family facts.
However, that will not allow a Family 'residence' fact to be changed to two Individual Standard Residence facts.
That will need a different technique that I can explain when we get there.
Then in Tools > Fact Types... there is still another Fact Set <none> and Visible <undefined> 'residence' fact.
That suggests that you have more than one variant of similarly named custom 'residence' facts, but each slightly different.
Maybe Events and Attributes or maybe Individual and Family facts.
Use the same method to Edit... each such variant <undefined> 'residence' fact.
BTW: When you deleted your custom 'residence' fact and added a standard Residence fact you were performing a similar conversion as the Change Any Fact Tag plugin, but it repeats it automatically for every matching fact.
Anyway, you now have several similarly named facts, i.e. those multiple 'residence' facts and Event and Attribute pairs.
Now the trick to differentiate such similarly named facts is to use Edit... and change the Label field.
So for an Event and Attribute pair, you could add " Event" to the Label of the Event.
For each 'residence' variant add some distinguishing text to their Label to make each one unique.
When you run Change Any Fact Tag set Source Tag Set to your Fact Set name RootsMagic or whatever you chose.
The Source Tag Name droplist should offer all your custom facts and they should all have different Labels.
So you can for example select the Event of an Event and Attribute pair and in the Target settings choose the Attribute.
For one of the Source 'residence' variants, in the Target settings you would choose Standard and Residence.
Then click the green button on the right under the Target settings to perform the conversion.
All the above was performed on the Individual Records tab for Individual facts.
You can repeat the process on the Family Records tab for Family facts.
However, that will not allow a Family 'residence' fact to be changed to two Individual Standard Residence facts.
That will need a different technique that I can explain when we get there.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
Re: Change Any Fact Tag plug-in
Dear Mike,
I think I understand the label trick. the problem is that the minute I define the undefined residence tag and place it in a fact set, a new undefined one springs up immediately. I can't delete it because it points to data and the one I've just defined has no effect on the sentence templates; it can be deleted as it doesn't seem to have picked up any facts.
I have not yet used the Change Any Fact plugin to merge a residence fact for my fact set with the standard residence tag.
Robert
I think I understand the label trick. the problem is that the minute I define the undefined residence tag and place it in a fact set, a new undefined one springs up immediately. I can't delete it because it points to data and the one I've just defined has no effect on the sentence templates; it can be deleted as it doesn't seem to have picked up any facts.
I have not yet used the Change Any Fact plugin to merge a residence fact for my fact set with the standard residence tag.
Robert
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
Re: Change Any Fact Tag plug-in
Here is the GEDCOM entry for one of the facts which are part of the undefined Residence:
1 RESI
2 DATE 17 APR 1940
2 _SHAR @I8@
3 ROLE Bx_child_resident
2 PLAC Bronx, New York
2 ADDR 219 Grant Avenue
2 SOUR @S611@
3 PAGE Jack Lax household
1 HUSB @I6@
1 WIFE @I7@
1 CHIL @I8@
1 CHIL @I191@
1 CHIL @I192@
1 CHIL @I193@
1 RESI
2 DATE 17 APR 1940
2 _SHAR @I8@
3 ROLE Bx_child_resident
2 PLAC Bronx, New York
2 ADDR 219 Grant Avenue
2 SOUR @S611@
3 PAGE Jack Lax household
1 HUSB @I6@
1 WIFE @I7@
1 CHIL @I8@
1 CHIL @I191@
1 CHIL @I192@
1 CHIL @I193@
-
tatewise
- Megastar
- Posts: 27078
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Change Any Fact Tag plug-in
You may not believe this but you have tripped over the same bug that I reported to Calico Pie a while ago!
The Family Residence (RESI) attribute is a standard fact in GEDCOM 5.5.1 that FH v7.0 is meant to honour.
That fact was not allowed in GEDCOM 5.5 which was supported by FH v6.2 which partially explains the following.
(This is different from the standard Individual Residence (RESI) attribute that is OK in all versions.)
From the perspective of the Family record that standard RESI tag is considered a perfectly valid Residence fact.
If it was not a valid tag it would have been considered a UDF and would not appear on the Facts tab.
However, Tools > Fact Types does NOT recognise it as a valid Family Residence attribute saying it is <undefined> and that is the bug. When you define it manually it just gets further confused.
So in Tools > Fact Types please delete those custom Family Residence Events that have a red bullet on the left.
Ignore the warnings about associated data. The deletion will have no effect on your Residence (RESI) facts.
When the bug gets fixed the symptoms we are experiencing will go away.
You may wish to add weight to my report by using http://www.calico-pie.com/osticket/open.php to report the problem yourself regarding the standard Family Residence fact RESI tag not being supported by Tools > Fact Types, and mention the Project was imported from RootsMagic.
The Family Residence (RESI) attribute is a standard fact in GEDCOM 5.5.1 that FH v7.0 is meant to honour.
That fact was not allowed in GEDCOM 5.5 which was supported by FH v6.2 which partially explains the following.
(This is different from the standard Individual Residence (RESI) attribute that is OK in all versions.)
From the perspective of the Family record that standard RESI tag is considered a perfectly valid Residence fact.
If it was not a valid tag it would have been considered a UDF and would not appear on the Facts tab.
However, Tools > Fact Types does NOT recognise it as a valid Family Residence attribute saying it is <undefined> and that is the bug. When you define it manually it just gets further confused.
So in Tools > Fact Types please delete those custom Family Residence Events that have a red bullet on the left.
Ignore the warnings about associated data. The deletion will have no effect on your Residence (RESI) facts.
When the bug gets fixed the symptoms we are experiencing will go away.
You may wish to add weight to my report by using http://www.calico-pie.com/osticket/open.php to report the problem yourself regarding the standard Family Residence fact RESI tag not being supported by Tools > Fact Types, and mention the Project was imported from RootsMagic.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
Re: Change Any Fact Tag plug-in
Thanks so much, Mike. I've done as you suggested, although the red-marked undefined residence reconstitutes itself immediately.
I will write to Calico Pie as you suggested. When the bug is fixed I'll probably start all over with a fresh conversion from RootsMagic. There's some useful work I can do on the RM front.
Thanks again and all good wishes.
Robert
I will write to Calico Pie as you suggested. When the bug is fixed I'll probably start all over with a fresh conversion from RootsMagic. There's some useful work I can do on the RM front.
Thanks again and all good wishes.
Robert
Re: Change Any Fact Tag plug-in
I'm really new to FH but almost positive I have the same problem. And it was an import from RootsMagic.
Mike, you said, "So in Tools > Fact Types please delete those custom Family Residence Events that have a red bullet on the left.
Ignore the warnings about associated data. The deletion will have no effect on your Residence (RESI) facts.
When the bug gets fixed the symptoms we are experiencing will go away."
I'm not sure if I'm doing something or if Calico Pie changed something. When I try to delete as stated above, not only do I get a warning about associated data, it won't let me delete it at all until I remove all references to it. And I'd be willing to do that but there are many and I don't know if there is a way to remove them except one by one. If there is, please let me know. Or if you think I'm doing something wrong, please let me know.
By the way Mike, I appreciate all your work on this forum. You have no idea how many times I've searched for an answer to something and you had it.
Jackie
Mike, you said, "So in Tools > Fact Types please delete those custom Family Residence Events that have a red bullet on the left.
Ignore the warnings about associated data. The deletion will have no effect on your Residence (RESI) facts.
When the bug gets fixed the symptoms we are experiencing will go away."
I'm not sure if I'm doing something or if Calico Pie changed something. When I try to delete as stated above, not only do I get a warning about associated data, it won't let me delete it at all until I remove all references to it. And I'd be willing to do that but there are many and I don't know if there is a way to remove them except one by one. If there is, please let me know. Or if you think I'm doing something wrong, please let me know.
By the way Mike, I appreciate all your work on this forum. You have no idea how many times I've searched for an answer to something and you had it.
Jackie
Thanks,
Jackie
Jackie
-
Robert Jacobs
- Famous
- Posts: 111
- Joined: 21 Mar 2015 18:03
- Family Historian: V7
- Location: Ellensburg, Washington, U.S.A.
- Contact:
Re: Change Any Fact Tag plug-in
I think we have to wait until Calico Pie deals with the bug. As Mike Tate suggested, I too have reported it. A ticket has been opened but there's been no action as yet. Calico Pie must have many inquiries and there may be other problems to fix.
I certainly wouldn't delete any of the underlying data. You say you have "many;" I have hundreds. If I cannot get the problem resolved in FH7 I shall have to stick with RootsMagic — which I'd prefer not to do.
If you were to open a ticket perhaps it would lend a little more urgency to the matter. It would also ensure that you'll be notified when all's well.
Robert
I certainly wouldn't delete any of the underlying data. You say you have "many;" I have hundreds. If I cannot get the problem resolved in FH7 I shall have to stick with RootsMagic — which I'd prefer not to do.
If you were to open a ticket perhaps it would lend a little more urgency to the matter. It would also ensure that you'll be notified when all's well.
Robert
-
tatewise
- Megastar
- Posts: 27078
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Change Any Fact Tag plug-in
Jackie, I think you are taking what I said out of context. Robert had tried to add custom fact definitions for those imported Family Residence facts (with a red bullet on the left). I was advising him to delete those custom fact definitions.
Jackie, if you have not added any custom definitions then you have none to delete.
Do not confuse those facts with the Standard Individual Residence fact that has never changed.
Robert, the 'problem' is minimal unless you need 'perfect' Reports.
FH will continue to handle those Family Residence facts without upsetting your Project data.
Jackie, if you have not added any custom definitions then you have none to delete.
Do not confuse those facts with the Standard Individual Residence fact that has never changed.
Robert, the 'problem' is minimal unless you need 'perfect' Reports.
FH will continue to handle those Family Residence facts without upsetting your Project data.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
ColeValleyGirl
- Megastar
- Posts: 4853
- Joined: 28 Dec 2005 22:02
- Family Historian: V7
- Location: Cirencester, Gloucestershire
- Contact:
Re: Change Any Fact Tag plug-in
Personally, I don't believe opening multiple tickets for the same problem with Calico Pie will achieve anything except gumming up the works...
Helen Wright
ColeValleyGirl's family history
ColeValleyGirl's family history