* Export Gedcom File - _TYPE
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Export Gedcom File - _TYPE
Hi Mike,
I'm running version 3.2 and have noticed the exported gedcom file for TNG no longer appears to be setting the _TYPE for media according to Keywords (DOCUMENT, PHOTO, HEADSTONE, etc.) The option "Media Keywords %d _KEYS:" is set to "Move to Note & _TYPE (TNG)".
I'm not sure if I've missed something.
Thanks,
Ron (Field)
I'm running version 3.2 and have noticed the exported gedcom file for TNG no longer appears to be setting the _TYPE for media according to Keywords (DOCUMENT, PHOTO, HEADSTONE, etc.) The option "Media Keywords %d _KEYS:" is set to "Move to Note & _TYPE (TNG)".
I'm not sure if I've missed something.
Thanks,
Ron (Field)
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
Hi Ron,
It depends on which Multimedia conversion mode you have chosen.
The first three (PART/FULL/ALL~LMO) Part/Full/All Frames via Local Media Objects do NOT honour that _TYPE feature, because I think TNG only supports _TYPE tags in Media Records that are produce by all the other modes, except (WIPE~ALL).
Having checked the Help & Advice for the plugins:help:export_gedcom_file:tng_the_next_generation|> Export Gedcom File ~ (TNG) The Next Generation it does not mention that exception, so I will update that advice.
Conversely, the _PRIM Y tag to identify the primary photo, is now ONLY applied for the (PART/FULL/ALL~LMO) Part/Full/All Frames via Local Media Objects. That was changed in the upgrade from plugin V3.1 to V3.2 but I am still investigating why that was done. It seems it may be an unwanted side-effect of a change for another product, and if so will be fixed in V3.3.
Can you, or anyone else, confirm whether that _PRIM Y tag is supported by TNG on both local Media Objects and Media record links.
It depends on which Multimedia conversion mode you have chosen.
The first three (PART/FULL/ALL~LMO) Part/Full/All Frames via Local Media Objects do NOT honour that _TYPE feature, because I think TNG only supports _TYPE tags in Media Records that are produce by all the other modes, except (WIPE~ALL).
Having checked the Help & Advice for the plugins:help:export_gedcom_file:tng_the_next_generation|> Export Gedcom File ~ (TNG) The Next Generation it does not mention that exception, so I will update that advice.
Conversely, the _PRIM Y tag to identify the primary photo, is now ONLY applied for the (PART/FULL/ALL~LMO) Part/Full/All Frames via Local Media Objects. That was changed in the upgrade from plugin V3.1 to V3.2 but I am still investigating why that was done. It seems it may be an unwanted side-effect of a change for another product, and if so will be fixed in V3.3.
Can you, or anyone else, confirm whether that _PRIM Y tag is supported by TNG on both local Media Objects and Media record links.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
Hi Mike,
I have found that TNG supports _Type with LMO and ABS and _PRIM Y with LMO and ABS.
Although I have always used ALL~LMO which previously had _TYPE and _PRIM Y tags.
Here's an example from a previous version of "Export Gedcom File".
Here's an example of an ABS _PRIM Y OBJE in an INDI record which works with TNG.
The ABS OBJE format you're currently using imports into TNG fine just no primary images (which you mentioned).
Thanks,
Ron
I have found that TNG supports _Type with LMO and ABS and _PRIM Y with LMO and ABS.
Although I have always used ALL~LMO which previously had _TYPE and _PRIM Y tags.
Here's an example from a previous version of "Export Gedcom File".
Code: Select all
1 OBJE
2 _PRIM Y
2 FORM jpeg
2 TITL Ron Field
2 FILE C:\Users\xxx\Desktop\Exports\TNG Web\0O1 Field Ron HD.jpg
2 _TYPE PHOTOS
2 NOTE Picture Note: Taken at my cousins home in England.
3 CONT Media Date: 3 AUG 2013
3 CONT Keywords: PHOTOSCode: Select all
1 OBJE @M529@
2 _PRIM YThanks,
Ron
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
Thank you Ron, I will endeavour to rectify those issues in V3.3 and post a prototype here to try out.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
Sounds great! Thanks Mike.
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
Try the attached Export Gedcom File Plugin Version 3.2.6 Date 22 Jun 2017 ZIP file [Now Deleted] that must be extracted before importing to FH, because it is larger than FHUG allows .
Use right-click Extract All on the downloaded .zip file to obtain the .fh_lua Plugin file.
This version should add _TYPE tags for upper-case Keywords in all Multimedia conversion modes.
It should add _PRIM Y tags for primary images in all Multimedia conversion modes except (FILE~REL) and (FILE~ABS).
Sorry for the lack of those tags in some modes in some preceding versions.
Use right-click Extract All on the downloaded .zip file to obtain the .fh_lua Plugin file.
This version should add _TYPE tags for upper-case Keywords in all Multimedia conversion modes.
It should add _PRIM Y tags for primary images in all Multimedia conversion modes except (FILE~REL) and (FILE~ABS).
Sorry for the lack of those tags in some modes in some preceding versions.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
Thank you Mike!
I should be able to test today.
Ron
I should be able to test today.
Ron
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
Hi Mike,
It installed fine but I receive the following on startup (of the plugin). Ron
It installed fine but I receive the following on startup (of the plugin). Ron
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
Sorry, minor hiccup, try the attached Export Gedcom File Plugin Version 3.2.6 Date 23 Jun 2017 ZIP file. [Now Deleted]
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
Hi Mike,
I've been doing some testing.
ALL~ABS is currently exporting ABS and LMO media links in the same file (double images on import) _PRIM Y appears to be fine.
ALL~LMO is exporting LMO OBJE links twice (double images on import) and _PRIM Y also appear to be working fine.
Ron
I've been doing some testing.
ALL~ABS is currently exporting ABS and LMO media links in the same file (double images on import) _PRIM Y appears to be fine.
ALL~LMO is exporting LMO OBJE links twice (double images on import) and _PRIM Y also appear to be working fine.
Ron
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
The ALL~*** modes do usually involve pairs of images as explained in plugins:help:export_gedcom_file:output_media_style|> Export Gedcom File ~ Output Media Style because they combine the PART~*** and FULL~*** modes.
BUT ALL~ABS should only produce links to Media Records and not Local Media Objects.
Can you give examples of what you believe is wrong, as I have never seen it produce LMO.
ALL~ABS should only use links such as OBJE @O123@ to one 0 @O123@ OBJE record.
There should NOT be any LMO such as OBJE followed by TITL, FILE, FORM, NOTE tags.
BUT ALL~ABS should only produce links to Media Records and not Local Media Objects.
Can you give examples of what you believe is wrong, as I have never seen it produce LMO.
ALL~ABS should only use links such as OBJE @O123@ to one 0 @O123@ OBJE record.
There should NOT be any LMO such as OBJE followed by TITL, FILE, FORM, NOTE tags.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
Here's an ALL~LMO export. It appears that it's generating parts where there are no parts (PDF file below?) including the additional images. It's not doing it to all the images but there are a lot. I even see some videos and PDF files being exported with a part. Images that actually do have a part are working correctly.
Here's the ALL~ABS export example which has LMO in the individual record.
The ABS 0 OBJE exists at the end of the file as well as the LMO versions.
Ron
Code: Select all
1 EVEN
2 TYPE DNA
2 DATE 28 MAR 2012
2 PLAC Salt Lake City, Salt Lake, Utah, United States
2 ADDR Ancestry.com
2 OBJE
3 TITL Y-DNA Results for Ron Field
3 FILE C:\Users\Ron\Desktop\Exports\TNG Web\1O5 Y-DNA Results Field Ron.pdf
4 FORM pdf
3 _TYPE DOCUMENTS
3 NOTE Media Date: 28 MAR 2012
4 CONT Keywords: DOCUMENTS
2 OBJE
3 TITL Y-DNA Results for Ron Field
3 FILE C:\Users\Ron\Desktop\Exports\TNG Web\0O5 Y-DNA Results Field Ron.pdf
4 FORM pdf
3 _TYPE DOCUMENTS
3 NOTE Media Date: 28 MAR 2012
4 CONT Keywords: DOCUMENTSCode: Select all
1 OBJE @O4153@
2 _PRIM Y
1 OBJE @O1@
1 OBJE @O2@
1 OBJE @O4154@
1 OBJE @O3@
1 OBJE @O4@
1 OBJE @O4155@
1 OBJE @O3639@
1 OBJE @O4156@
1 OBJE @O3537@
1 OBJE @O4157@
1 OBJE @O3945@
1 _FLGS
2 __LIVING Living
1 CHAN
2 DATE 24 MAR 2017
3 TIME 11:14:17
0 @O4152@ OBJE
1 FILE C:\Users\Ron\Desktop\Exports\TNG Web\1O5 Y-DNA Results Field Ron.pdf.pdf
2 TITL Y-DNA Results for Ron Field
2 FORM pdf
1 _TYPE DOCUMENTS
1 NOTE Media Date: 28 MAR 2012
2 CONT Keywords: DOCUMENTS
0 @O4153@ OBJE
1 FILE C:\Users\Ron\Desktop\Exports\TNG Web\1O1 Field Ron HD.jpg
2 TITL Ron Field
2 FORM jpg
1 _TYPE PHOTOS
1 NOTE Picture Note: Taken at my cousins home in England.
2 CONT Media Date: 3 AUG 2013
2 CONT Keywords: PHOTOS
0 @O4154@ OBJE
1 FILE C:\Users\Ron\Desktop\Exports\TNG Web\1O3 cousins.jpg
2 TITL Sarah Ron and Katie
2 FORM jpg
1 _TYPE PHOTOS
1 NOTE Caption Note: Ron Field
2 CONT Media Date: 1998
2 CONT Keywords: PHOTOS
0 @O4155@ OBJE
1 FILE C:\Users\Ron\Desktop\Exports\TNG Web\1O3639 16931076651_415b4744b5_o.jpg
2 TITL Ron Field
2 FORM jpg
1 _TYPE PHOTOS
1 NOTE Caption Note: Ron Field
2 CONT Media Date: 1980
2 CONT Keywords: PHOTOS
0 @O4156@ OBJE
1 FILE C:\Users\Ron\Desktop\Exports\TNG Web\1O3537 Ron Field 1974.jpg
2 TITL Ron Field
2 FORM jpg
1 _TYPE PHOTOS
1 NOTE Caption Note: Ron Field
2 CONT Media Date: 9 AUG 1974
2 CONT Keywords: PHOTOS
0 @O4157@ OBJE
1 FILE C:\Users\Ron\Desktop\Exports\TNG Web\1O3945 Ron1975.jpg
2 TITL Ron Field
2 FORM jpg
1 _TYPE PHOTOS
1 NOTE Caption Note: Ron Field
2 CONT Media Date: 1 JUL 1975
2 CONT Keywords: PHOTOSRon
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
You are correct, the ALL~LMO example shows essentially the same PDF file being exported twice.
It should not do that, since there is neither a Face/Detail frame nor a Link/Note caption.
I will investigate why that is happening and try to rectify.
It looks like the problem probably only affects non-image files such as PDF and videos.
The ALL~ABS example is perfectly correct.
It only uses 1 OBJE @O123@ links to 0 @O123@ OBJE records.
There are no Local Media Objects such as shown in your first example.
What you probably don't realise is that Gedcom records of any type can appear in any order anywhere.
Every time a tag has a level 0 digit prefix, that signifies the start of a new record.
Your example shows the end of an Individual record terminated with CHAN, DATE, TIME tags.
Then there are 6 Media records each starting with 0 @O415*@ OBJE which are the part Face/Detail frames.
The full frame matching pair for each of these will be Media records near the end of the Gedcom.
So for example 1 OBJE @O4154@ links to the nearby part frame Media record for 1O3 cousins.jpg file, and 1 OBJE @O3@ links to the matching original full frame Media record for 0O3 cousins.jpg file near the end.
It should not do that, since there is neither a Face/Detail frame nor a Link/Note caption.
I will investigate why that is happening and try to rectify.
It looks like the problem probably only affects non-image files such as PDF and videos.
The ALL~ABS example is perfectly correct.
It only uses 1 OBJE @O123@ links to 0 @O123@ OBJE records.
There are no Local Media Objects such as shown in your first example.
What you probably don't realise is that Gedcom records of any type can appear in any order anywhere.
Every time a tag has a level 0 digit prefix, that signifies the start of a new record.
Your example shows the end of an Individual record terminated with CHAN, DATE, TIME tags.
Then there are 6 Media records each starting with 0 @O415*@ OBJE which are the part Face/Detail frames.
The full frame matching pair for each of these will be Media records near the end of the Gedcom.
So for example 1 OBJE @O4154@ links to the nearby part frame Media record for 1O3 cousins.jpg file, and 1 OBJE @O3@ links to the matching original full frame Media record for 0O3 cousins.jpg file near the end.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
I may have used a bad example for ALL~ABS as I'm seeing the same results of duplicate images for images without regions with ABS and LMO after importing to TNG.
Also its not just video and pdf files. I also see source images, baptism, census etc. being exported as if they have regions when they don't.
Also its not just video and pdf files. I also see source images, baptism, census etc. being exported as if they have regions when they don't.
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
Sorry Ron, you are absolutely correct.
I thought I had tested that feature to ensure such duplicates did not occur, but must have slipped through somehow.
Try the attached Export Gedcom File Plugin Version 3.2.7 Date 24 Jun 2017 ZIP file. [Now Deleted]
I thought I had tested that feature to ensure such duplicates did not occur, but must have slipped through somehow.
Try the attached Export Gedcom File Plugin Version 3.2.7 Date 24 Jun 2017 ZIP file. [Now Deleted]
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
rfield
- Diamond
- Posts: 63
- Joined: 25 Jun 2015 18:41
- Family Historian: V7
- Location: Winnipeg, Canada
- Contact:
Re: Export Gedcom File - _TYPE
Hi Mike,
I've been testing ALL~ABS and ALL~LMO and looks good. _TYPE and _PRIM Y are working great in both modes and I don't see any doubles.
I'll continue to do some checking to make sure I don't find anything odd.
Thank you very much!
Ron
I've been testing ALL~ABS and ALL~LMO and looks good. _TYPE and _PRIM Y are working great in both modes and I don't see any doubles.
I'll continue to do some checking to make sure I don't find anything odd.
Thank you very much!
Ron
Re: Export Gedcom File - _TYPE
Mike,
Came upon this thread while browsing. Should I be even concerned with v3.2.7, or wait for v3.3 if using currently using FILE~REL with v3.2.4?
Ron
Came upon this thread while browsing. Should I be even concerned with v3.2.7, or wait for v3.3 if using currently using FILE~REL with v3.2.4?
Ron
Ron Krzmarzick~~ FH 7.0.20 TNG 14.0.2 website Roots & Relatives Remembered, Laragon 5.0, Win 11 pro
- tatewise
- Megastar
- Posts: 27087
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File - _TYPE
Ron, could you please checkout the new version in Export Gedcom File with Full v Brief option (15110).
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Export Gedcom File - _TYPE
Mike,
Assuming you meant either Ron, will give it a test and compare outputs to make sure all is unchanged (in my case).
Ron
Assuming you meant either Ron, will give it a test and compare outputs to make sure all is unchanged (in my case).
Ron
Ron Krzmarzick~~ FH 7.0.20 TNG 14.0.2 website Roots & Relatives Remembered, Laragon 5.0, Win 11 pro