Jump to content


Photo

RM4's New GEDCOM Export Format Causes Problems


  • Please log in to reply
17 replies to this topic

#1 pjmpjm

pjmpjm

    Member

  • Members
  • PipPip
  • 13 posts

Posted 30 March 2009 - 01:03 AM

I didn't get any response from my earlier message, so thought I'd simplify my question and try again.

RM4 seems to export GEDCOMs in a different format from RM3.

Can anyone explain exactly what has changed?

I can't upload my GEDCOMs to my online database without showing scrambled information and the notation "PLACE" showing up everywhere!

So, with much regret, I've had to revert back to RM3.

Feedback from the GEDCOM experts will be very much appreciated . . .

Thanks!

Patrick

#2 welsh793

welsh793

    Member

  • Members
  • PipPip
  • 9 posts

Posted 31 March 2009 - 10:19 AM

QUOTE(pjmpjm @ Mar 30 2009, 12:03 AM) View Post

I didn't get any response from my earlier message, so thought I'd simplify my question and try again.

RM4 seems to export GEDCOMs in a different format from RM3.

Can anyone explain exactly what has changed?

I can't upload my GEDCOMs to my online database without showing scrambled information and the notation "PLACE" showing up everywhere!

So, with much regret, I've had to revert back to RM3.

Feedback from the GEDCOM experts will be very much appreciated . . .

Thanks!

Patrick



Sorry I can't help in why but I have the same idea that maybe it is too soon to start using RM4. I have gone back to RM3 at least until more bugs have been erased.

#3 Romer

Romer

    Advanced Member

  • Members
  • PipPipPip
  • 2056 posts

Posted 31 March 2009 - 10:32 AM

QUOTE(pjmpjm @ Mar 30 2009, 02:03 AM) View Post

I can't upload my GEDCOMs to my online database without showing scrambled information and the notation "PLACE" showing up everywhere!


What application are you using to import your GEDCOM into your online database? With all the added functionality in RM4, the GEDCOM export would undoubtedly be different and more varied than under RM3, as you mention. As a result, it sounds as though another possibility could be with the online application's ability to handle any new or altered GEDCOM tagging.

In looking at several of these problem entries, are you seeing the same problems in the GEDCOM export file that you're also encountering once you bring it your online database? Are there any additional problem details that you can relate to help someone in determining what the explanation to what you're seeing might be?

#4 kbens0n

kbens0n

    Advanced Member

  • Members
  • PipPipPip
  • 3444 posts

Posted 31 March 2009 - 11:15 AM

QUOTE(pjmpjm @ Mar 30 2009, 03:03 AM) View Post
I can't upload my GEDCOMs to my online database without showing scrambled information and the notation "PLACE" showing up everywhere!

This thread will be helpful if you are referring to Ancestry.com or RootsWeb WorldConnect:
http://archiver.root...9-03/1238434827

---
--- "GENEALOGY, n. An account of one's descent from an ancestor who did not particularly care to trace his own." - Ambrose Bierce
--- "The trouble ain't what people don't know, it's what they know that ain't so." - Josh Billings
---Ô¿Ô---
K e V i N


#5 pjmpjm

pjmpjm

    Member

  • Members
  • PipPip
  • 13 posts

Posted 31 March 2009 - 05:30 PM

Hi Romer

Thanks very much for your reply.

You've hit the nail right on the head. Several of us are trying -- by trial and error -- to work out what new, additional information is being exported in RM4 GEDCOMs.

When we establish this, we can 'strip out' those parameters, those GEDCOM tags, and create a GEDCOM that's identical to RM3's export.

The uploading software is RootsWeb's own built-in upload facilty, which has a function (line 32 in the 'old' upload program) that allows manual removal of any specific GEDCOM tags in the upload process.

So far, I've been able to solve all the weird display problems except for the display of my sources. I can't get them to display at all, really.

The GEDCOM parameters in question are: _UID,_SDATE,_COLOR,_TMPLT,FIELD,VALUE

and possibly also _BIBL and _SUBQ -- I'm still experimenting. There may be more.

More feedback appreciated!

Best wishes

Patrick

QUOTE(Romer @ Apr 1 2009, 03:32 AM) View Post


What application are you using to import your GEDCOM into your online database? With all the added functionality in RM4, the GEDCOM export would undoubtedly be different and more varied than under RM3, as you mention. As a result, it sounds as though another possibility could be with the online application's ability to handle any new or altered GEDCOM tagging.

