MobileRead Forums - View Single Post

drMerry · 04-17-2011, 09:07 AM

Hi,

I have a suggestion / request for a core enhancement.
I would really like to use multiple library's at one time. My reasons:

1. There has been made a clear choice in the structure of the file-location.
No discussion about this to change it.
In my case, all e-books are on a home-server. This server is accessible by FTP. My server is doing a lot of tasks. If a ftp-user gets into my calibre-lib, it takes a long time to display all my 1872 authors, sometimes causing a time-out. If I could have multiple databases in Calibre, I could put my authors in a sub-database on start-letter (A, B, C,...)
2. I have multiple users using both the ftp and the Calibre front-end.
If I had multiple db's, I could give separate access to users (some would only want to have books of a particular language or topic for example).
If I add a book of this type, I want it to be available in this particularly db, but also in compete library.
3. I have a separate computer for work / study. I would like to keep some books on my 2nd computer. If I open my lib, I want to see all my books including study-books on my 2nd-pc.
On the first pc, I want to see only the books on the server (this are the only books available for this pc)
4. In any case I want to search / view all books available for the current pc.

Implementation thoughts:
Scan for available db's on startup. Scan only in predefined directories and their sub-directories.
If a db is not available (for example a laptop that is on travel with only the local part available), only show available db's. If none, show the current warning.

When adding a book, put the book in a predefined db (e.g. Main or Unsorted), a user-predefined db, a rule-based db (author starts with A? Put in db A), or ask the user.

Put Access-rights on db's. It is not very useful to add a password on a db, books are accessible by browsing. But with multiple db's, you could add some restrictions on a db. For example, you could deny users of db x to delete files. If they delete files, It will not be removed from the db, but will be moved to a predefined location / db. Only users that have access to the other db, can really delete books. This will prevent 'digibetics' from removing books accidentally.

Just some thoughts.
Thinking about it is easier than building it, but it would improve my personal usability of Calibre a lot.

04-17-2011, 09:07 AM	#1
drMerry Addict Posts: 293 Karma: 21022 Join Date: Mar 2011 Location: NL Device: Sony PRS-650	Suggestion: Work with multiple databases Hi, I have a suggestion / request for a core enhancement. I would really like to use multiple library's at one time. My reasons: 1. There has been made a clear choice in the structure of the file-location. No discussion about this to change it. In my case, all e-books are on a home-server. This server is accessible by FTP. My server is doing a lot of tasks. If a ftp-user gets into my calibre-lib, it takes a long time to display all my 1872 authors, sometimes causing a time-out. If I could have multiple databases in Calibre, I could put my authors in a sub-database on start-letter (A, B, C,...) 2. I have multiple users using both the ftp and the Calibre front-end. If I had multiple db's, I could give separate access to users (some would only want to have books of a particular language or topic for example). If I add a book of this type, I want it to be available in this particularly db, but also in compete library. 3. I have a separate computer for work / study. I would like to keep some books on my 2nd computer. If I open my lib, I want to see all my books including study-books on my 2nd-pc. On the first pc, I want to see only the books on the server (this are the only books available for this pc) 4. In any case I want to search / view all books available for the current pc. Implementation thoughts: Scan for available db's on startup. Scan only in predefined directories and their sub-directories. If a db is not available (for example a laptop that is on travel with only the local part available), only show available db's. If none, show the current warning. When adding a book, put the book in a predefined db (e.g. Main or Unsorted), a user-predefined db, a rule-based db (author starts with A? Put in db A), or ask the user. Put Access-rights on db's. It is not very useful to add a password on a db, books are accessible by browsing. But with multiple db's, you could add some restrictions on a db. For example, you could deny users of db x to delete files. If they delete files, It will not be removed from the db, but will be moved to a predefined location / db. Only users that have access to the other db, can really delete books. This will prevent 'digibetics' from removing books accidentally. Just some thoughts. Thinking about it is easier than building it, but it would improve my personal usability of Calibre a lot.