|
Yes, but I want to use the file itself to retrieve the metadata from the file, by passing it to a localhost server that will analyse and summarise the file and return the metadata.
To be in sync with what Calibre is doing and to have the context to return the exact data for the individual book and to put the returning metadata into the result_queue, I need to be able to retrieve the file location and send it to the localhost for analysis.
So what you are saying is I'm going to have to do a database search and then compile the paths from the DB result?
Just another quick question. For the Cache DB class, in the documentation, it doesn't say what any of the custom classes are expecting as input e.g.
search(query, restriction='', virtual_fields=None, book_ids=None)
Search the database for the specified query, returning a set of matched book ids.
Query in what way? an SQL query e.g. "SELECT book_id FROM books" ? a cut-down query "book_id From Books" a Set, a Dict, a list of tuples? Do we need to set a cursor and send that, like working with SQLite?
Without the input information, I'm trying to stack trace to find the original function to work out the inputs to the functions. Is it worth adding the expected input to the documentation? Plus, maybe a little example so people get the idea of how the custom function works?
|