In looking at several of these problem entries, are you seeing the same problems in the GEDCOM export file that you're also encountering once you bring it your online database? Are there any additional problem details that you can relate to help someone in determining what the explanation to what you're seeing might be?



Hi kbensOn

Thanks very much for your reply.

Yes, I'm participating in the RootsMagic-Users newsgroup at RootsWeb and receiving help there.

More feedback from GEDCOM experts will be appreciated.

I especially need to know what GEDCOM parameters might be interfering in the display of my sources.

Best wishes

Patrick

patrick@mpx.com.au


QUOTE(kbens0n @ Apr 1 2009, 04:15 AM) View Post

This thread will be helpful if you are referring to Ancestry.com or RootsWeb WorldConnect:
http://archiver.root...9-03/1238434827



#6 Romer

Romer

    Advanced Member

  • Members
  • PipPipPip
  • 2056 posts

Posted 31 March 2009 - 05:51 PM

Patrick,

I've certainly heard of the RootsWeb upload application, but have never used it, myself. Hopefully, enough people here on the boards work with it to allow people approaching the problem from different directions to come to a resolution through further collaboration. I wish you luck!

By the way, do you know if the developer of the app or anyone now associated with maintaining it receives questions and feedback? If so, you can certainly try to attack the issue from that angle, as well.

#7 Romer

Romer

    Advanced Member

  • Members
  • PipPipPip
  • 2056 posts

Posted 31 March 2009 - 10:49 PM

It looks as though RM 4.0.1.1 resolved any issues:

http://www.rootsmagi...?showtopic=6255

#8 yallcome

yallcome

    Advanced Member

  • Members
  • PipPipPip
  • 31 posts

Posted 07 April 2009 - 11:45 PM

Nope -- issues not resolved with update. Still having spouse problems (haha) and source problems with uploads to Rootsweb.



QUOTE(Romer @ Apr 1 2009, 05:49 AM) View Post

It looks as though RM 4.0.1.1 resolved any issues:

http://www.rootsmagi...?showtopic=6255



#9 pjmpjm

pjmpjm

    Member

  • Members
  • PipPip
  • 13 posts

Posted 08 April 2009 - 04:14 AM

I've been working with the RM4 GEDCOM export process for some days now, but still haven't found a fool-proof way to get all my sources to display properly when uploading my GEDCOM to RootsWeb. Others have reported similar problems. It may be that Bruce and the RM team are working on this one.

Patrick

patrick@mpx.com.au


QUOTE(yallcome @ Apr 8 2009, 04:45 PM) View Post

Nope -- issues not resolved with update. Still having spouse problems (haha) and source problems with uploads to Rootsweb.



#10 BarryBoyer

BarryBoyer

    Member

  • Members
  • PipPip
  • 20 posts

Posted 08 April 2009 - 05:57 PM

Is this the sort of problems folks are seeing?

Birth: 3 AUG 1900 in Oregon, USA
_TMPLT:
FIELD:
Name: Page 1
Census: 1910
_SDATE: 1 JUL 1910 Buena Vista, Polk Co., Oregon, USA
_TMPLT:
FIELD:
Name: Page
VALUE: Ancestry.com image 3 of 10 (October 2006) - District 238 2
Census: 1930
_SDATE: 1 JUL 1930 Chepalis, Grays Harbor Co., Washington, USA
_TMPLT:
FIELD:
Name: Page
VALUE: Chepalis, Grays Harbor, Washington; Roll: 2488; Page: 5B; Enumeration District: 20

The above is part of my database on RootsWeb's WorldConnect

#11 pjmpjm

pjmpjm

    Member

  • Members
  • PipPip
  • 13 posts

Posted 09 April 2009 - 05:58 AM

Hi Barry

You'll need to strip the following GEDCOM tags when you upload to RootsWeb:

_BIBL _COLOR _SDATE _SUBQ _TMPLT _UID

This can be done on line 32 of the 'old' upload system.

Let me know if you need more details about how to to this.

However, it probably won't solve the whole problem of the proper display of sources.

Patrick

patrick@mpx.com.au


QUOTE(BarryBoyer @ Apr 9 2009, 10:57 AM) View Post

Is this the sort of problems folks are seeing?

