[digiKam-users] how to move collections

[frederic chaume]

Hi Gilles

thanks for reply

I have started the migration process, so I moved the collections one by 
one, then I updated the path using the refresh button in the DK 
configuration, BUT the collection didn't come back in the album view in 
the left sidebar (I wait all the processes were completed) . I had to 
restart DK to see them back. Is that normal ? I still have several to 
move , so let me know how to proceed , I can do it now.

Also I would like to move the DB in another disk (SSD one), I see a 
button for DB migration, any advice before starting it ?


regards

Frederic


Le 26/01/2022 à 22:32, Gilles Caulier a écrit :
>
>
> Le mer. 26 janv. 2022 à 09:30, frederic chaume 
> <frederic.chaume at gmail.com> a écrit :
>
>     thanks all for your feedback, so seems straightforward now , good news
>
>     Maik, I have 50 collections because I have 2 collections per year
>     (since
>     lat 25 years)  , one for the raw and one for the published jpg and
>     I'm
>     using different backup solutions for each
>     Now I didn't think about the best strategy, when I start using DK,
>     just
>     started to create collections per year. What is the best or the most
>     efficient or more performant ? more smaller collections or less
>     bigger
>     collections? is there any advice let me know I can think to revise my
>     strategy
>
>
> We have never tested digiKam with a lot of collections like you.
>
> But typically it must be fully transparent. If you don't find any time 
> latency while searching items over all collections, well it's perfect.
>
> There is no perfect workflow. Each user setup collections as the best 
> personal solution. You can set just one collection with all stored 
> items in a specific album categorized by type of events, not by date, 
> and use the calendar or the timeline tools to do the triaging for you.
>
> Best
>
> Gilles Caulier
>
>
>     regards
>
>     Frederic
>
>
>     Le 25/01/2022 à 22:12, Maik Qualmann a écrit :
>     > And exactly this work on the database is no longer necessary
>     with a current
>     > digiKam version, since there is an "update" button in the
>     collection. Why
>     > frederic has 50 collections is a mystery to me, I wouldn't put
>     each folder
>     > branch in its own collection, but everyone has to know that for
>     themselves.
>     >
>     > Maik
>     >
>     > Am Dienstag, 25. Januar 2022, 20:13:58 CET schrieb Ty Mayn:
>     >> I am revived user low on the learning curve andbut I can
>     respond to how I
>     >> repaired a moved collection by going directly into the digikam4
>     data
>     >> basefile.  I have no experience in using the migration tool but
>     I did grab
>     >> a 2 year old collection and  the files for digikam6
>     installation out of a
>     >> backup location.  They had been living on an even older
>     workstation hard
>     >> drive  and I hoped that the collection would just operate by
>     firing up the
>     >> collection from a backup.   Digikam6 did fine to display the
>     thumbnails for
>     >> the identical recursive tree of folders and file images... but
>     it could not
>     >> deliver the full image preview.   I guess it could get to the
>     thumbnails
>     >> directly through the thumbnail database.
>     >>        Not understanding the migration tool..I installed DB
>     Browser and
>     >> studied the database field called AlbumRoots
>     >>   It has and identifier field and a path that allows the
>     digikam display
>     >> tools to fetch the proper full image .
>     >>     If ound that the identifier retained in the digikam4 was
>     pointing to a
>     >> UUID  for the hard drive in the old workstation
>     >> I had also moved the identically named folder and file
>     collection under a
>     >> new top level folder rather than root.
>     >> The field titled "specificPath" perhaps should be titled
>     "completePath"
>     >> from root.
>     >> To be safe I moved my identical folder collection to drive
>     root  (where it
>     >> had resided on earlier workstation) instead of trying to add
>     the toplevel
>     >> folder to the specific path
>     >>        The format for the 2 fields  identifier  and specific
>     path is
>     >>     volumeid:?uuid=NewHexstring  /identicalFolderCollection
>     >>    With those 2 fields set digikam happily treated the moved
>     collection as a
>     >> native home.
>     >>        My post about this is on the inactive other digikam forum
>     >> https://forum.kde.org/viewtopic.php?f=256&t=173758
>     <https://forum.kde.org/viewtopic.php?f=256&t=173758>
>     >>      I am a learner non programmer grasping for bits of info
>     and I was
>     >> relieved to find this direct way of repairing a collection and
>     database
>     >> which is identically positioned in a folder tree, but moved
>     without advance
>     >> planning.
>     >>      I am sure the many helpers on this list  have addressed
>     this structure
>     >> in past postings,
>     >>    but the info is buried in the past  until these email
>     threads are
>     >> gathered into a unified searchable document.
>     >> Ty
>     >>
>     >> On Tue, Jan 25, 2022 at 3:42 AM frederic chaume
>     <frederic.chaume at gmail.com>
>     >>
>     >> wrote:
>     >>> Hi All
>     >>>
>     >>> my current Disk is going to be out of sapce and I would like
>     to move all
>     >>> my collections (~50)  from current Disk to a new one.
>     >>> Then I would like to know what is the best process to do it.
>     >>> I see a refresh button for each collection in DK
>     configuration, is it
>     >>> then enough to choose the new location ? can we do it after
>     having moved
>     >>> the collections ?
>     >>>
>     >>> FYI I'm using DK7.5
>     >>>
>     >>> thanks for advices
>     >>>
>     >>> frederic
>     >
>     >
>     >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20220130/85618241/attachment-0001.htm>