* Export Gedcom File new features

[jbtapscott]

Will do Mike

[jbtapscott]

Mike - just to let you know, I eventually got a response from Atilla. This included a Gedcom attachment which he said would resolve the problem - import the Gedcom and the media files (which were still on their servers) would auto attach. Looking at the Gedcom it looks like all they have done is "hardcode" a path (to the FMP servers) where the Media files can be found for each .

0 @M1@ OBJE
1 _URL http://tree.findmypast.com/assetHandler ... 1112C3B3CF
1 FILE http://tree.findmypast.com/assetHandler ... 1112C3B3CF
1 FORM JPG
1 TITL Annis, Norman S - Birth Certificate


I have gone back to him and said (again) that a generic solution is required that would allow me to auto attach several hundred media files.

I suspect it just comes down to nobody knows how to get the auto linking working again!.

[tatewise]

Yes, all he has done is manually perform what the auto link does, which is pointless, because as you say it needs to be generically repeatable.

I never got a call back from Atilla and have been distracted onto other things.

You could try Version 3.2.14 in Export Gedcom File plug-in V3.2.11 (15136) that has a small update for the FMP Zip Media.

[ronk]

You could try Version 3.2.14 in Export Gedcom File plug-in V3.2.11 (15136) that has a small update for the FMP Zip Media.

Mike,
Is there really a v3.2.14? Your link is to v3.2.11. I'm still using v3.2.10. I suspect v3.3 is not far away, but I bet it seems endless the way users keep coming up with more requests for your versatile plugin.

Ron

[tatewise]

The thread Subject mentions V3.2.11 but an attachment therein is V3.2.14.
Yes, V3.3 is not far away but new requests keep postponing it.
If only products would implement Gedcom correctly (either 5.5 or Draft 5.5.1) then it would be so much easier.

[Gary Carson]

When using V 3.2.14 and the TNG export option, the media files all have prefix number to file name. What is the purpose for this number?

[tatewise]

Gary, see plugins:help:export_gedcom_file:the_faq#how_are_the_exported_multimedia_file_names_derived|> How are the exported Multimedia file names derived?.

FH allows Face/Detail Frame parts of images to be defined, but these do not export to other products.
The Plugin effectively crops each part frame out of the image to create exportable media images, and needs the prefix to identify each cropped image distinct from the full image.

You can use (FILE~ABS) Multimedia via Absolute Link Records to retain original Media filenames, but they will all be full images and no part frames.

[Gary Carson]

Not sure what is the difference between full images and part frames. Help me better understand.

[ColeValleyGirl]

Full images are just what it says on the tin.

Frames are where you've marked out a part of an image (say, the face of one out of many people) and associated that with an individual. So if you've got a wedding photograph you can be precise about which individual is which.

[tatewise]

See the FH V6 video in how_to:v4:adding_multimedia|> Adding Photographs and Other Multimedia and also on any Media tab Edit a photo and use Link to Face/Detail and click Help for details, which explains the 'old' feature that has always been in FH.

[Gary Carson]

When I use the TNG Export Mode and use (FILE~ABS) Multimedia via Absolute Link Records to retain original Media filenames, I loose the _PRIM designation. Is there any combination that permits exporting to TNG and retaining Primary Photo designation (_PRIM) and original Media filenames?

[tatewise]

Currently, no there is no such combination - sorry Gary.
But I will have a quick look to see if it easy for me to modify.

Other users appear to be happy with the filename prefixes exported to TNG.
I do not use TNG and rely on their feedback.
I got the impression that the filenames are not very visible, just like in FH where they only appear hidden in Media Records.

[ronk]

Mike,

The media filenames are quite visible in TNG merely by clicking on a the media description hyperlink. I guess '_PRIM' , or LFT's 'Preferred' and TNG's 'default photo' designation is something I've not addressed since I migrated from LFT 1 1/2 years ago. I let the sequence or preference of media determine that since, in my Gedcoms, I believe the first media photo becomes TNG's default photo 'assignment'. The TNG 'default photo' is significant, since it is the image that appears aside the person name at the top of indvidual/person pages. I'm not even sure how _PRIM is set in FH or if it is recognized in TNG's import but something could be tested.

Ron

[tatewise]

Some other users have pointed out that the first Media photo might NOT be the preferred photo displayed for that Individual.
e.g. It could have the Exclude from Diagrams option set that excludes it from both Diagrams and the Focus Window.
So the Plugin only sets _PRIM Y on the first Media item without that option set as explained in Help & Advice.

_PRIM Y is NOT valid in FH and only added on TNG & RMT export by the Plugin.
Similarly, _PROF and _PHOTO are added for other products.
FH uses the order of the Media links, but governed by the Exclude from Diagrams and Exclude from Reports settings.

See earlier postings:
Export Gedcom File - _TYPE (15095)
Export Gedcom File ~ Preferred Media (14125)
V6.2.2 Export GEDCOM error message (14062)
A couple Export Gedcom File questions (12716)

[ronk]

