Quote:
Originally Posted by jindroush
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.
|
Yes, yes, and yes.
Quote:
|
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)
|
Oh, good -- it appears we already have someone who knows exactly what to do. I eagerly await your patch.
Quote:
|
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)
|
...or just do what I do, and don't use 0.10 to mean 0.1 (which doesn't exist).
Quote:
3) Similarly, [0] could be omitted from displaying, solving my beef with it 
|
What exactly IS you beef with it?
Quote:
|
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.
|
That is an ugly hack.
Split the book, there is a plugin to do it for you.
Quote:
|
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.
|
For the odd book that actually has multiple series values, you can manually assign it.
Quote:
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. 
|
Yes it is a bit of a bummer, unfortunately that is because you are wrong -- it is not simple. So say the experts.