I think this is a Flickr issue, not PSU, but perhaps someone here will have a suggestion.
Within PSU I have created a Flickr portfolio. Within that portfolio I have created a collection of a couple hundred family history photos. These photos often contain groups of people whose names have been added to the IPTC extension field "Person in the Image".
After uploading the Flickr portfolio I visit my online Flickr account. When I view the image and click on the "Show EXIF" button, only one name displays per image (it seems to be the first in the list of names for that image's metadata field).
I want a person viewing the image on Flickr to be able to see the entire list of names.
Are there any suggestions as to how achieve my goal using Flickr and PSU's portfolio capability? If not with Flickr, are there any other online services that might work?
- David P
Flickr, concerning person in image tag - shows only one name out of many
Re: Flickr, concerning person in image tag - shows only one name out of many
I havent tried this, but just something that pops to mind... Try to add areas in PSU for the faces and then upload them to Flickr. Does that make a difference? Could be that flickers reads these areas but not the people tag.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Flickr, concerning person in image tag - shows only one name out of many
Thank you for the suggestion, Hert. I did try it, but unfortunately it did not resolve the problem.
It would certainly be helpful if the other developers followed standards as rigorously as you do.
- David P
It would certainly be helpful if the other developers followed standards as rigorously as you do.
- David P
Re: Flickr, concerning person in image tag - shows only one name out of many
Maybe you could write the names as plain keywords?
Re: Flickr, concerning person in image tag - shows only one name out of many
Vlad, your suggestion would likely work, but in general I try to limit my use of people's names as keywords for a couple of reasons:
1. Years ago my daughter noticed that on Google/Bing searches, her name would occasionally show up linked to online photographs of her. The connection seemed to trace back to the use of her name as a keyword. That exposure seemed like a really bad idea.
2. As a computer guy from way back, I realized the hard way that having the same data in multiple places can cause a lot of problems (I'm not referring to multiple data backups, by the way). Occasionally I would change the data in one place, but not the other. This would lead problems with inconsistent data and it was a lot of tedious work to make things right. Therefore if there is one standardized field to use for a specific purpose (i.e. "Person in the Image"), I'll choose that field as opposed to a general purpose field.
For my current need (making available to my cousins semi-historical photos of relatives), Vlad's solution might be a reasonable solution. To not pollute my no-names-as-keywords PSU database policy, it seems like I would need the ability in batch to create keywords from an XMP field array. As far as I know, that capability is not currently available in PSU.
My quick and dirty, so-so solution is to upload the images with all metadata to OneDrive, send the album sharing link to my cousins, and provide them with instructions for using "Jeffrey's Image Metadata Viewer" ( http://regex.info/exif.cgi/exif.cgi ) to reveal the "Person in the Image" array.
Thank you, Vlad.
- David Paine
1. Years ago my daughter noticed that on Google/Bing searches, her name would occasionally show up linked to online photographs of her. The connection seemed to trace back to the use of her name as a keyword. That exposure seemed like a really bad idea.
2. As a computer guy from way back, I realized the hard way that having the same data in multiple places can cause a lot of problems (I'm not referring to multiple data backups, by the way). Occasionally I would change the data in one place, but not the other. This would lead problems with inconsistent data and it was a lot of tedious work to make things right. Therefore if there is one standardized field to use for a specific purpose (i.e. "Person in the Image"), I'll choose that field as opposed to a general purpose field.
For my current need (making available to my cousins semi-historical photos of relatives), Vlad's solution might be a reasonable solution. To not pollute my no-names-as-keywords PSU database policy, it seems like I would need the ability in batch to create keywords from an XMP field array. As far as I know, that capability is not currently available in PSU.
My quick and dirty, so-so solution is to upload the images with all metadata to OneDrive, send the album sharing link to my cousins, and provide them with instructions for using "Jeffrey's Image Metadata Viewer" ( http://regex.info/exif.cgi/exif.cgi ) to reveal the "Person in the Image" array.
Thank you, Vlad.
- David Paine