12-14-2014, 05:57 PM | #1 |
Connoisseur
Posts: 78
Karma: 52
Join Date: Nov 2014
Device: Kindle
|
Feature request: More flexible series
Hi,
I tried to search forum for duplicate request, but didn't find it. I'd like to see to have the ability: a) for book to be in more than one series b) to have the possibility not to enter series index if needed For a) it would behave similarly to tags in mass edit dialogue, I believe division by ; would work okay. Export, import, edit, all of these would be similar, maybe with the exception of auto-setting [1], at least gui wise. For database, it's simple N:M table for connecting book-id to series-id/index. Similar table must exist now for linking book-author records. For b) this feature request was already here (with solutions as '0' or '1000' which are dirty workarounds, not solutions). Also people requested ranges (for omnibuses), but these could be worked around by multiple records SeriesName #1; SeriesName #2; SeriesName #3 Also, I think the number shouldn't be float or double, but something like Integer.Integer because there are such systems around, I believe Goodreads (which I plan to synchronize to). Goodreads example: https://www.goodreads.com/book/show/18709246-bullseye Book in two series, both in .5 order Last edited by jindroush; 12-14-2014 at 06:26 PM. Reason: Added example |
12-14-2014, 07:44 PM | #2 |
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
1) Use a custom column of type series.
2) I like my "dirty" workaround, and I don't really understand what point you think you are making about them. What difference does it make if there is a number there you are ignoring? Surely there must be something there anyway, to indicate null -- that is what the zero was invented for, so we could express non-existence. If you really, really want... change the default value. Preferences ==> Advanced ==> Tweaks. tweak value of Auto increment series index Code:
series_index_auto_increment = '0' And what does it being a float or not have anything to do with the price in China? For that matter, why are you so sure of what goes on in Goodreads' backend? Series in calibre is capped at 2 decimals anyway, as if that made any difference. Last edited by eschwartz; 12-14-2014 at 07:49 PM. |
12-14-2014, 07:47 PM | #3 |
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
And lo, the Goodreads metadata source plugin. Hmm, the author didn't seem to be troubled by the number of decimals...
https://www.mobileread.com/forums/sho...d.php?t=130638 |
12-14-2014, 09:23 PM | #4 |
Resident Curmudgeon
Posts: 74,027
Karma: 129333114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I think what the OP wants is the series column to support multiple series like the tag column supports multiple tags.
|
12-14-2014, 09:41 PM | #5 | |
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Quote:
And also a confusing bone to pick with floats as the datatype. |
|
12-14-2014, 10:54 PM | #6 |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
To my mind the series index is more like a version number than a number. If I was writing "1.1", "1.12", I would probably be referring the first and twelfth story that are between the first and second novels. In calibre, I would have to record that as "1.01" and "1.12". That works if I plan ahead or know there are more than ten in-between stories, but I rarely do (plan ahead).
|
12-14-2014, 11:00 PM | #7 |
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
That is what I use it for as well. I solve the problem, BTW, by always using the smaller version. I think chaley has a calibre-debug script he created for someone to check the other same-series entries for >=10 and insert a final value into a custom column.
|
12-15-2014, 04:04 AM | #8 | ||
Addict
Posts: 245
Karma: 20386
Join Date: Sep 2010
Location: France
Device: Cybook Diva
|
Quote:
Several use cases come to mind, but mostly short stories collections where two or more works are side-stories in their respective series. Looking for "My Series" would look like Code:
series:"=My Series" or series_1:"=My Series" or series_2:"=My Series" or series_3:"=My Series" or series_4:"=My Series" Quote:
N. |
||
12-15-2014, 04:28 AM | #9 | |
Grand Sorcerer
Posts: 11,742
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
Coloring and icon rules would require a different solution, probably a tags-like composite column that aggregates the names from the columns included in the search term. Hmmm... I could make a template function that returns the values in the "virtual" column. This would be a gui-only function so it would not obviate the need for the composite column if the info is to be used in save-to-disk templates. I am not sure what problem you are solving with the max() function. |
|
12-15-2014, 06:40 AM | #10 | |
Grand Sorcerer
Posts: 6,234
Karma: 11768331
Join Date: Jun 2009
Location: Madrid, Spain
Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2
|
Quote:
Please, could you elaborate about the difference between integer.integer and float. Taking into account that you can number a book as 5.55 (I've checked). |
|
12-15-2014, 07:06 AM | #11 | ||
Addict
Posts: 245
Karma: 20386
Join Date: Sep 2010
Location: France
Device: Cybook Diva
|
Quote:
Quote:
N. |
||
12-15-2014, 09:30 AM | #12 | |
Grand Sorcerer
Posts: 11,742
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
Given this fact, we are left with finding ways for people to solve the problem in some way within the existing structure. This is why I added grouped search terms several years ago, to provide a way to search across multiple columns using one lookup name. I am willing to add template functions to improve things if a) their semantics can be described in a sentence or two and b) they are generally useful. A function to return the values in a grouped search term might be one example. |
|
12-15-2014, 10:48 AM | #13 | ||
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Quote:
And to really get all the stories in perspective, especially in a short story collection, there is not and never will be any replacement for just splitting the darn things already, like normal people do. The OP at least had an actual logical reason for wanting tag-like series', at least at first -- for crossovers, or things with subseries I guess. The problem is as chaley said, and the reason why Kovid shoots this down every time, the challenge of implementation is WILDLY disproportionate to its return value, making it unlikely anyone will ever care enough to fix this minor niggle. Quote:
Either way, having a stable decimal value allows you to make things consistent. |
||
12-15-2014, 10:58 AM | #14 |
Connoisseur
Posts: 78
Karma: 52
Join Date: Nov 2014
Device: Kindle
|
Reply from OP
To answer some questions:
1) I still think that natural built-in support for multiple series is the only "good thing to do". Everything else is plain hacking, with (IMO very) limited functionality. a) for example, if I enter book into Series1 #1 and Series2 #13 using the hacks above - would I see Series2 in series browser? Would search find it? Would grid sort by it? etc. b) similar code and approach already has to be 'inside' for multiple authors and multiple tags for one book. Yes, there should be some additional code here and there but I won't expect weeks of rocket engineering there... (Also could be done part-by-part, starting with silent update of internal db access functions) 2) I suppose my float vs integer.integer was replied by someone up there. For calibre now, 1.1 and 1.10 is the same and as someone wrote, one would have to plan in advance to accomodate sub-series number first (as 1.01 a 1.10). Which help store some stories or additional material indexes between 'main' books of series. So integer.integer is different and sorts differently than float (which is what I think calibre uses atm) 3) Similarly, [0] could be omitted from displaying, solving my beef with it 4) As I originally wrote, series ranges 1-3 could be stored as #1, #2, #3 - I still stand my ground here, but there is no problem to make gui join consecutive records as 1-3 and also allowing entering 1-3 as range (and internally storing as 1, 2, 3). Again, this could be implemented separately later. 5) I haven't tried the plugin for goodreads metadata, but clearly, it can't get all the data I'd like to see, because it has no way of storing them. It could be sufficient for basic metadata, but I'm not talking basic. I believe everything is about priorities - and since my own priority is to be able to be synchronized with real source of metadata (in my case Goodreads), hearing that something which could be relatively simply done as 'won't implement' is a bit bummer. |
12-15-2014, 11:27 AM | #15 | |||||||
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
|
|||||||
Tags |
feature request, series |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Feature Request: Book #s for Book Sets Within a Series | dclewis | Marvin | 0 | 09-23-2014 11:22 PM |
[Feature Request] Series ID | taosaur | Calibre | 3 | 06-14-2013 11:05 PM |
Feature Request, Series book 3 of [Total] | icq70610 | Calibre | 7 | 12-25-2012 02:29 AM |
Feature request: Ability to put a book in a series without an index number | lunixer | Calibre | 6 | 08-29-2011 11:37 AM |
series metadata feature request | speakingtohe | Calibre | 4 | 07-01-2010 05:58 PM |