Quote:
Originally Posted by Magic Man
Calibre manages its books using a filesystem, it doesn't store them in a db or other container so the point is moot.
I can understand perfectly that if there was a requirement two have more than one book directory with exactly the same name under the same author directory then there would need to be some form of unique identifyer in the book directory name to identify it, hence the id value
|
Version 1 of Calibre did exactly as you describe - it kept the files and metadata inside the database. File formats were completely inaccessible to the user, other than by the tools provided to Send to Device or Save to Disk. For performance and other reasons, later versions were rewritten to store the files in the OS file system and metadata only in the db, but Calibre still needed a unique reference to each file storage directory.
It's not hard to strip off the id, should you want to, but you should be aware that the entire file name is not used to create the folder name - only a limited number of the first characters in the title, plus the id. Should Kovid change to your proposed design, functionality would be lost, as the user often has no control over the title/author during initial import when metadata is read from inside the file being imported.
The bottom line is that Calibre uses the library folder/directory as part of its database, it needs to be uniquely named and that's not likely to change any time soon.