[Kavita] Skip filename parsing for zips containing a comicinfo.xml

[CtrlAltDefeat94]

Idea Description

I would find a setting useful to disable filename parsing for any file that contains a comicinfo.xml.
If the tag isn't in the comicinfo, it means that tag shouldnt be used at all.
For example Re Zero volumes with Chapter X in their titles dont have a chapter tag inside the comicinfo, so there's no need to parse it as such.

Related;
#2908

Idea Category

Feature Enhancement

Duration of Using Kavita

No response

Before submitting

• I've already searched for existing ideas before posting.

[KenNZ23]

I'd like to support this request (or something similar). This is an issue with Kavita that has frustrated me also, and may speak to a larger design philosophy problem, namely, how does Kavita treat comicinfo.xml files?

With regards to the request and the related issue #2908 that it is linked to, my initial suggestion is that if a comicinfo.xml file is present, and if it has data in any of the issue, volume, or format fields then Kavita should skip filename parsing for the purposes of determining issue or volume number and instead only take from the data present in the comicinfo.xml files. This would address the related issue for any user making use of comicinfo.xml files (which should be everyone if they care about their library!). Filename parsing should be a method of last resort limited to people who don't use comicinfo.xml files.
For example, such a change would mean that when processing a file named 'Elephantmen 2260 v03.cbz' with a comicinfo.xml file containing data in the volume field (eg. 3), Kavita would process this as volume 3 and would leave the issue field empty. Currently Kavita will add 2260 to the issue field, resulting in this one file showing up in Kavita as both Volume 3 and as Issue 2260. Given that there are multiple volumes in this series, we currently end up with multiple issue 2260's...

The suggestion here to entirely skip filename parsing if a comicinfo.xml is present is a more significant step and one that suggests that Kavita development needs to take a firmer stand on the use of comicinfo.xml files. Of course, having this as a setting may work around this.

With regards to design philosophy and 'taking a stand' on the use of comicinfo.xml files I suggest you need to consider pushing users into an either/or situation. Either they use a comicinfo.xml file - in which case Kavita will assume they have filled it out correctly with the data they want to use and will skip filename parsing, or, they do not use comicinfo.xml files (ie. they remove them from any .cbz files they have) and let Kavita do all the parsing. Having a hybrid system (as current) where Kavita will read the comicinfo.xml file, grabbing volume and format data, but still parsing the filename, adding issue data that is not in the comicinfo.xml file is just causing headaches for the large amount of comics that have numbers in their names.
The biggest problem I can see is that even if you push people into an either/or system, you will likely need to have some code that performs a 'sanity check' on any comicinfo.xml file to ensure it has the minimum amount of data required to create a sane entry in the database. That may be as little as having something in the series or title field and perhaps treating any comicinfo.xml lacking data in all of the issue, volume, or format fields as a 'special.' You'd then have to alert people to which files failed to parse due to missing data in the comicinfo.xml files.

I anticipate that you will be reluctant to push back at the users too much, as it will no doubt cause complaints from people with badly organised libraries (most likely as a result of piracy). I already see someone wanting you to allow them to disable parsing of comicinfo.xml files rather than sorting out their own library... Therefore my suggestion to you is as follows:

1. Consider implementing my 'initial suggestion' as default behaviour in Kavita: If a comicinfo.xml file is present and has data in any of the issue, volume, or format fields then skip filename parsing for the purposes of determining issue or volume number and instead only take from the data present in the comicinfo.xml files. I believe this will solve most current issues.
2. Consider implementing the OP's suggestion to completely disable filename parsing if a comicinfo.xml file is present as an Advanced/Experimental setting, with any resulting issues being completely on the user who chose to enable this.