View Single Post
Old 12-02-2017, 08:05 PM   #13
haertig
Wizard
haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.haertig ought to be getting tired of karma fortunes by now.
 
Posts: 1,910
Karma: 32500000
Join Date: Sep 2017
Device: PW3, Galaxy Tab A9+, Moto G7
Sounds like you might need a "source code control" system. Those are designed to either 1) only allow one user to edit something at a time, or 2) allow concurrent editing and then intelligently merge the two edits. Each user could have their local copy of Calibre to assist in the editing process. But the actual "database" is the source code control system. You could even have a "master Calibre" drawing the most recent committed version of a file to display in its library. You could even get by with the ancient, but simple, RCS or SCCS system, if you don't need concurrent editing.
haertig is offline   Reply With Quote