MobileRead Forums - View Single Post - Vast rewrites when importing a wrongly cased author

DaltonST · 01-22-2018, 04:09 PM

A good way to avoid that issue is to not import raw books directly into your Main Library, but rather into a Workbench Library. Scrub, standardize and add missing metadata to the books while still in your Workbench Library. Such activity has zero impact on the books already in your Main Library. Finally, move your new books from your Workbench Library to your Main Library.

If your Main Library is actually fairly trashed-out, then rename it Workbench, and create a fresh Main. Move only the clean books from Workbench to Main, and work on the remaining books now in your Workbench.

Be sure to Vacuum the metadata.db file, since it grows to an enormous size over time. Do so with Library > Library Maintenance > Check Library, which first vacuums metadata.db and then compares it to your physical books, and vice-versa.

If you do not want any .opf files being created while you make many mass-changes in your Workbench Library, you can purge the queue for just the WorkBench Library using the Job Spy plugin, which has a Tool to do just that (highlighted in the attachment).

That tool is designed to be used when it is a total waste of cpu and disk to create .opf files at a rate of 1 per second constantly for ever-changing metadata that is actively being worked on in a Workbench Library.

When you move your clean books to your Main Library, a final .opf file will be created for that new book in that Library.

Obviously, do not purge the queue for your Main Library. Those .opf files allow you to recover from a corrupt metadata.db file. The exception to that rule might be creating a new Custom Column that is easily recomputed, and you don't want 50,000 .opf files being created just to be able to restore a Custom Column that is easily re-populated on-demand (e.g. from a simple, fast job).

DaltonST

01-22-2018, 04:09 PM	#8
DaltonST Deviser Posts: 2,265 Karma: 2090983 Join Date: Aug 2013 Location: Texas Device: none	A good way to avoid that issue is to not import raw books directly into your Main Library, but rather into a Workbench Library. Scrub, standardize and add missing metadata to the books while still in your Workbench Library. Such activity has zero impact on the books already in your Main Library. Finally, move your new books from your Workbench Library to your Main Library. If your Main Library is actually fairly trashed-out, then rename it Workbench, and create a fresh Main. Move only the clean books from Workbench to Main, and work on the remaining books now in your Workbench. Be sure to Vacuum the metadata.db file, since it grows to an enormous size over time. Do so with Library > Library Maintenance > Check Library, which first vacuums metadata.db and then compares it to your physical books, and vice-versa. If you do not want any .opf files being created while you make many mass-changes in your Workbench Library, you can purge the queue for just the WorkBench Library using the Job Spy plugin, which has a Tool to do just that (highlighted in the attachment). That tool is designed to be used when it is a total waste of cpu and disk to create .opf files at a rate of 1 per second constantly for ever-changing metadata that is actively being worked on in a Workbench Library. When you move your clean books to your Main Library, a final .opf file will be created for that new book in that Library. Obviously, do not purge the queue for your Main Library. Those .opf files allow you to recover from a corrupt metadata.db file. The exception to that rule might be creating a new Custom Column that is easily recomputed, and you don't want 50,000 .opf files being created just to be able to restore a Custom Column that is easily re-populated on-demand (e.g. from a simple, fast job). DaltonST Attached Thumbnails Last edited by DaltonST; 01-22-2018 at 04:20 PM. Reason: typo.