Birth: 3 AUG 1900 in Oregon, USA
_TMPLT:
FIELD:
Name: Page 1
Census: 1910
_SDATE: 1 JUL 1910 Buena Vista, Polk Co., Oregon, USA
_TMPLT:
FIELD:
Name: Page
VALUE: Ancestry.com image 3 of 10 (October 2006) - District 238 2
Census: 1930
_SDATE: 1 JUL 1930 Chepalis, Grays Harbor Co., Washington, USA
_TMPLT:
FIELD:
Name: Page
VALUE: Chepalis, Grays Harbor, Washington; Roll: 2488; Page: 5B; Enumeration District: 20

The above is part of my database on RootsWeb's WorldConnect



#12 yallcome

yallcome

    Advanced Member

  • Members
  • PipPipPip
  • 31 posts

Posted 09 April 2009 - 06:07 AM

Hi guys --

Just had a note from Bruce when I got home. He suggested I export my RM4 data to a GEDCOM, then re-import it into RM4 to see how it looked. It looked fine. So I went ahead and re-exported the new RM4 data to a GEDCOM and uploaded it to RootsWeb (the new way, not stripping anything) and it took and looks fine. Sources, Spouses, and all.

Don't know what that did, other than possibly do a final scouring on the data that came over originally from RM3, but hey, it worked.

to a file
QUOTE(pjmpjm @ Apr 9 2009, 12:58 PM) View Post

Hi Barry

You'll need to strip the following GEDCOM tags when you upload to RootsWeb:

_BIBL _COLOR _SDATE _SUBQ _TMPLT _UID

This can be done on line 32 of the 'old' upload system.

Let me know if you need more details about how to to this.

However, it probably won't solve the whole problem of the proper display of sources.

Patrick

patrick@mpx.com.au



#13 BarryBoyer

BarryBoyer

    Member

  • Members
  • PipPip
  • 20 posts

Posted 10 April 2009 - 06:51 PM

Thanks, I would like to know how to 'improve' the export. Perhaps the rest of the fix will come soon?

#14 pjmpjm

pjmpjm

    Member

  • Members
  • PipPip
  • 13 posts

Posted 10 April 2009 - 11:14 PM

Hi Yallcome

I wrote to you directly but realised that it would be better to repeat my report here, for others to see.

So far, I can't replicate your interesting experiment, which was:

1. You exported a RM4 GEDCOM, then reimported it into RM4 as a brand new database.

2. Then you exported the resulting new RM4 database as yet another new GEDCOM.

3. Finally, you uploaded this newest GEDCOM successfully to RootsMagic, without display or source problems, and without having to strip any GEDCOM tags.

My own experience was unfortunately quite different. The 'doubly-created' or 'filtered' RM4 GEDCOM I uploaded to RootsMagic, both without stripping tags (same distastrous display) and with stripping tags (same problem in displaying sources and many 'fatal error level' reports when at least three digits follow a CONT tag in the GEDCOM) didn't seem to make any difference at all.

I tried this experiment with RM4 databases that were creating both by direct import of the RM3 database into RM4 -- and by importing a RM3 GEDCOM into RM4. Same problems resulted in both cases.

Another experiment not yet tried by myself -- exporting a RM4 GEDCOM and importing it into a new RM3 database, then exporting a RM3 GEDCOM, and then finally uploading the resulting GEDCOM to RootsMagic.

If this latter method worked, it would allow me to keep using RM4 as my primary genealogy database, and still maintain my RootsWeb site. However, it would involve some extra trouble and I'd have to see if it's worth it.

For the present, I've reverted to using RM3.

For the record, in case it matters, my RM database is just over 59,000 individuals in size, with some 3500 sources.

Hope this helps keep others up-to-date on the RM4 GEDCOM export situation.

Patrick

patrick@mpx.com.au


QUOTE(yallcome @ Apr 9 2009, 11:07 PM) View Post

Hi guys --

Just had a note from Bruce when I got home. He suggested I export my RM4 data to a GEDCOM, then re-import it into RM4 to see how it looked. It looked fine. So I went ahead and re-exported the new RM4 data to a GEDCOM and uploaded it to RootsWeb (the new way, not stripping anything) and it took and looks fine. Sources, Spouses, and all.

Don't know what that did, other than possibly do a final scouring on the data that came over originally from RM3, but hey, it worked.