_PRIM Y is NOT valid in FH and only added on TNG & RMT export by the Plugin.

A bit confused by your response, will have to read your numerous references. I don't see any _PRIM added in the TNG export Gedcom, using FILE~Rel media links in the plugin.

[tatewise]

Yes, that is the crux of Gary's comments - they are NOT added in (FILE~ABS/REL) modes.
He wants original filenames (without prefixes) as per those modes , but also wants _PRIM Y tags, which as the Help & Advice says are NOT added in those two modes.

[ronk]

OK, understood. You have referred again to the plugin's Help & Advice, and I looked it over, but, in the File~ABS/REL option, I couldn't find reference to the _PRIM Y being output or not. Sorry, but for my edification, could you point me to that passage? I decided against searching through the help section in fh_lua with its ~8000 lines of code (WOW).

[Gary Carson]

There is an import option for media coming into TNG for the first image associate with a person or family to be the default photo for that person or family. I want to be sure the default photo is the one showing in FH.

[tatewise]

Gary, if you want the first image for a person as shown in FH to also be the default image in TNG, then you need to use a Media option that reproduces the Link to Face part frame, such as (PART/ALL~LMO) or (PART/ALL~ABS). Otherwise, TNG won't display the same part frame image as in FH, but only the full image on which that part frame is based.

Ron, firstly the Help & Advice is not embedded within the Plugin .fh_lua script, but is in plugins:index|> Family Historian Plugins under Plugin Help and Advice for published Plugins. For TNG specific advice you need to look under the Export Gedcom File ~ Output Formats for (TNG) The Next Generation where under Media & Keywords it says:

For each Individual record, the most preferred Media tab item without Exclude from Diagrams set, gains the _PRIM Y tag to identify the primary photo, except for (FILE~REL/ABS) Multimedia via Relative/Absolute Link Records modes.

Yes, it is a large Plugin, although 3,000 lines are my standard library of functions used by many of my Plugins, and 700 lines present the user dialogue of Option tabs. The size to some extent reflects the number of products supported (that continues to grow) and the disparity of Gedcom dialects they employ.

[Gary Carson]

Using version 3.2.14 and (PART/ALL~LMO) or (PART/ALL~ABS) is not available in my Multimedia Conversion Basic options.

[ronk]

For each Individual record, the most preferred Media tab item without Exclude from Diagrams set, gains the _PRIM Y tag to identify the primary photo, except for (FILE~REL/ABS) Multimedia via Relative/Absolute Link Records modes.

Ok, Mike, got it. Kindly forgive me for missing that nested sentence in skimming the plugin's Help and Advice. I did next try doing a text search in the script, but obviously that was not the right place.

[tatewise]

Gary, the Multimedia Conversions mentioned are (PART~LMO) or (ALL~LMO) or (PART~ABS) or (ALL~ABS).
I just contracted them a little.

However, after looking at the Plugin script it was easy to cater for _PRIM Y tag in (FILE~ABS) & (FILE~REL) modes too.
So now those tags, and similar tags for other products, apply to all Multimedia Conversions.

Try the attached Export Gedcom File Plugin ZIP Version 3.2.15 Dated 25 Jul 2017.
[EDIT: Attachment deleted as now updated in Plugin Store.]

[ronk]

Mike,

I too will test Export Gedcom v3.2.15 be on the lookout for how the _PRIM Y tag impacts my TNG default photo procedures. You do realize you're not only advancing Family Historian software through increased flexibility, but the other genealogical software as well with this powerful plugin. I've recently tried out the RM export also, since Roots Magic has the new TreeShare with Ancestry, and I have a member account.

So having used LFT, FTM 2017, RM 7.5 and TNG. But as a PC program, none reach the feature level of FH. Both TNG and FH by far have the most powerful indexing, with partial firstname/lastname/ID searches, as well as maiden/married names.

Thanks!

[ronk]

Mike,

Just to confirm, that ~ \Family Historian Projects\FHtreename\FHtreename.fh_data\Plugin Data\Export Gedcom File.dat contains ALL the settings for the plugin. I do a full project backup, but is that the relevant file to restore if any settings amiss?

Also, aside from the Media (which I backup another way so move to another temp folder before doing the backup and move back after), I find one of the large files in a Project full backup is the cache,...is the cache an integral part and needed for backup?

[tatewise]

Thank you for your help Ron.
Yes, being able to integrate FH, TNG and RootsMagic forms a powerful trio, with FH PC programmability, TNG online, and RM TreeShare with Ancestry.

You have correctly identified the Plugin settings data file.
But the options for TNG and RMT have not changed in V3.2.15, only the way tags are handled.

The Cache folder holds three sets of cached data.
FindMyPastCache.dat is associated with Internet Data Matches for FindMyPast.
MyHeritageCache.dat is associated with Internet Data Matches for MyHeritage.
ThumbCache.dat is the media thumbnails cache.
This last one is the biggy, and does NOT need backing up as it gets rebuilt as needed, and benefits from so doing occasionally.
The first two are worth saving, but only if you use Internet Data Matches in the Focus Window.