Jump to content


Sherman Peabody

Member Since 21 Aug 2014
Offline Last Active Oct 21 2020 09:21 PM
-----

Topics I've Started

Footnote References in Narrative Reports

02 November 2014 - 06:30 PM

When the option "Print notes" is set for a narrative report, shouldn't the superscript footnote reference appear at the end of the note text in the narrative instead of at the end of the fact sentence?  As it is, the note text appears to be unsourced.

 


First Experience with TMG Direct Import

22 September 2014 - 09:12 PM

Below are comments on what the import does and how it might be adjusted to be better.  I see direct import as providing a best possible import of TMG data into the existing RootsMagic infrastructure. I do not consider this to be the place for discussion of TMG features that do not transfer well into RM.

 

All in all, the TMG Direct import is good.  These are the things that jumped out at me. I'm sure I'll find others as a walk thru 21,000 persons...

  • When a fact is created from the appearance of a witness on a non-family fact, it should be attached to the witness’ person record, not the principal’s.  For example, a witness to a death event might be the widow or the informant on the death certificate.  These facts should be attached to the widow or the informant, not to the person who died.
  • I would think in almost every case that a TMG sentence refers to the [L] variable, the RootsMagic equivalent should be [PlaceDetails] [Place]. Or more specifically, <[L]> should be replaced with <[PlaceDetails]>< [Place]>.
  • A spouse as a witness does not imply that the event should be a family event.  For example, a spouse being a witness to a death most likely implies that it was intended to be an individual event attached to the spouse.  Another example, a spouse may be identified (as a witness) as the “closest relative” on a military registration.  That does not mean the spouse also registered for the military.
  • Birth date and death date are not populated in the Name Table.  Assuming TMG’ers will be importing to RM version 6, rebuilding indices should be recommended in the documentation as a "post-import" procedure.
  • With even a modestly large database, the first “Progress” screen that is displayed when an import is done can take quite a while before it displays anything.  A simple “working…” displayed in that popup window might be reassuring.
  • It sure would be nice if TMG split memos could be interpreted and imported as customized sentences and TMG split witness memos could be interpreted and imported as customized witness sentences, but I definitely understand why that is a "version 2" feature.
  • TMG surety values are not imported in any way.   I’m not sure how they should import, but does RM import QUAY values from GEDCOM?  I would think it would be similar.
  • When a TMG date variable ([D]) appears inside angle brackets (“<>”), if anything else appears inside the angle brackets other than the [D] variable itself, the RM variable [Date:Plain] should be used.  This allows the alterations of date prepositions in TMG to be realized in RM. It might not be the best use of RM [Date] constructs but more of the TMG sentences will come across without extra prepositions.

TMG features I already miss...

24 August 2014 - 10:03 PM

I would like to see a way to subdivide the [description] value and then be able to refer to the subdivisions in the sentence.  For example:

 

Description:  Lizzie|25|daughter|Mississippi

Sentence:     [Person] appeared  as [Desc:1], a< [Desc:2] year old>< [Desc:3]><, born in [Desc:4]>.

Result:          "Elizabeth Jones appeared as LIzzie, a 25 year old daughter, born in Mississippi."

 

[Desc] would represent the value of the entiire field just as it does now. Nothing between two vertical bars would represent a blank subdivision value.