You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On an author's page, the series and works are currently listed by descending publication date by default while works are ordered by ordinal number in a series both on the series page and with their cover miniatures on the author page.
I'd like to propose changing the default sort order to ascending publication date on the author page to harmonize with how the works are handled in a series. (Reverse ordering of works in a series would not make much sense at all.)
If users disagree, it could be made a user setting. But I think this would be the more intuitive default.
The text was updated successfully, but these errors were encountered:
The idea behind author's work descending order was to see the "hottest" release first, as it feels more relevant to see which book that have been out in 2024, than the one in 2006.
But I see your logic, the same as a director's filmography, you start by the oldest movie, logically.
I gave it a try with b2ba527. A user setting seems a bit too much considering the work on the table these days (shall it be the same setting for all entities or only for works, a setting for the series too,).
Do you mind testing the change and report anything incoherent here ?
On an author's page, the series and works are currently listed by descending publication date by default while works are ordered by ordinal number in a series both on the series page and with their cover miniatures on the author page.
I'd like to propose changing the default sort order to ascending publication date on the author page to harmonize with how the works are handled in a series. (Reverse ordering of works in a series would not make much sense at all.)
If users disagree, it could be made a user setting. But I think this would be the more intuitive default.
The text was updated successfully, but these errors were encountered: