
#1
Posted 01 August 2013 - 02:34 PM
#2
Posted 01 August 2013 - 05:33 PM
Put what you want to print with the field, if that field is used, between <>.
#3
Posted 01 August 2013 - 07:48 PM
[person] retired< [Date]> < [PlaceDetails]> <in [Place:Plain]>.
I hope this does not mess up anything else.

#4
Posted 01 August 2013 - 09:17 PM
Since you didn't tell us you were using Place details, I used place as an example. You could also have < from [Placedetails:plain]> to get the sentence you posted in your first post if ABC Company is in the Place details.
John Doe retired< [Date]>< from [Placedetails:plain]>.
You could have a sentence, for example, like:
John Doe retired< [Date]>< from [Placedetails:plain]> whose head office was < at [Place:plain]>.
John Doe retired in 2008 from ABC Company whose head office was at Dallas, Dallas County, Texas.
This would be a sentence as you might customize it on the Edit person screen.
The sentence must always have any field you want to print in the sentence.
If you have a description field you want to print, you would add [desc] to the sentence.
In some ways you are learning a completely new program with some familiar elements as RM 4 was a complete rewrite of RootsMagic.
#5
Posted 02 August 2013 - 04:24 AM

#6
Posted 02 August 2013 - 10:04 AM
Place details are specific to RootsMagic. The chance that another program will import them is very slim and that data will be lost for the person you gave the gedcom to. Even importing a RM 6 gedcom into RM 3 will lose the Place details.
If you do make a gedcom for use in RM 4 + versions, remember to check the RM specific box on the export gedcom screen.
Sharing facts is another thing to think about if you are going to be sharing with gedcom with some one else. The fact is only tied to the Principal and not the Sharee when importing a gedcom into another program.
#7
Posted 02 August 2013 - 02:04 PM
Is there any custom report you can help me create to tell me of anyone who has a RM specific field or detail field filled in so I can see them all to correct back?
#8
Posted 02 August 2013 - 03:42 PM
Any fact > Place details > "is not blank" will find Persons having an event with a Place Detail.
Persons having Family facts such as Marriage, Census (family), Residence (family) can be found with:
Census (family) > exists > "is True"
or by using the Fact List report.
Persons sharing a fact/event are not readily found in RM. Consequently, some outboard tools have been developed:
People Who Share a Fact with a Principal List - Query produces a list
People Who Share A Fact with a Principal, But Who Are Not in a Tree in The File List - Query produces a list
Facts - Split Shared to Individual converts shared facts to individual facts for compatibility with 3rd party software
These are also included in the RMtrix utility, making them pretty easy to use.
Tom user of RM7630 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com wiki, exploiting the database in special ways >>>
app, a bundle of RootsMagic utilities.
#9
Posted 02 August 2013 - 04:24 PM
#10
Posted 03 August 2013 - 02:39 PM
#11
Posted 04 August 2013 - 10:52 AM
Laura, on the RM6 export of a gedcom I do not see a box labeled RM specific fields..is it perhaps labeled something else?Before you decide to use Place details, you need to think about whether you will ever be sharing with someone else who uses another program by gedcom.
Place details are specific to RootsMagic. The chance that another program will import them is very slim and that data will be lost for the person
If you do make a gedcom for use in RM 4 + versions, remember to check the RM specific box on the export gedcom screen.
.
#12
Posted 04 August 2013 - 11:10 AM
The very last one in the left hand column.
#13
Posted 04 August 2013 - 12:19 PM
#14
Posted 05 August 2013 - 07:25 PM
#15
Posted 05 August 2013 - 09:05 PM
1 BURI 2 _PRIM Y 2 DATE 1 JAN 1951 2 PLAC Glasgow, Lanarkshire, Scotland, United Kingdom 2 ADDR Craigton Cemetery & Crematorium, Cardonald 3 MAP 4 LATI N55.8468694 4 LONG W4.3337611The Place value is with the PLAC tag; the Place Detail value is attached to the ADDR tag. The Place Detail geocoordinates are also included under the MAP tag, which is subsidiary to ADDR. The only non-standard GEDCOM tag is _PRIM.
The question is, what does the destination software do with the data exported by RootsMagic to standard GEDCOM tags?
Tom user of RM7630 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com wiki, exploiting the database in special ways >>>
app, a bundle of RootsMagic utilities.
#16
Posted 05 August 2013 - 09:16 PM
Every fact has it's own default sentence. Changing the way one fact's sentence reads does not gobally change the other facts. You have to change each fact separately.
If you have place details entered on the Edit person screen and no [Placedetails] field in the sentence, then place details are not going to print in the Narritive report. I have one fact that is marked to enable the desciption field, and I enter data into the desciption field for the fact. But, I don't want that data printed in a Narrative report so I don't have [Desc] in the fact sentence.
#17
Posted 06 August 2013 - 05:41 AM
#18
Posted 06 August 2013 - 10:20 AM
What a can of worms I have now discovered that I have opened . Not wanting to use the Place detail field for fear of loosing data, my new coding for retirement of [person] retired< [Date]> <from [Place:Plain]>.is working well but I now see the default prefix for the place field appears to be IN no matter what fact is used...so many many of my common facts read with an improper prefix because I am not using the place detail field. I guess I now how to go thru all the facts and see which ones uses the detail field and change the coding to the place:plain coding I used in the retirement one and pick a prefix that fits the fact (marriage, occupation, graduated etc.etc ) . This seems like a lot..but the IN prefix reads odd currently. For example..now it says Joe graduated in 2002 in UCONN in Storrs, CT. It would read better to say AT UCONN or even from UCONN . If I learn how to create a custom fact instead of changing the default, would that fact be exported in a gedcom or imported into other programs or would they too be possibly eliminated as the RM specific field of Place Details might?. I am trying to take a step back and decide the best way to proceed so my narratives read correctly, my data is safe..and fact imput is easier and not have to always figure out how to customize each entry and I would appreciate any advice.
This sentence template uses AT
[person] graduated< [Date]>< [PlaceDetails]>< [Place]>.
This sentence template uses FROM
[person] graduated< [Date]>< from [PlaceDetails:Plain]>< [Place]>.
You can select to edit the List>Fact Type sentence template so it effects everyone. Or, customize the fact sentence for the one event on their Edit Person screen. On the right on the very bottom under Sentence click on "Customize Sentence" and edit it there.
RootsMagic
#19
Posted 06 August 2013 - 11:38 AM
[person] was born< [Date]>< [PlaceDetails]>< on his father's farm about 3 miles East of [Place:plain]>
I suggest you create a new database and drag and drop a family into it to experiment with sentence templates before making any more changes in your database. When you know what changes you want to make, you can then make them in the main database.
I find it helpful to open a person's Edit person screen in the Play database and customize the sentence for a fact with all the fields entered until I have the sentence as I want it for the fact default sentence. I can see the results of the change right away without going back and forth to the Fact type list. When I get it as I want it, I copy and paste the default sentence for that fact into my main database.
Help, Index, search for template, template languages , click Display button, Sentence Template language.
#20
Posted 06 August 2013 - 12:44 PM
Also tagged with one or more of these keywords: fact type
Product Support - Current Versions →
RootsMagic 7 →
Discussion →
Fact types ported as Fact NoteStarted by magmatic, 02 Aug 2020 ![]() |
|
![]() |
||
Product Support - Current Versions →
FamilySearch Family Tree →
Duplicate Fact TypesStarted by GlenB, 29 Jan 2018 ![]() |
|
![]() |
||
Product Support - Current Versions →
RootsMagic 7 →
Discussion →
Newspapers.com and Fold3 Ancestry facts creating unique RM fact typesStarted by GalinAZ, 23 Oct 2017 ![]() |
|
![]() |
||
Product Support - Current Versions →
RootsMagic 7 →
Discussion →
Merge "Fact Type"Started by BaldEagle7, 18 Sep 2017 ![]() |
|
![]() |
||
General →
RootsMagic Wish List →
TreeShare Enhancement Request - Fact Type ExclusionStarted by GreenwoodKL, 08 Jul 2017 ![]() |
|
![]() |