I am using Legacy as my local tool, exporting the gedcom (Gedcom 5.5) and then uploading to PGV
The exported GEDCOM contains OBJ-records for pictures.
PGV is set to use 2 levels in Multimedia and the filenames in the OBJ-records are structured to fit a 2-level mediastructure in PGV.
The mediafiles are uploaded to the correct /media/* - directory in PGV.
Uploading GEDCOM using replace old GEDCOM, do not keep medialinks.
If the persons have just one mediaobject in their part of the GEDCOM peopleboxes shows that picture.
If persons have muliple mediaobjects Legacy puts the persons picture as the last of the OBJs in the GEDCOM. OBJs like christening church are placed first. Legacy sets "_PRIM Y" for all picture-objects.
When this is uploaded to PGV the Christening Church picture gets al lower Media-index than Persons picture, and the Church is shown in the peoplebox.
I have changed set the Churc-highlight to "No" and reordered the media, but still people are showed as churches.
If I edit the GEDCOM (before uploading), changing the Churches highlight to "_PRIM N" or putting the persons picture OBJ as the first OBJ, then the correct picture is showed in the people-box.
Is it a bug, a feature - or me missing some details when RTFM
arild
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Legacy isn't using the Media definitions correctly. There should only be one media object identified with the "_PRIM Y" tag. All the rest should NOT have any "_PRIM" tags at all.
Here's how PGV decides what media object to display:
1. Ignore all media object references where the Highlight option is set to "No"
2. Pick the first media object reference where the Highlight option is set to "Yes"
3. If (2) doesn't yield a result, pick the first media object reference
4. if (3) doesn't yield a result, display a gender-specific generic silhouette if the confiuration allows it.
You'll need to look at the GEDCOM record for the person as well as the GEDCOM record for the media object itself. There could be a conflict between the two.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Rules PhpGedView uses to decide which is the highlighted media object
* 1. "Use this image as thumbnail" (_THUM Y). The first object with this setting will be used regardless of the
object's level in the gedcom record.
* 2. "Highlighted image" (_PRIM Y).
The first object with this setting will be used if no _THUM Y exists regardless of level in gedcom record.
* 3. Other. The first level 1 object will be used (provided it doesn't have a _THUM N or _PRIM N setting) if there is not some other object with _THUM Y or _PRIM Y (level 1 objects appear on the media tab on the individual page).
And Then:
Rule #2 reflects the setting of the "highlight" option. This is useful when there are several images and it is desirable to make PGV use a specific one, or when one wants PGV to use an image that's attached to a Fact rather than one attached to the person's record.
I then tried (in PGV) to set the "highlight" off on all MMobjects apart from the persons photo.
- but it did not work :-( PGV seem to make its final decision during the import process.
I have written to Legacy Support and asked them if there is a way to supress the _PRIM-tag.
They initially gave an incorrect yes-answer. The case with them is still open.
May be I have to write a script to process my GEDCOM before I am exporting it to PGV ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That documentation is wrong about the use of the _THUM tag.
The _THUM tag is looked at AFTER PGV has decided which media object should be displayed. It overrides the GEDCOM configuration setting "Use thumbnail" for this media object only.
When the GEDCOM "Use thumbnail" option is set to "no", PGV will always send the full-sized image whenever a page calls for a thumbnail. The browser is then required to adjust to image it receives to fit the box where it is to be displayed. When that option is set to "yes", the browser normally sends the much smaller thumbnail image so that less bandwidth is required. The "_THUM" tag, when set to "Y", forces PGV to always send the full-sized image regardless of the GEDCOM configuration.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using Legacy as my local tool, exporting the gedcom (Gedcom 5.5) and then uploading to PGV
The exported GEDCOM contains OBJ-records for pictures.
PGV is set to use 2 levels in Multimedia and the filenames in the OBJ-records are structured to fit a 2-level mediastructure in PGV.
The mediafiles are uploaded to the correct /media/* - directory in PGV.
Uploading GEDCOM using replace old GEDCOM, do not keep medialinks.
If the persons have just one mediaobject in their part of the GEDCOM peopleboxes shows that picture.
If persons have muliple mediaobjects Legacy puts the persons picture as the last of the OBJs in the GEDCOM. OBJs like christening church are placed first. Legacy sets "_PRIM Y" for all picture-objects.
When this is uploaded to PGV the Christening Church picture gets al lower Media-index than Persons picture, and the Church is shown in the peoplebox.
I have changed set the Churc-highlight to "No" and reordered the media, but still people are showed as churches.
If I edit the GEDCOM (before uploading), changing the Churches highlight to "_PRIM N" or putting the persons picture OBJ as the first OBJ, then the correct picture is showed in the people-box.
Is it a bug, a feature - or me missing some details when RTFM
Legacy isn't using the Media definitions correctly. There should only be one media object identified with the "_PRIM Y" tag. All the rest should NOT have any "_PRIM" tags at all.
Here's how PGV decides what media object to display:
1. Ignore all media object references where the Highlight option is set to "No"
2. Pick the first media object reference where the Highlight option is set to "Yes"
3. If (2) doesn't yield a result, pick the first media object reference
4. if (3) doesn't yield a result, display a gender-specific generic silhouette if the confiuration allows it.
You'll need to look at the GEDCOM record for the person as well as the GEDCOM record for the media object itself. There could be a conflict between the two.
In the DOC I found this:
Rules PhpGedView uses to decide which is the highlighted media object
* 1. "Use this image as thumbnail" (_THUM Y). The first object with this setting will be used regardless of the
object's level in the gedcom record.
* 2. "Highlighted image" (_PRIM Y).
The first object with this setting will be used if no _THUM Y exists regardless of level in gedcom record.
* 3. Other. The first level 1 object will be used (provided it doesn't have a _THUM N or _PRIM N setting) if there is not some other object with _THUM Y or _PRIM Y (level 1 objects appear on the media tab on the individual page).
And Then:
Rule #2 reflects the setting of the "highlight" option. This is useful when there are several images and it is desirable to make PGV use a specific one, or when one wants PGV to use an image that's attached to a Fact rather than one attached to the person's record.
- but it did not work :-( PGV seem to make its final decision during the import process.
I have written to Legacy Support and asked them if there is a way to supress the _PRIM-tag.
They initially gave an incorrect yes-answer. The case with them is still open.
May be I have to write a script to process my GEDCOM before I am exporting it to PGV ;-)
That documentation is wrong about the use of the _THUM tag.
The _THUM tag is looked at AFTER PGV has decided which media object should be displayed. It overrides the GEDCOM configuration setting "Use thumbnail" for this media object only.
When the GEDCOM "Use thumbnail" option is set to "no", PGV will always send the full-sized image whenever a page calls for a thumbnail. The browser is then required to adjust to image it receives to fit the box where it is to be displayed. When that option is set to "yes", the browser normally sends the much smaller thumbnail image so that less bandwidth is required. The "_THUM" tag, when set to "Y", forces PGV to always send the full-sized image regardless of the GEDCOM configuration.