I want to store my images on a networked hard drive. I want my wife to
be able to access them from her *cough* Windows XP *cough* computer and me from my Fedora machine. We don't need simultaneous access. How do set this up ? The reason I ask this question is because when I open Digikam-> Settings-> Configure Digikam -> Collections -> Database File Path, I see "Note a remote file system, such as NFS, cannot be used here." Thanks _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tue, Sep 15, 2009 at 4:13 AM, Linuxguy123 <[hidden email]> wrote:
> I want to store my images on a networked hard drive. I want my wife to > be able to access them from her *cough* Windows XP *cough* computer and > me from my Fedora machine. We don't need simultaneous access. > > How do set this up ? > > The reason I ask this question is because when I open Digikam-> > Settings-> Configure Digikam -> Collections -> Database File Path, I see > "Note a remote file system, such as NFS, cannot be used here." > > Thanks > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Do you need access to the database file remotely as well? As in, does your wife use Digikam on her Windows machine? If not, then you can just have the DB file local on your machine and the pictures on a network share. For Fedora, I use a CIFS share to access my network drives with my pictures. It is mounted at boot through the fstab file, and it works just fine in Digikam. In Windows, you could mount a network share as a drive and have it point to where your pictures are. David _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Linuxguy123
I have a same situation, all my photos are on NFS share, my digikam DB
is on my desktop local. My wife has also the share mounted and needs to be able to tag the pictures for printing/sending to various friends. I'm planning to implement this (once I get to re-install my wife's laptop). 1) Keep all photos on NFS (or CIFS) share ...mounted to me and my wife (I have complete backup copy elsewhere) 2) Keep my digikam DB on my desktop 3) Let my wife have digikam on her laptop with local DB 4) She'll be tagging pics and digikam will save the tags to exif info of each photo (as well as her local digikam db) 5) Then I can re-scan the pics on my PC and get all the tags from exif and process further as instructed (by her :)) By this I'll get (somehow) the two DBs in sync ...at minimal I'll get the info I need from her to my db. Brano > I want to store my images on a networked hard drive. I want my wife to > be able to access them from her *cough* Windows XP *cough* computer and > me from my Fedora machine. We don't need simultaneous access. > > How do set this up ? > > The reason I ask this question is because when I open Digikam-> > Settings-> Configure Digikam -> Collections -> Database File Path, I see > "Note a remote file system, such as NFS, cannot be used here." > > Thanks > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by David Moran-3
On Tue, 2009-09-15 at 09:39 -0700, David Moran wrote:
> On Tue, Sep 15, 2009 at 4:13 AM, Linuxguy123 <[hidden email]> wrote: > > I want to store my images on a networked hard drive. I want my wife to > > be able to access them from her *cough* Windows XP *cough* computer and > > me from my Fedora machine. We don't need simultaneous access. > > > > How do set this up ? > > > > The reason I ask this question is because when I open Digikam-> > > Settings-> Configure Digikam -> Collections -> Database File Path, I see > > "Note a remote file system, such as NFS, cannot be used here." > > > > Thanks > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > Do you need access to the database file remotely as well? As in, does > your wife use Digikam on her Windows machine? My wife will need to access the db to tag images, etc. I have had *our* images set up on *my* computer for a long time and she is either using my computer to access them (which peeves me off) or not getting access when she wants (which peeves her off). Last night I showed her how I moved the images from a regular file system into Digikam and how she could view raw files even if I hadn't converted them yet. She was happy this was a step in the right direction. The next step is for her to have total access on her laptop. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Brano
On Tue, 2009-09-15 at 15:41 -0400, Brano wrote:
> I have a same situation, all my photos are on NFS share, my digikam DB > is on my desktop local. > My wife has also the share mounted and needs to be able to tag the > pictures for printing/sending to various friends. At least I'm not the only one with this need. > > I'm planning to implement this (once I get to re-install my wife's laptop). > > 1) Keep all photos on NFS (or CIFS) share ...mounted to me and my wife > (I have complete backup copy elsewhere) > 2) Keep my digikam DB on my desktop > 3) Let my wife have digikam on her laptop with local DB > 4) She'll be tagging pics and digikam will save the tags to exif info of > each photo (as well as her local digikam db) > 5) Then I can re-scan the pics on my PC and get all the tags from exif > and process further as instructed (by her :)) > > By this I'll get (somehow) the two DBs in sync ...at minimal I'll get > the info I need from her to my db. Hmmm... I'm skeptical that this will work (without issues). Can someone who has done it comment ? If everything is stored in the EXIF tag field, what does DigiKam need a db for ? Obviously lots of things. Why can't a DigiKam application connect to a remote db, other than for reasons of concurrent access ? I wouldn't have a problem ensuring that my wife and I aren't both using DigiKam at the same time. Thanks for the replies ! _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Sep 15, 2009, at 11:49 AM, Linuxguy123 wrote: > On Tue, 2009-09-15 at 15:41 -0400, Brano wrote: >> I have a same situation, all my photos are on NFS share, my digikam >> DB >> is on my desktop local. >> My wife has also the share mounted and needs to be able to tag the >> pictures for printing/sending to various friends. > > At least I'm not the only one with this need. > I use picasa at work from an rsynced directory so always write metadata to files. >> >> I'm planning to implement this (once I get to re-install my wife's >> laptop). >> >> 1) Keep all photos on NFS (or CIFS) share ...mounted to me and my >> wife >> (I have complete backup copy elsewhere) >> 2) Keep my digikam DB on my desktop >> 3) Let my wife have digikam on her laptop with local DB >> 4) She'll be tagging pics and digikam will save the tags to exif >> info of >> each photo (as well as her local digikam db) >> 5) Then I can re-scan the pics on my PC and get all the tags from >> exif >> and process further as instructed (by her :)) >> >> By this I'll get (somehow) the two DBs in sync ...at minimal I'll get >> the info I need from her to my db. > > Hmmm... I'm skeptical that this will work (without issues). Can > someone who has done it comment ? If everything is stored in the > EXIF > tag field, what does DigiKam need a db for ? Obviously lots of > things. > > Why can't a DigiKam application connect to a remote db, other than for > reasons of concurrent access ? I wouldn't have a problem ensuring > that > my wife and I aren't both using DigiKam at the same time. > > Thanks for the replies ! > The database is much much faster than having to scan the directory each time someone asks for a tag. There is also the problem with video files that can't be tagged yet (I'm hoping that Exiv2 will eventually handle those). I think that the idea of sharing the photos but using local databases would work well. Syncing up the database from the EXIF data in the files will work well. -- Tim Jenness _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Linuxguy123
On 09/15/2009 05:49 PM, Linuxguy123 wrote:
> On Tue, 2009-09-15 at 15:41 -0400, Brano wrote: > >> I have a same situation, all my photos are on NFS share, my digikam DB >> is on my desktop local. >> My wife has also the share mounted and needs to be able to tag the >> pictures for printing/sending to various friends. >> > At least I'm not the only one with this need. > > >> I'm planning to implement this (once I get to re-install my wife's laptop). >> >> 1) Keep all photos on NFS (or CIFS) share ...mounted to me and my wife >> (I have complete backup copy elsewhere) >> 2) Keep my digikam DB on my desktop >> 3) Let my wife have digikam on her laptop with local DB >> 4) She'll be tagging pics and digikam will save the tags to exif info of >> each photo (as well as her local digikam db) >> 5) Then I can re-scan the pics on my PC and get all the tags from exif >> and process further as instructed (by her :)) >> >> By this I'll get (somehow) the two DBs in sync ...at minimal I'll get >> the info I need from her to my db. >> > Hmmm... I'm skeptical that this will work (without issues). Can > someone who has done it comment ? If everything is stored in the EXIF > tag field, what does DigiKam need a db for ? Obviously lots of things. > > Why can't a DigiKam application connect to a remote db, other than for > reasons of concurrent access ? I wouldn't have a problem ensuring that > my wife and I aren't both using DigiKam at the same time. > > Thanks for the replies ! > store tags in exif, you have to turn it on in settings. Granted, this is not perfect solution, but it just exactly meets my needs. Multi user DB would be nice to have, but I can definitely live without it. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I've read digikam having a development version using mysql instead sqlite, so sooner or later we'll have multiuser environment.
On Wed, Sep 16, 2009 at 3:21 AM, Brano <[hidden email]> wrote:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Wed, 2009-09-16 at 09:23 +0200, Goose wrote:
> I've read digikam having a development version using mysql instead > sqlite, so sooner or later we'll have multiuser environment. Thanks for sharing that. I'm going go hold off on setting up my multi user system until that ships. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 09/16/2009 10:04 AM, Linuxguy123 wrote:
> On Wed, 2009-09-16 at 09:23 +0200, Goose wrote: > >> I've read digikam having a development version using mysql instead >> sqlite, so sooner or later we'll have multiuser environment. >> > Thanks for sharing that. I'm going go hold off on setting up my multi > user system until that ships. > You may be waiting a long time ...better review with dev team what's in developement and due dates. Mysql support does not imply multi user access management will be implemented day one (if at all). _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Wed, 2009-09-16 at 10:08 -0400, Brano wrote:
> On 09/16/2009 10:04 AM, Linuxguy123 wrote: > > On Wed, 2009-09-16 at 09:23 +0200, Goose wrote: > > > >> I've read digikam having a development version using mysql instead > >> sqlite, so sooner or later we'll have multiuser environment. > >> > > Thanks for sharing that. I'm going go hold off on setting up my multi > > user system until that ships. > > > You may be waiting a long time ...better review with dev team what's in > developement and due dates. > Mysql support does not imply multi user access management will be > implemented day one (if at all). I think this is why sqlite cannot be (should not be ?) used on a network share drive: http://www.sqlite.org/lockingv3.html See "How to corrupt the database." But... will it corrupt if only one user is access it at a time ? When I searched on sqlite + multiuser + network drive, it seems as though a lot of people want to use sqlite over a network. A lot of interesting applications use sqlite including Lightroom and Aperture. One person suggested that someone write a remote access interface to sqlite so that it can access the database on a network share drive. He called it an sqlite "redirector". I think that would be a much better effort than having to set up and administer mysql. http://archives.devshed.com/forums/databases-124/multiuser-db-on-network-share-2135870.html The other way around this problem is to look at using the Firebird database. http://en.wikipedia.org/wiki/Firebird_(database_server) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Brano
> >> I've read digikam having a development version using mysql instead
> >> sqlite, so sooner or later we'll have multiuser environment. > > > > Thanks for sharing that. I'm going go hold off on setting up my multi > > user system until that ships. > > You may be waiting a long time ...better review with dev team what's in > developement and due dates. > Mysql support does not imply multi user access management will be > implemented day one (if at all). MySQL support is on our schedule for the coding sprint this October/November. Multi-user support, concurrent access, including locking or conflic resolution, is a more difficult story. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Wed, 2009-09-16 at 18:15 +0200, Marcel Wiesweg wrote:
> > >> I've read digikam having a development version using mysql instead > > >> sqlite, so sooner or later we'll have multiuser environment. > > > > > > Thanks for sharing that. I'm going go hold off on setting up my multi > > > user system until that ships. > > > > You may be waiting a long time ...better review with dev team what's in > > developement and due dates. > > Mysql support does not imply multi user access management will be > > implemented day one (if at all). > > MySQL support is on our schedule for the coding sprint this October/November. > Multi-user support, concurrent access, including locking or conflic > resolution, is a more difficult story. Speaking from experience, its really easy to handle multi user access... create 2 access types. First one is RW, second one is read only. The first person to log into the db gets RW. All others are read only. Tell the user what connection they have when they log in. If they don't like what they get, they can log out and kick off the person who has RW access. It will work for 80% of the users needs. Most people (me) just want to be able to put the pictures and db on a networked drive and be able to access it from a variety of computers. Having concurrent editing access for multiple users would be nice to have, but just having remote access would be a good start, even if only one person has rw privileges. The team could implement concurrent multi user editing access at a later date. I also like the idea of having a read only user permission because I don't want everyone being able to edit the pictures and tags, especially deleting raw files or jpegs if there is only one of them. I would like to see DigiKam use a trash setup (either from the OS or within itself) for this very reason. Imagine having 20,000 tagged images and a user who doesn't understand things removes a couple tags from the tag list when they meant to remove them from a few pictures. Hours and hours of work is lost in 30 seconds. :shudder: _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 09/16/2009 12:42 PM, Linuxguy123 wrote:
> On Wed, 2009-09-16 at 18:15 +0200, Marcel Wiesweg wrote: > >>>>> I've read digikam having a development version using mysql instead >>>>> sqlite, so sooner or later we'll have multiuser environment. >>>>> >>>> Thanks for sharing that. I'm going go hold off on setting up my multi >>>> user system until that ships. >>>> >>> You may be waiting a long time ...better review with dev team what's in >>> developement and due dates. >>> Mysql support does not imply multi user access management will be >>> implemented day one (if at all). >>> >> MySQL support is on our schedule for the coding sprint this October/November. >> Multi-user support, concurrent access, including locking or conflic >> resolution, is a more difficult story. >> > Speaking from experience, its really easy to handle multi user access... > create 2 access types. First one is RW, second one is read only. The > first person to log into the db gets RW. All others are read only. > Tell the user what connection they have when they log in. If they don't > like what they get, they can log out and kick off the person who has RW > access. > > It will work for 80% of the users needs. Most people (me) just want to > be able to put the pictures and db on a networked drive and be able to > access it from a variety of computers. Having concurrent editing access > for multiple users would be nice to have, but just having remote access > would be a good start, even if only one person has rw privileges. > > The team could implement concurrent multi user editing access at a later > date. > > I also like the idea of having a read only user permission because I > don't want everyone being able to edit the pictures and tags, especially > deleting raw files or jpegs if there is only one of them. I would like > to see DigiKam use a trash setup (either from the OS or within itself) > for this very reason. > > Imagine having 20,000 tagged images and a user who doesn't understand > things removes a couple tags from the tag list when they meant to remove > them from a few pictures. Hours and hours of work is lost in 30 > seconds. :shudder: > > can screw up your collection, you can as easily do a wrong click and have things gone for good. Not speaking of very possible HDD failure. Disks are so cheap today, photos are priceless, invest to a secondary HDD and do some kind of rsync daily. (I personally have all my valuables (photos) on RAID-5 disks rsyncing to backup disk daily) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Wed, 2009-09-16 at 13:33 -0400, Brano wrote:
> On 09/16/2009 12:42 PM, Linuxguy123 wrote: > > On Wed, 2009-09-16 at 18:15 +0200, Marcel Wiesweg wrote: > > > >>>>> I've read digikam having a development version using mysql instead > >>>>> sqlite, so sooner or later we'll have multiuser environment. > >>>>> > >>>> Thanks for sharing that. I'm going go hold off on setting up my multi > >>>> user system until that ships. > >>>> > >>> You may be waiting a long time ...better review with dev team what's in > >>> developement and due dates. > >>> Mysql support does not imply multi user access management will be > >>> implemented day one (if at all). > >>> > >> MySQL support is on our schedule for the coding sprint this October/November. > >> Multi-user support, concurrent access, including locking or conflic > >> resolution, is a more difficult story. > >> > > Speaking from experience, its really easy to handle multi user access... > > create 2 access types. First one is RW, second one is read only. The > > first person to log into the db gets RW. All others are read only. > > Tell the user what connection they have when they log in. If they don't > > like what they get, they can log out and kick off the person who has RW > > access. > > > > It will work for 80% of the users needs. Most people (me) just want to > > be able to put the pictures and db on a networked drive and be able to > > access it from a variety of computers. Having concurrent editing access > > for multiple users would be nice to have, but just having remote access > > would be a good start, even if only one person has rw privileges. > > > > The team could implement concurrent multi user editing access at a later > > date. > > > > I also like the idea of having a read only user permission because I > > don't want everyone being able to edit the pictures and tags, especially > > deleting raw files or jpegs if there is only one of them. I would like > > to see DigiKam use a trash setup (either from the OS or within itself) > > for this very reason. > > > > Imagine having 20,000 tagged images and a user who doesn't understand > > things removes a couple tags from the tag list when they meant to remove > > them from a few pictures. Hours and hours of work is lost in 30 > > seconds. :shudder: > > > > > Well, no offense, but how about daily backups? It's not that other users > can screw up your collection, you can as easily do a wrong click and > have things gone for good. Not speaking of very possible HDD failure. > Disks are so cheap today, photos are priceless, invest to a secondary > HDD and do some kind of rsync daily. > (I personally have all my valuables (photos) on RAID-5 disks rsyncing to > backup disk daily) An ounce of prevention is worth a pound of cure. That is why Unix OSes have file and directory permissions. And when might I figure out that this error happened and how much time might have elapsed between when it happens and when I figure it out and how much work might have been done in that time. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 09/16/2009 01:46 PM, Linuxguy123 wrote:
> On Wed, 2009-09-16 at 13:33 -0400, Brano wrote: > >> On 09/16/2009 12:42 PM, Linuxguy123 wrote: >> >>> On Wed, 2009-09-16 at 18:15 +0200, Marcel Wiesweg wrote: >>> >>> >>>>>>> I've read digikam having a development version using mysql instead >>>>>>> sqlite, so sooner or later we'll have multiuser environment. >>>>>>> >>>>>>> >>>>>> Thanks for sharing that. I'm going go hold off on setting up my multi >>>>>> user system until that ships. >>>>>> >>>>>> >>>>> You may be waiting a long time ...better review with dev team what's in >>>>> developement and due dates. >>>>> Mysql support does not imply multi user access management will be >>>>> implemented day one (if at all). >>>>> >>>>> >>>> MySQL support is on our schedule for the coding sprint this October/November. >>>> Multi-user support, concurrent access, including locking or conflic >>>> resolution, is a more difficult story. >>>> >>>> >>> Speaking from experience, its really easy to handle multi user access... >>> create 2 access types. First one is RW, second one is read only. The >>> first person to log into the db gets RW. All others are read only. >>> Tell the user what connection they have when they log in. If they don't >>> like what they get, they can log out and kick off the person who has RW >>> access. >>> >>> It will work for 80% of the users needs. Most people (me) just want to >>> be able to put the pictures and db on a networked drive and be able to >>> access it from a variety of computers. Having concurrent editing access >>> for multiple users would be nice to have, but just having remote access >>> would be a good start, even if only one person has rw privileges. >>> >>> The team could implement concurrent multi user editing access at a later >>> date. >>> >>> I also like the idea of having a read only user permission because I >>> don't want everyone being able to edit the pictures and tags, especially >>> deleting raw files or jpegs if there is only one of them. I would like >>> to see DigiKam use a trash setup (either from the OS or within itself) >>> for this very reason. >>> >>> Imagine having 20,000 tagged images and a user who doesn't understand >>> things removes a couple tags from the tag list when they meant to remove >>> them from a few pictures. Hours and hours of work is lost in 30 >>> seconds. :shudder: >>> >>> >>> >> Well, no offense, but how about daily backups? It's not that other users >> can screw up your collection, you can as easily do a wrong click and >> have things gone for good. Not speaking of very possible HDD failure. >> Disks are so cheap today, photos are priceless, invest to a secondary >> HDD and do some kind of rsync daily. >> (I personally have all my valuables (photos) on RAID-5 disks rsyncing to >> backup disk daily) >> > An ounce of prevention is worth a pound of cure. That is why Unix OSes > have file and directory permissions. > > And when might I figure out that this error happened and how much time > might have elapsed between when it happens and when I figure it out and > how much work might have been done in that time. > paranoia and countless solutions ;) ...pick what is right for you in your scenario. But do not underestimate your enemy ;) i.e. disks are spinning and will fail when you leas expect it, users make errors when least expected ...and so on ;) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |