Auto numbering series when adding books

[Marg1780]

Hello, I have a number of epubs which belong to a general collection rather than having a specific series order. They each have a "calibre:series" metadata entry, but do not have a "calibre:series_index" entry.

Until recently, when I added such books to Calibre, they would automatically be assigned the next available number (which is what I want, since it essentially sets the ordering by date of creation), but now they each enter as "seriesName[1]" instead. Did I manage to screw something up in the settings, or has the behavior changed? And if so, are there any settings I can adjust to get things back to the old behavior?

I'd really appreciate any help from the experts! Thanks!

[theducks]

Preferences: tweaks: <ID: series_index_auto_increment>

But no entry sounds weird... Like someone removed it
AFAIK Calibre MUST have a series_index value if there is a series.

The index can be 0, usually defaults to 1

[Marg1780]

Originally Posted by theducks

Preferences: tweaks: <ID: series_index_auto_increment>

But no entry sounds weird... Like someone removed it
AFAIK Calibre MUST have a series_index value if there is a series.

The index can be 0, usually defaults to 1

Thanks so much for the information - I had a look through "tweaks" (I was focusing on "input" menus and "add books" etc.) and found a line for

use_series_auto_increment_tweak_when_importing = False

I suspect that in the older versions the installation default was True, since I don't believe I've ever so much as breathed on anything in that area. (At least not intentionally... ) Just flipped it and tried it, and that does indeed put it back to the old behavior!

My comment about the metadata applied to the internal metadata within the epub itself. Specifically, the entry within content.opf. I generate the epubs myself using Sigil, and I include a "<meta name="calibre:series" content="x" />" entry, but not the second line for series_index. Once the epub is entered into Calibre, it is automatically assigned an index value - the trouble was that for the past month or so - since 3.32.0, I think? - every new one I added was assigned an index value of 1. Fixed now, and all is great.