[Bug] Comma delimited SeriesGroup field in ComicInfo not importing as expected

[shrublet]

Steps to reproduce

1. Create an archive with the SeriesGroup field in ComicInfo.xml
2. Import into library with Collections from ComicInfo enabled

Expected behavior

Based on the documentation here for the Anansi Project, I presumed comma-separated values would be converted into discrete collections in Komga.

Actual behavior

Komga imports the collection as a singular entry with a comma in the name instead.

Logs

No response

Komga version

0.165.0

Operating system

Windows 11

Other details

Have additionally tried importing with multiple SeriesGroup fields, but only one is ingested.

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I have checked the FAQ.
• I have updated the app to the latest version.
• I will fill out all of the requested information in this form.

[gotson]

From the documentation:

The SeriesGroup element will be used to create a collection with that name, or add the series to an existing collection with that name.

If the SeriesGroup element is set to a different value in each book of the series, then each value of the element will create a collection.

[shrublet]

Ah, ok I think I understand. Komga doesn't import them individually, but comma-separated values are considered discrete in the ideology of the documentation? If I understand correctly. I wasn't sure as I recall you spearheading creating the documentation for a unified ComicInfo schema. If this is the case, I assume there is no way to have multiple automatically generated collections from multiple SeriesGroup entries? Thanks.

[gotson]

Well ComicInfo is not documented, and the documentation we produced came after the Komga implementation. Changing the behaviour now would introduce a change for existing users, and i am not really sure of what's the usage of that field in the wild.

[shrublet]

Fair enough. It's not a big deal regardless. I personally just use the field for both original magazine release and franchise, but I'm not sure if these are "intended" uses of these fields. And it's mostly for the fact that Komga automatically organizes these into collections which is convenient. You can go ahead and close this though if Komga is working as intended or this isn't a planned feature.

[github-actions]

🎉 This issue has been resolved in v1.0.0 (Release Notes)