Open CCOSTAN opened 11 years ago
We have experimental code for this. It works but the drawback is to get a simple modification we download the entire photo again and reprocess it.
Perhaps that is okay but I'm not sure how well that scales when you are making mass edits along with other users.
It's a valid issue/feature though.
On Saturday, May 11, 2013, Carlo Costanzo wrote:
Not sure how to lay this out so :
Currently when importing in photos, any TAGs stored in the files get imported in (AWESOME!). I have used Picasa to add in tags, then dropped them into the DropBox uploader and Blammo; Imported pictures with Tags. Great!
I've recently pointed Picasa to the OpenPhoto folder structure on Dropbox and took the opportunity to add more tags to the existing pictures (mainly related to the AWESOME facial recognition and some Geo correcting).
Now I need a way to have Trovebox rescan those existing pictures for the updated tags and Geo information.. Maybe an admin type rescan? a tag update button? I would think it would be inefficient to automatically trigger but an admin forced rescan seems reasonable no?
Probably slightly similar to #680https://github.com/photo/frontend/issues/680but different in it's own way.
Hopefully that made sense.
CARLO.
— Reply to this email directly or view it on GitHubhttps://github.com/photo/frontend/issues/1259 .
-- Snet form my mobl phoone
@jmathai I'd love to help test it out on the hosted side if possible. I have about 20k photos now online and will be going back via Picasa and updating the tags and Geo-Locations on them. (Frankly the Picasa interface is much easier to use at this moment for mass updates). If I could trigger updates across my collection via an admin interface, that would be great.
Does it reprocess the ENTIRE library or just changed files? If it's just changed files I would imagine the scaling issues would be similar to the Upload from Dropbox feature.
CARLO.
Just the modified files. We could be smarter about processing them but if you make 5 rapid updates to the same file and each is tracked by Dropbox we reprocess the photo 5 times :).
We've paused that device but it should still work. I will let you know. Not sure on an eta to enable it but ill have a look.
On Wednesday, May 15, 2013, Carlo Costanzo wrote:
@jmathai https://github.com/jmathai I'd love to help test it out on the hosted side if possible. I have about 20k photos now online and will be going back via Picasa and updating the tags and Geo-Locations on them. (Frankly the Picasa interface is much easier to use at this moment for mass updates). If I could trigger updates across my collection via an admin interface, that would be great.
Does it reprocess the ENTIRE library or just changed files? If it's just changed files I would imagine the scaling issues would be similar to the Upload from Dropbox feature.
CARLO.
— Reply to this email directly or view it on GitHubhttps://github.com/photo/frontend/issues/1259#issuecomment-17946330 .
-- Snet form my mobl phoone
That's only if it is an automatic continuous process though no? If it's a admin button, then presumably, a user would make a bunch of changes (even 5 in a row) and then go to the TroveBox interface and kick off the Reprocess task which would only see the LATEST changed file..
Not sure how to lay this out so :
Currently when importing in photos, any TAGs stored in the files get imported in (AWESOME!). I have used Picasa to add in tags, then dropped them into the DropBox uploader and Blammo; Imported pictures with Tags. Great!
I've recently pointed Picasa to the OpenPhoto folder structure on Dropbox and took the opportunity to add more tags to the existing pictures (mainly related to the AWESOME facial recognition and some Geo correcting).
Now I need a way to have Trovebox rescan those existing pictures for the updated tags and Geo information.. Maybe an admin type rescan? a tag update button? I would think it would be inefficient to automatically trigger but an admin forced rescan seems reasonable no?
Probably slightly similar to https://github.com/photo/frontend/issues/680 but different in it's own way.
Hopefully that made sense.
CARLO.