collection location change

[Maik Qualmann]

The "top" folder is the same one you already set (/media/mik/d3p3/photos). 
This should already be set in the file dialog.
If you do everything right there is no problem, if you choose a wrong root 
folder, the database will be rescanned. If it is an SQLite DB, then simply 
backup the digikam4.db file beforehand.

Maik

Am Samstag, 5. August 2023, 15:10:40 CEST schrieb Mik - Mint:
> Thank you for the reply.
> The process of changing the location type initially asks for the
> location of the removable media (/media/mik/d3p3-photos) and then for
> the name of the "top" folder in that location.
> 
> There is currently no "top" folder so:-
> 
> It appears that I would have to create a dummy folder on
> /media/mik/d3p3-photos to act a "top"
> 
> I can do that but what effect will it have on the existing database and
> its contents ?
> 
> I really don't want to degrade the existing records !
> 
> ----------------------------------------------------
> 
> On 05/08/2023 11:51, Maik Qualmann wrote:
> > Next to the trash icon you have the icon for updating the collection. You
> > can also easily change the collection type with this.
> > 
> > Maik
> > 
> > Am Samstag, 5. August 2023, 11:00:03 CEST schrieb Mik - Mint:
> >> The collection location as currently defined is in "local collections"
> >> but, as show, it is actually on a removeable hard drive. In practice
> >> this means that I have to mount the drive before starting Digikam or the
> >> startup just hangs.
> >> 
> >> - how do I define the collection as removeable without losing all the
> >> stored info? I'm concerned that hitting the delete button will lose the
> >> stored info
> >> 
> >> - what is the practical difference of the 2 options (local/removeable?