This is a re-post I made to TMG-L: I don't know to what extent RootsMagic personnel will monitor the TMG-L for reports on direct import experiences and problems so I would encourage you to: - post problem/bug reports at http://support.rootsmagic.com/anonymous_requests/new (although the linking page says "We offer free online technical support for paid customers") OR - join the RootsMagic Forums at http://forums.rootsmagic.com/ and post to RootsMagic 6 > Issues with tags for "TMG" "import" RM staffer Renee Zamora monitors both and manages a tracking system for bugs and enhancement requests. While I participated with Jim in testing direct import before its release, I am but a novice with TMG and tested imports from the Sample Project and from a 5000 person Project loaned by a long-time TMG user. So I cannot readily answer advanced TMG user questions that involve complex usage of its features. I have just published a page on the differences in sentence template languages and formatting codes which may be of interest to TMG-RootsMagic explorers, especially those technically inclined. It's at: http://sqlitetoolsforrootsmagic.wikispaces.com/TMG-RootsMagic+Sentence+Variables+%26+Format+Codes An issue which I'm sure many will detect, but surprisingly was absent from the 5000 person project, is that sentences for sources with split Citation Detail (CD1, CD2,..) do not contain any of the Citation Detail. The full value is there in the [CD] field but the sentence templates use [CD1] etc, not [CD]. A fix is to manually edit the Source Template sentence templates to use [CD] in the sentences - there are only 3 or 4 such source templates in the Sample Project - however that changes the order and lengthens the Short Footnote and the || separator remains in the output. A much better result is to add [CD1] et al fields to the source template field definitions and then edit each citation to separate the pieces out of [CD] into the new fields. Unfortunately, every citation needs to be edited - for some users this may number in the thousands or even tens of thousands. I'm hopeful that the RootsMagician will be persuaded to find the resources to automate this parsing and mapping on import. Meanwhile, I am conceiving a SQLite procedure which might be able to do it after import. Tom On Sun, Sep 21, 2014 at 9:59 AM, Jim Byram via <tmg-refugees@rootsweb.com> wrote: > Thanks, Barbara. > > Two omissions in the import have been found so far... the place LatLong > value and the place comments. I've reported those. > > The RootsMagic import needs the project and exhibits in their folders. It > will not import from a TMG .SQZ backup file. > > The TMG backup is a ZIP file. If necessary, you can always change the > filetype to ZIP and drag the project and exhibits folders out of a backup > to > the appropriate locations. > > Jim > > *** > To unsubscribe from the list, please send an email to > TMG-REFUGEES-request@rootsweb.com with the word 'unsubscribe' without the > quotes in the message subject and body. > ------------------------------- > To unsubscribe from the list, please send an email to > TMG-REFUGEES-request@rootsweb.com with the word 'unsubscribe' without the > quotes in the subject and the body of the message >

I've created an interim solution to the split Citation Details problem, described at: http://sqlitetoolsforrootsmagic.wikispaces.com/TMG-RootsMagic+Split+Citation+Details Tom > On Sep 21, 2014, at 3:03 PM, Tom Holden <ve3meo@gmail.com> wrote: > ... > > I have just published a page on the differences in sentence template languages and formatting codes which may be of interest to TMG-RootsMagic explorers, especially those technically inclined. It's at: > > http://sqlitetoolsforrootsmagic.wikispaces.com/TMG-RootsMagic+Sentence+Variables+%26+Format+Codes > > An issue which I'm sure many will detect, but surprisingly was absent from the 5000 person project, is that sentences for sources with split Citation Detail (CD1, CD2,..) do not contain any of the Citation Detail. The full value is there in the [CD] field but the sentence templates use [CD1] etc, not [CD]. A fix is to manually edit the Source Template sentence templates to use [CD] in the sentences - there are only 3 or 4 such source templates in the Sample Project - however that changes the order and lengthens the Short Footnote and the || separator remains in the output. A much better result is to add [CD1] et al fields to the source template field definitions and then edit each citation to separate the pieces out of [CD] into the new fields. Unfortunately, every citation needs to be edited - for some users this may number in the thousands or even tens of thousands. > > I'm hopeful that the RootsMagician will be persuaded to find the resources to automate this parsing and mapping on import. Meanwhile, I am conceiving a SQLite procedure which might be able to do it after import. > > Tom > >> On Sun, Sep 21, 2014 at 9:59 AM, Jim Byram via <tmg-refugees@rootsweb.com> wrote: >> Thanks, Barbara. >> >> Two omissions in the import have been found so far... the place LatLong >> value and the place comments. I've reported those. >> >> The RootsMagic import needs the project and exhibits in their folders. It >> will not import from a TMG .SQZ backup file. >> >> The TMG backup is a ZIP file. If necessary, you can always change the >> filetype to ZIP and drag the project and exhibits folders out of a backup to >> the appropriate locations. >> >> Jim >> >> *** >> To unsubscribe from the list, please send an email to TMG-REFUGEES-request@rootsweb.com with the word 'unsubscribe' without the quotes in the message subject and body. >> ------------------------------- >> To unsubscribe from the list, please send an email to TMG-REFUGEES-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message >

>>>On Monday, 22 September 2014 5:03 AM Tom Holden via <tmg-refugees@rootsweb.com> wrote: >>>..................... >>> - post problem/bug reports at http://support.rootsmagic.com/anonymous_requests/new >>>I'm hopeful that the RootsMagician will be persuaded to find the resources to automate this parsing and mapping on import. >>> Meanwhile, I am conceiving a SQLite procedure which might be able to do it after import. Tom ---------------------------------------------------------------------------- ------- Great idea Tom, but I'm not hopeful they will invest that sort of effort - it might be a step too far for existing RM users to assimilate as well. But I've reported a couple of bugs and issues with the import to the link you gave - will see what happens. Nobody else seems to have noticed that the import process makes no attempt to handle Citation Sureties, even though some sort of mapping to RM 'Proof' should have been possible? OK, it only has 3 categories, but they could at least try.... As far as I'm concerned, the current RM sentence import process creates so much rubbish and drops so much detail that it is totally unusable. And even if they fixed that (a major task) I still see RM's poor media handling, dreadful charting and reports, lack of Flags as total show-stoppers - it will never be a viable transfer product for me without major development. Don Ferguson