![]() Message: "No other collections are configured in your database". The preceding description can be replaced by a simple (probably, grayed out) When there are no collections in the second table the whole table along with This will not remove the files, but this collection will disappearįrom your Digikam and Digikam of *all other users* which use this a standard red X icon, or the word "Delete"),Ī tooltip: "Remove this collection from the database. a standard green plus icon or the word "Add"),Ī tooltip: "Add this collection to your Digikam" "Collection on Network Shares, such as NFS and Samba/CIFS" Icon for network shares collection + a tooltip: "Collection on Removable Media, such as CD, DVD and USB drives" Icon for removable media collection + a tooltip: "Local Collection, directly stored on your computer hard disk" | | Alice Photos | /home/alice/Pictures | | | Type | Name | Possible Path(s) | Action | To access these collections you will need to provide a path to image files Other users of your database have configured the following collections. You have configured the following collections: (Removable media and remote file systems are supported) ![]() Write access is necessary to be able to edit images in these albums. Legend andīehavior are described in the next comment (presumably, comment #3 ).īelow are the locations of root albums used to store image files. So collection settings tab can look like the following mockup.ĪSCII tables and their headers are used just to signify the layout. Two are given by the user who already configured an access to theĬollection). It to the user along with a descriptive name and probably a path hints (last Maybe, a better solution: allow to query collection list from DB and present What ifĬollection is read-only? What if Bob now uses his own DB? In a collection root with collection UUID, but I don't like it. Although he knows path to theĬollection, how can he know UUID? A possible solution: digikam writes uuid.txt Wants to access the same files and DB entries. There is a broader issue of guessing that different absolute file names referĪlice configures her digikam and adds photos (DB records are created). Usecase, it seems logical to store them in local config. The question is where to store the paths for collection roots. IMHO, DB should contain all file paths relative to each collection root,Į.g. Restoration, mount point move/rename, etc. ![]() Other affected use cases may be thought of: DB & files on mobile HDD, backup home/alice/Pictures and Bob on his computer as /mnt/photoes. Themselves are shared over NFS, but Alice mounts them on her computer as This issue may also break the following use case (I actually need this!):Īlice and Bob use shared MySQL server for digikam database. Sorry for the lengthy post, but I tried to be constructive and not only stateĪ problem, but propose a viable solution.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |