---- Reported by shotwell-maint@gnome.bugs 2010-11-10 09:36:00 -0800 ----

Original Redmine bug id: 2797
Original URL: http://redmine.yorba.org/issues/2797
Searchable id: yorba-bug-2797
Original author: bejan -
Original description:

Is it possible to set up an automatic tagging system so when you publish a
photo it will be tagged as such? Better yet if Shotwell could recognize when
publishing if a duplicate is already been published. I think in todays age
with so many cameras and pictures to be stored it would be immensely helpful.

Thank you for your work

Related issues:
duplicated by shotwell - 4329: Uploading to Picasa doesn't care about
already uploaded i... (Duplicate)



---- Additional Comments From shotwell-maint@gnome.bugs 2012-03-26 16:57:00 -0700 ----

### History

####

#1

Updated by Clinton Rogers over 2 years ago

  * **Tracker** changed from _Bug_ to _Feature_

A user from the mailing list had a similar idea, but along with duplicate
publishing prevention, he wanted to be able to see which services a photograph
had been published to and on what date, and for all that to be searchable.
Because tags are searchable, simply encoding all that into a tag seems like it
would satisfy both requests.

####

#2

Updated by Mateusz Loskot over 2 years ago

On the ml, I proposed some additional ideas related this enhancement:

[Persist information about photo
publishing](http://lists.yorba.org/pipermail/shotwell/2011-April/002123.html)

####

#3

Updated by Adam Dingle over 2 years ago

  * **Subject** changed from _Automatic tagging or duplicate protection when publishing photos_ to _Remember which photos have been published to which services_

####

#4

Updated by Adam Dingle over 2 years ago

Briefly, Mateusz's suggestion on the mailing list was that if Shotwell
remembered which photos have been published where, it could let the user
search for photos which had or had not been published to different services. I
agree this could be useful.

####

#5

Updated by Adam Dingle about 2 years ago

  * **Description** updated (diff)
  * **Priority** changed from _Low_ to _Normal_

####

#6

Updated by Adam Dingle about 2 years ago

  * **Priority** changed from _Normal_ to _High_

####

#7

Updated by Raienr Krug about 2 years ago

One additional ide to keep in mind when implementing this:

- "offline publishing" feature: instead of actual publishing, the picture would be tagged and at the next sync, upladed.

- for services which allow this, to have a "sync" feature: images with the "published to the album X at service Y" tag but not published yet will be published, and pictures on Y but not local will be downloaded and tagged accordingly. This would make it possible to consolidate pictures published from different sources.

####

#8

Updated by Adam Dingle about 2 years ago

Raienr, thanks for the suggestion. We actually have a separate ticket for
syncing bidirectionally to publishing destinations: that's #2676.

####

#9

Updated by Adam Dingle over 1 year ago

Also requested downstream at
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/965683 .



--- Bug imported by chaz@yorba.org 2013-11-25 21:48 UTC  ---

This bug was previously known as _bug_ 2797 at http://redmine.yorba.org/show_bug.cgi?id=2797

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product shotwell. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product shotwell. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution