Feature request:

[Giordanni]

Hi there
I think it will be great if we can define multiple values for a book in "Series"field like, for example, "Tags" field.
I often need to set multiple values for this field. For example: a book belonging to some series, but also it is included in some collection.
Thanks in advance.
Best regards,
Giordanni

[theducks]

Originally Posted by Giordanni

Hi there
I think it will be great if we can define multiple values for a book in "Series"field like, for example, "Tags" field.
I often need to set multiple values for this field. For example: a book belonging to some series, but also it is included in some collection.
Thanks in advance.
Best regards,
Giordanni

Not doable (and has been requested before)
Series is really 2 fields (shown as 1 in the grid), Series (name), series_index (the number)

The common work around is a Custom Column (Series type)
In addition, set your Preferences: Searching : Grouped Searches (a tab) and Similar Books (a Tab)

[Giordanni]

Hi there and thanks for your reply.
IMHO, since I don't know your system design, and supposing you have a one-to-many relationship between Book and Series entities, have you consider this relationship becomes a many-to-many relationhip (with the series index in the relationship itself)? Maybe with this approach, the problem would be solved.
Of course, consecuences in whole system should be analyzed.
Again, it is just an idea.
Regards

[BetterRed]

Originally Posted by Giordanni

...

Of course, consecuences in whole system should be analyzed.
Again, it is just an idea.

And the impact on the three 3 million active users, about which one knows - where they are, which OS, and which calibre version they use.

BR

[chaley]

Originally Posted by Giordanni

Hi there and thanks for your reply.
IMHO, since I don't know your system design, and supposing you have a one-to-many relationship between Book and Series entities, have you consider this relationship becomes a many-to-many relationhip (with the series index in the relationship itself)? Maybe with this approach, the problem would be solved.
Of course, consecuences in whole system should be analyzed.
Again, it is just an idea.
Regards

calibre is open source. You are very welcome to make the database and user interface changes and submit them to @kovid for review and (possible) inclusion in calibre. Be aware that in addition to the db and calibre interface, you will probably need to change a lot of other stuff including the web server, many (!) plugins, many device drivers, and some programs like koreader and calibre sync.

[JSWolf]

Originally Posted by chaley

calibre is open source. You are very welcome to make the database and user interface changes and submit them to @kovid for review and (possible) inclusion in calibre. Be aware that in addition to the db and calibre interface, you will probably need to change a lot of other stuff including the web server, many (!) plugins, many device drivers, and some programs like koreader and calibre sync.

Sorry, but I disagree with having to change external programs. That's the purview of whoever maintains them.

[chaley]

Originally Posted by JSWolf

Sorry, but I disagree with having to change external programs. That's the purview of whoever maintains them.

Sigh. It is at least polite to advise them about what was changed and how it might affect them, especially if you *know* that it is a breaking change. But hey, not my problem. Let kiwidude figure out why the plugins no longer work.

[JSWolf]

Originally Posted by chaley

Sigh. It is at least polite to advise them about what was changed and how it might affect them, especially if you *know* that it is a breaking change. But hey, not my problem. Let kiwidude figure out why the plugins no longer work.

True that.

[ownedbycats]

Remember what happened when DeDRM broke and all the new users showed up here complaining about it? Yeah, that'd happen again unless plugin authors and third-party developers get advance notice and change it in time.