1norabelle414
We can now use "hours" and "minutes" as units in the Pages field, which is lovely. However, when sorting by the Pages field, the system only counts up the numbers and doesn't take the units into account. The result can look like this, when sorted from least to most:
13 hours; 11 minutes (sorts as 24)
5 hours; 21 minutes (sorts as 26)
13 hours; 16 minutes (sorts as 29)
8 hours; 41 minutes (sorts as 49)
5 hours; 50 minutes (sorts as 55)
10 hours; 58 minutes (sorts as 68)
etc.
It's obviously very difficult to correlate time to pages, but if it's possible to count the hour unit as equaling 60 minute units then at least audiobooks by themselves would sort correctly, which would be a big help.
13 hours; 11 minutes (sorts as 24)
5 hours; 21 minutes (sorts as 26)
13 hours; 16 minutes (sorts as 29)
8 hours; 41 minutes (sorts as 49)
5 hours; 50 minutes (sorts as 55)
10 hours; 58 minutes (sorts as 68)
etc.
It's obviously very difficult to correlate time to pages, but if it's possible to count the hour unit as equaling 60 minute units then at least audiobooks by themselves would sort correctly, which would be a big help.
2LeslieWx
>1 norabelle414: What a lovely little coding problem!! :)
I could fix it in FORTRAN. I could fix it in MATLAB. I could probably fix it in a couple other languages that are of no use to the LibraryThing infrastructure ...
What's under LT's hood, anyway?
I could fix it in FORTRAN. I could fix it in MATLAB. I could probably fix it in a couple other languages that are of no use to the LibraryThing infrastructure ...
What's under LT's hood, anyway?
4jjwilson61
I thought they used Javascript
5bnielsen
>4 jjwilson61: On the client side, but sorting is done on the server side (to be able to serve the contents in small pieces).
6norabelle414
This would be nice to have going into the year-end statistics season :-)

