View Single Post
Old 02-22-2019, 10:17 AM   #146
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Originally, LC was a private plug-in that I developed just for me, and running it as multiple threads in the foreground rather than jobs in the background fit how I needed to use it for dodgy fiction books. I made it available to everyone later as an afterthought.

EPUBs always have a page count, so the Count Pages plugin is perfect running as a job. Ditto for Extract ISBN, Polish Books, Modify EPUB, etc. That is not at all the case for DDC or LCC for random fiction books with sketchy metadata that often do not have a straight-forward lookup. It takes manual fiddling with to find them, and even then fails frequently for new fiction unless a manually-discovered alternate ISBN can be found for the lookup.

I have automated the quality fixes and metadata enhancements (e.g. count pages, polishing, extract ISBN, etc.), so all of that is already done by the time I get around to running LC in my Work Bench Library. I am referring to the Job Spy plug-in. See the attached.



DaltonST
Attached Thumbnails
Click image for larger version

Name:	2019-02-22 09_12_48-Window.jpg
Views:	314
Size:	559.4 KB
ID:	169860  
DaltonST is offline   Reply With Quote