I'm using 4.1.5 PGV version and I'd like to upgrade to latest version.
I had some errors on media (few photos) and I decided to delete all media before to upgrade and reenter them after upgrade.
Before upgrade, during a GEDCOM check, I found some different errors; can you give me more informations about them?
First error:
In checker I can read as follow
0000001[] missing HEAD:GEDC; see HEAD
0000002[] invalid tag; see HEAD
0000003 1 CHAR UTF8
0000004 1 SOUR PhpGedView
0000005 2 NAME PhpGedView Online Genealogy
0000006 2 VERS 3.3.8 final
0000007 1 DATE 14 Aug 2007
but in GEDCOM downloaded I can see
0 HEAD
1 SOUR PhpGedView
2 NAME PhpGedView Online Genealogy
2 VERS 4.1.5
1 DEST DISKETTE
1 DATE 07 APR 2010
2 TIME 11:17:09
1 GEDC
2 VERS 5.5.1
2 FORM Lineage-Linked
1 CHAR UTF8
Second error:
0002365 1 BURI
0002366[] invalid tag; see INDI @I295@
0002367 2 PLAC New York
Why?
Many other errors like this:
0003501 2 DATE 06 APR 2010
0003502 3 TIME 17:52:31
0003503 2 _PGVU paprita
0003504 0 @M27@ OBJE
0003505[] invalid tag; see OBJE @M27@
0003506[] missing OBJE:FILE:FORM; see OBJE @M27@
0003507[] invalid tag; see OBJE @M27@
0003508 1 _PRIM Y
0003509[] invalid tag; see OBJE @M27@
0003510 1 CHAN
0003511 2 DATE 06 APR 2010
0003512 3 TIME 18:19:15
0003513 2 _PGVU paprita
Please help me, thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understand that all errors are not important and it's a good news.
By the way, in order to have a "clear" GEDCOM file, can I delete lines where media files are not present?
If yes, what I have to do, exactly?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you mean "no errors displayed when checking gedcom", then do not bother. This tool was written for developers, so they can check that PGV is generating data that matches the specification exactly. The errors you mention are not problems.
If you mean that you want to delete media objects from your gedcom, then it is easiest to do this using PhpGedView. You can delete the media objects there. Then, export / download the file to get a new copy, without the media.
If you mean something else, please say!
Greg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you mean that you want to delete media objects from your gedcom, then it is easiest to do this using PhpGedView. You can delete the media objects there. Then, export / download the file to get a new copy, without the media.
This is what I intend; the problem is that on PGV media object are deleted (as a matter of fact I can't see them) but they continue to stay in GEDCOM file …
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PhpGedView doesn't use the GEDCOM file once it's been imported. You can have the program create a new one for you by using the Export function on the Manage GEDCOMs page. The new GEDCOM should not have any of the deleted Media stuff in it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
_PhpGedView doesn't use the GEDCOM file once it's been imported. You can have the program create a new one for you by using the Export function on the Manage GEDCOMs page. The new GEDCOM should not have any of the deleted Media stuff in it. _
This is interesting … now I understand that if I upgrade doesn't matter if GEDCOM file is not perfect … I need it only to change system, passing from PGV to another application … ok, now it's all clear.
Thanks to all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually, when you upgrade PGV to a new version, you are advised to export the database to a GEDCOM using the old program BEFORE you upgrade. You should, just as a safety measure, export your database from time to time even when you're not planning to do an upgrade. You'd do this when you've used PGV to make major changes to your family tree.
Sometimes, you are advised to re-import the GEDCOM as part of the upgrade process. This might be required when the database tables are redefined with new columns.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using 4.1.5 PGV version and I'd like to upgrade to latest version.
I had some errors on media (few photos) and I decided to delete all media before to upgrade and reenter them after upgrade.
Before upgrade, during a GEDCOM check, I found some different errors; can you give me more informations about them?
First error:
In checker I can read as follow
0000001[] missing HEAD:GEDC; see HEAD
0000002[] invalid tag; see HEAD
0000003 1 CHAR UTF8
0000004 1 SOUR PhpGedView
0000005 2 NAME PhpGedView Online Genealogy
0000006 2 VERS 3.3.8 final
0000007 1 DATE 14 Aug 2007
but in GEDCOM downloaded I can see
0 HEAD
1 SOUR PhpGedView
2 NAME PhpGedView Online Genealogy
2 VERS 4.1.5
1 DEST DISKETTE
1 DATE 07 APR 2010
2 TIME 11:17:09
1 GEDC
2 VERS 5.5.1
2 FORM Lineage-Linked
1 CHAR UTF8
Second error:
0002365 1 BURI
0002366[] invalid tag; see INDI @I295@
0002367 2 PLAC New York
Why?
Many other errors like this:
0003501 2 DATE 06 APR 2010
0003502 3 TIME 17:52:31
0003503 2 _PGVU paprita
0003504 0 @M27@ OBJE
0003505[] invalid tag; see OBJE @M27@
0003506[] missing OBJE:FILE:FORM; see OBJE @M27@
0003507[] invalid tag; see OBJE @M27@
0003508 1 _PRIM Y
0003509[] invalid tag; see OBJE @M27@
0003510 1 CHAN
0003511 2 DATE 06 APR 2010
0003512 3 TIME 18:19:15
0003513 2 _PGVU paprita
Please help me, thanks.
Ignore the header errors. They are unimportant PGV will generate a new header.
CEME is available in some versions of the specification but not others. PGV is happy with it. Ignore this error.
There are many variations of the structure of the media record. PGV can cope with pretty much all of them. These are unimportant.
00035051 FORM Fotografia invalid tag;
FORM should be a format (.jpg, .gif, .mp3, etc.)
PGV doesn't use this, so it doesn't matter.
PGV can read and understand almost anything you can generate from any other application.
I understand that all errors are not important and it's a good news.
By the way, in order to have a "clear" GEDCOM file, can I delete lines where media files are not present?
If yes, what I have to do, exactly?
What do you mean by "clear"
If you mean "no errors displayed when checking gedcom", then do not bother. This tool was written for developers, so they can check that PGV is generating data that matches the specification exactly. The errors you mention are not problems.
If you mean that you want to delete media objects from your gedcom, then it is easiest to do this using PhpGedView. You can delete the media objects there. Then, export / download the file to get a new copy, without the media.
If you mean something else, please say!
Greg
If you mean that you want to delete media objects from your gedcom, then it is easiest to do this using PhpGedView. You can delete the media objects there. Then, export / download the file to get a new copy, without the media.
This is what I intend; the problem is that on PGV media object are deleted (as a matter of fact I can't see them) but they continue to stay in GEDCOM file …
PhpGedView doesn't use the GEDCOM file once it's been imported. You can have the program create a new one for you by using the Export function on the Manage GEDCOMs page. The new GEDCOM should not have any of the deleted Media stuff in it.
_PhpGedView doesn't use the GEDCOM file once it's been imported. You can have the program create a new one for you by using the Export function on the Manage GEDCOMs page. The new GEDCOM should not have any of the deleted Media stuff in it. _
This is interesting … now I understand that if I upgrade doesn't matter if GEDCOM file is not perfect … I need it only to change system, passing from PGV to another application … ok, now it's all clear.
Thanks to all.
Actually, when you upgrade PGV to a new version, you are advised to export the database to a GEDCOM using the old program BEFORE you upgrade. You should, just as a safety measure, export your database from time to time even when you're not planning to do an upgrade. You'd do this when you've used PGV to make major changes to your family tree.
Sometimes, you are advised to re-import the GEDCOM as part of the upgrade process. This might be required when the database tables are redefined with new columns.
Ok, very kind of you