You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it seems that Komga is unable to read the ComicInfo.xml file unless it's embedded in the cbz file. While that is highly functionable, that does mean that in order for the app to easily recognize the file, a file modification is necessary. Since Komga doesn't have a internal metadata matcher, to my knowledge at least, this is kinda necessary unless the user wants to write everything by hand in the UI... or create a bespoke scheduled task to have some outside script run over it all routinely... which most users won't do.
The modification of the file does mean that the file gets a new checksum, unique from other identical files, which in turn makes it much harder to flag duplicate data without... well... designing a workflow that opens the archive, reads the comicinfo and try a best guess at if it's a duplicate or no.
A "simple" way to address this is to simply allow external files to be read.
I do get that the team is probably reasonably busy with the new UI (Love it btw, please let me put that as default), and I don't know how many are running into the same issue as me here... but this would certainly be a good quality of life update for my part.
I'll probably writeup my own bespoke script to do this over API, or failing that, direct database manipulation... but it would be MUCH neater to just have that as base functionality.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi.
Currently it seems that Komga is unable to read the ComicInfo.xml file unless it's embedded in the cbz file. While that is highly functionable, that does mean that in order for the app to easily recognize the file, a file modification is necessary. Since Komga doesn't have a internal metadata matcher, to my knowledge at least, this is kinda necessary unless the user wants to write everything by hand in the UI... or create a bespoke scheduled task to have some outside script run over it all routinely... which most users won't do.
The modification of the file does mean that the file gets a new checksum, unique from other identical files, which in turn makes it much harder to flag duplicate data without... well... designing a workflow that opens the archive, reads the comicinfo and try a best guess at if it's a duplicate or no.
A "simple" way to address this is to simply allow external files to be read.
So
[BestScans]_Awesome_Manga_v44_ch9843.cbz
[BestScans]_Awesome_Manga_v44_ch9843.comicinfo.xml
for instance.
I do get that the team is probably reasonably busy with the new UI (Love it btw, please let me put that as default), and I don't know how many are running into the same issue as me here... but this would certainly be a good quality of life update for my part.
I'll probably writeup my own bespoke script to do this over API, or failing that, direct database manipulation... but it would be MUCH neater to just have that as base functionality.
All reactions