to a file



Hi Barry

It might be worth your while trying Yallcome's 'double GEDCOM export' experiment that I just outlined.

And it won't hurt to strip the _BIBL _COLOR _SDATE _SUBQ _TMPLT _UID tags when you upload to RootsMagic, just to be sure.

I'd be interested to hear if anyone else can successfully 'scour' or 'filter' a RM4 GEDCOM in this way.

I'm going to try it a 3rd time later this weekend, in case I've done something wrong.

Please write again if you have success -- or even if you don't!

Good luck!

Patrick

patrick@mpx.com.au


QUOTE(BarryBoyer @ Apr 9 2009, 10:57 AM) View Post

Is this the sort of problems folks are seeing?

Birth: 3 AUG 1900 in Oregon, USA
_TMPLT:
FIELD:
Name: Page 1
Census: 1910
_SDATE: 1 JUL 1910 Buena Vista, Polk Co., Oregon, USA
_TMPLT:
FIELD:
Name: Page
VALUE: Ancestry.com image 3 of 10 (October 2006) - District 238 2
Census: 1930
_SDATE: 1 JUL 1930 Chepalis, Grays Harbor Co., Washington, USA
_TMPLT:
FIELD:
Name: Page
VALUE: Chepalis, Grays Harbor, Washington; Roll: 2488; Page: 5B; Enumeration District: 20

The above is part of my database on RootsWeb's WorldConnect



#15 Nathanville

Nathanville

    New Member

  • Members
  • Pip
  • 4 posts

Posted 12 April 2009 - 07:33 AM

Yes I had the same problem with GedCom files from RM4, unfortunately be the time I'd discovered the problem I'd already added lots of new information to the RM4 database so I couldn't go back to using RM3 without loosing that data unless I could get the GedCom file back from RM4 to RM3 without data being scrambled when I us RM to create the files for my website.

I tried importing the GedCom file from RM4 to Family Tree Maker (FTM) but it wasn't recognised by FTM as a valid file. But in the end I found that by exporting the GedCom file from RM4 to RM3 then from RM3 to FTM and then back to RM3 it worked with all but a slight loss of data on some of the minor fields. So for now I'm sticking with RM3 as the main database for uploading to my website with copying GedCom files to FTM occasionally because of it's excellent 'Smart' access to the online births/marriages/deaths post 1837 and census records from 1841 to 1901. All long winded but no single genealogy program yet has all the facilities that I use e.g. for a graphical and interactive tree of my family tree I also use the free program DftCom2 from www.dftcom2.co.uk


#16 kbens0n

kbens0n

    Advanced Member

  • Members
  • PipPipPip
  • 3444 posts

Posted 12 April 2009 - 07:56 AM

QUOTE(Nathanville @ Apr 12 2009, 09:33 AM) View Post
I tried importing the GedCom file from RM4 to Family Tree Maker (FTM) but it wasn't recognised by FTM as a valid file.


http://www.rootsmagi...p...ic=6322&hl=

---
--- "GENEALOGY, n. An account of one's descent from an ancestor who did not particularly care to trace his own." - Ambrose Bierce
--- "The trouble ain't what people don't know, it's what they know that ain't so." - Josh Billings
---Ô¿Ô---
K e V i N


#17 yallcome

yallcome

    Advanced Member

  • Members
  • PipPipPip
  • 31 posts

Posted 13 April 2009 - 10:40 AM

Needless to say, while I'm happy I'm up and working on RM4, this is a little worrying.

#18 pjmpjm

pjmpjm

    Member

  • Members
  • PipPip
  • 13 posts

Posted 30 May 2009 - 04:01 AM


QUOTE(kbens0n @ Apr 12 2009, 11:56 PM) View Post


The latest RM4 update seems to have solved the previous GEDCOM export issues with RootsWeb. I've had private confirmation from some of the RM users who regularly upload to RootsWeb online databases that the newest RM4 version now creates a GEDCOM acceptable to RootsWeb. My understanding is that there was nothing at all wrong with RM4's GEDCOMs, but that RootsWeb had special requirements.

I'd be happy to hear from others who have faced this difficulty, especially if any RM4 GEDCOM issues remain.

For myself, I consider this chapter closed. Thanks, Bruce! biggrin.gif

Best wishes

Patrick

patrick@mpx.com.au