---- Reported by adam@yorba.org 2010-05-24 07:58:00 -0700 ----

Original Redmine bug id: 1963
Original URL: http://redmine.yorba.org/issues/1963
Searchable id: yorba-bug-1963
Original author: Adam Dingle
Original description:

Most people need to back up their photos in some way. It might be nice if
Shotwell could help with this, for example by coping all photos and their
metadata to an external hard drive (either automatically or upon request).

Related issues:
related to shotwell - Feature #3145: Archive Photos (Open)
related to shotwell - Feature #3417: check database consistency (Open)



---- Additional Comments From shotwell-maint@gnome.bugs 2011-03-28 07:50:00 -0700 ----

### History

####

#1

Updated by Kostas - over 3 years ago

The same backup solution as Picasa would be nice:

[http://picasa.google.com/support/bin/answer.py?hl=en&answer=18393](http://pic
asa.google.com/support/bin/answer.py?hl=en&answer=18393)

####

#2

Updated by Jim Nelson about 3 years ago

By metadata, I'm assuming this means all the data in the database, thumbnails,
mimics, etc. -- i.e. that this feature is a full Shotwell backup as well as
backing up the master files themselves. If not, we should open a separate
ticket for this feature.

####

#3

Updated by John Harris almost 3 years ago

  * **Keywords** set to _asset management, backup_

Pros shoot a great number of images. I may shoot several thousand in a month.
This of course consumes quite a bit of disk space, and some house keeping is
in order.

Can we include some asset management to the backup? i.e. files can be moved
offline and still be searchable in the database. The meta data, mimics and
thumbs, and offline drive ID would be retained on the client for search and
retrieval.

Some facility to print an index for each backup might be useful for offline
viewing as well.

####

#4

Updated by Adam Dingle almost 3 years ago

Replying to [comment:5 studiogrynn]:

> Can we include some asset management to the backup? i.e. files can be moved
offline and still be searchable in the database. The meta data, mimics and
thumbs, and offline drive ID would be retained on the client for search and
retrieval.

> Some facility to print an index for each backup might be useful for offline
viewing as well.

See #3145 .

####

#5

Updated by Коренберг Марк over 2 years ago

How backup may be implemented:

teach Shotwell to use, so called, Collections.

it's a folder with images, thumbnails, db and all needed files to work.

Shotwell should be able to open collections. It will be nice if multiple
collections may be opened at same time.

Tree on the left pane may look like:

    
    
    
    L-Collection1
    
    | L-2010
    
    | | L-January
    
    | | L-February
    
    |    …
    
    L-Collection2
    
    | L-1984
    
    | | L-January
    
    | | L-February
    
    |    …
    
    …
    
    

By default, Shotwell should open User's default collection (in his home dir).

Shotwell should be able to make collection from subset of photos (export as
collection)

or directly burn newly created collection to DVD. Also it should recognize
such DVDs and open them instantly when user insert such disk into drive.

So, to backup photos, user should select photos and press “burn to DVD%â€.
Next time, if %(=caps)DVD disk will be opened via Shotwell, it will be shown
as collection. If DVD will be opened in a file browser, user will find his
photos as plain files.

Also, this feature will allow to open foreign collections (suppose multiuser
environment on one computer)

P.S. inspired by iPhoto



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

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

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