Summary: | backup on dvd (and maybe sync with dvd-ram?) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Dennis Gnad <bluedrago> |
Component: | Plugin-Generic-WishForNewTools | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | anaselli, caulier.gilles |
Priority: | NOR | ||
Version: | 0.7.4 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dennis Gnad
2005-10-02 14:48:16 UTC
why not use backup software that is meant for this job? e.g. kdar - I doubt digikam should solve _every_ problem around images I think that the basic feature of having the ability to index a dvd for searching and thumbnail viewing from inside digikam will be awesome. I think it's something that should be offered by photos management solution. Indexing of offline media and search capabilities from within digikam would really be a killer feature! Does anybody else offer that? Moreover, since DVDs are not much more reliable than hdds, it would be great if digikam could keep a track of several backups on several distinct mediums. In addition to the star rating sytem, you could have an "image healthiness" indicator that is simply the number of copies on different mediums, each copy decreasing the risk of loss... *** This bug has been confirmed by popular vote. *** Probably another candidate that would be fixed if I managed to get round to implementing bug #143978 I think digikam is a great photo manager, but the use of big SLRs (several MP) makes that every album of i.e. 50 photos a size about 100Mb, more or less. The fact that digikam stores all the photos in HD makes impossible to manage large quantity of photos (I'm talking about thousands of family photos). I think that a good wished could be the possibility of create a database of created DVDs or other media, just an indexation of filenames, tags, and thumbs... Only a cataloguer, without the viewer possibility. *** This bug has been marked as a duplicate of bug 224312 *** |