Quote:
Originally Posted by CrossReach
That's my problem right now. There's two of us working side by side on a project and we'll both be updating and converting Word files to epub, as Calibre is the best program out there for converting epubs that we have found. But maybe my plan will not work then.
|
Sounds like theDucks' proposed 3 machine workflow is the only functional answer. Each user has their own calibre and maintains their own library for the work they're doing. When they finish a book, they export it, using calibre's Save to Disk function, targeting a network shared folder on the third machine.
The 3rd machine run's its own calibre 24/7 and has the shared network folder as a watch folder (set in Prefs>Adding Books). This copy of calibre will then automatically move the books from the watch folder to its library. Since importing is not processor/memory intensive to any great degree and since this machine has no other "chore" other than to offer the network shared folder, it doesn't need to be a particularly powerful machine. Even if imports are somewhat slow it doesn't matter since no user is waiting for it to fininsh.
This way, each user's calibre is isolated from the "master" calibre. Each worker has their own library or libraries; perhaps one for "waiting in the queue", one for "in progress" and one for "done at exported to the master".