Loading Profile...
Store picture metadata before it is uploaded to Flickr.
It would be great if the information entered when preparing an upload was saved locally, and would be remembered when you closed then opened the FlickrExport export window. It's really frustrating to have spent a lot of time preparing an upload to Flickr, then be forced to close then re-open the window, losing everything.
I’m hopeful
1
person likes 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 Matt,
I've chewed over different ways to do this, but the overriding problem is that you're not guaranteed to get the same set of photos in the next export session as you got in the first - because the selection of photos is under the control of the user and FlickrExport can't request photos to be exported that the user hasn't selected.
I'm definitely aware of and sensitive to the issue, though, but I haven't yet found a design that I'm happy makes this problem understandable to most users.
Best,
Fraser1 Comment
Add a comment
This is one of the best points
-
Hi Fraser,
Would a different set of photos really matter? All photos are going to the same place, namely your Flickr account. And they are only exported once, right? So couldn't any metadata entered against a photo be stored, and used repeatedly, almost like a local replication of state on Flickr, but that has not yet been sent to Flickr?
Hope that's clear - I'm not really sure of the terms you used to describe your user experience. -
Inappropriate?It might matter, depending on what the user's expectations are. Even if FlickrExport stored all the exported images and metadata outside of iPhoto before uploading (which it could do), would people be confused if they did further edits on those same images in iPhoto and then restored a previous export to find that "old" versions had been uploaded?
Also, if you ignore the selected exports in favour of ones loaded from disk, you lose any access to those versions in the host application. This is more of a problem for Aperture, where the "add keyword and metadata after upload" features wouldn't be able to work.
I'm definitely keen to increase robustness like this, but I need to find a way to do it that's not confusing and/or limiting.
I’m optimistic
EMPLOYEE
