Loading Profile...
Allow FlickrExport to make tags from other metadata.
Much like how FlickrExport now automatically fills in the lens information as a tag, it would be nice to be able to have it automatically add tags from any metadata fields that are used in Aperture.
For example, I'd very much like to have tags made from Country, Province, and City metadata fields, as well as custom fields that I've added to Aperture, such as Continent, Publisher, and so on.
For example, I'd very much like to have tags made from Country, Province, and City metadata fields, as well as custom fields that I've added to Aperture, such as Continent, Publisher, and so on.
I’m exuberant.
5
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
-
Inappropriate?Hi Geoff,
This is definitely something I'm thinking about for FlickrExport 4.
Best,
Fraser -
Inappropriate?I just wish Flickr itself paid more attention to EXIF and IPTC metadata and allowed editable mapping onto Flickr's tags. -
Inappropriate?What confuses me, Geoff and Fraser, is why Aperture used to export IPTC City, State, and Country as tags, but doesn't anymore. And why once, when I stopped it in the middle of an export, I found that it had exported the City, State, and Country tags. Why doesn't it just consistently export them?
I’m frustrated
-
Inappropriate?FlickrExport makes an explicit call to force Flickr tags to be what was seen in the FlickrExport UI, and not including the additional tags that Flickr pulls from EXIF/IPTC. This was done because a number of users were disturbed to find additional tags on Flickr that they thought would not be shown because they didn't see it in the FlickrExport UI.
As I see it, there are two solutions to the problem:
1. FlickrExport allows you to pick arbitrary EXIF/IPTC fields to be used for tags and shows everything in the tag field.
or
2. Flickr provides an API call to prevent scanning of IPTC keywords on upload.
Unfortunately, neither of these are workarounds for the state of this feature in 3.0, but I hope that explains it.
EMPLOYEE
