Quote:
Originally Posted by kaufman
How is this different from the "scan for new books" option that exists now? I have never done this, but don't people run into the same issue today? Are you getting a lot of complaints about metadata now.
|
Technically it isn't different, which is one reason that option 2 interests me. However, there are some qualitative differences.
The first is the source of the books. Generally the books discovered in a CC library either came via calibre send-to-device/content server so that the metadata in the book was updated on the way out and is at least close to correct, or they came from "somewhere else" so that the metadata is unknown. The first works well. The second doesn't, and yes, we hear about it. We also hear about problems with non-epub, especially pdf where the scan produces books named "asdbwe" and the like.
A second is when the scan happens. It happens as part of a connect, which means that if a book can be matched to the calibre library the user sees the correct metadata immediately. There is no intermediate state such as will exist between an import and a connect/metadata update.
A third is that scanning is not advertised as a CC advantage/feature. It is simply something that CC does. The result: expectations are usually not set. We hear frequently hear from people who know about the scan and have expectations for it. In particular we hear from people who want the file names parsed for title/author/series because the book contains no metadata or the metadata is wrong. Down this path lies a reimplementation of calibre, something we are not interested in doing.