View Single Post
Old 11-09-2022, 12:00 PM   #7709
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 6,999
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by ownedbycats View Post
Since I'm not entirely sure what "other metadata processing" means, confirmation that a copy category wouldn't work? I tested the following on a few fics and it worked once and then stopped working. So I'm inclined to think the "successful" run was a user error, e.g. forgetting to clear the field beforehand
Most metadata entries are populated during the 'get metadata' phase. cover_image can be filled much later, depending on the value.

As currently coded, cover_image is being filled after covertype has already been cached as an empty list. And the metadata cache does not trace back through include_in_* settings.

IE, cover_image is uncached when set, but not entries derived from it, whether from include_in_* or replace_metadata conditionals. Most of the time, it doesn't matter; and the cache saves significant time for users with extensive metadata editing. Until now, I would have said all the time.

I am considering whether this corner case is worth addressing or not.

This feels a bit familiar. Was there a similar case before?
JimmXinu is offline   Reply With Quote