Is your feature request related to a problem?
The Audiobooks library can be sorted by Title, Author, Narrator, Publisher, Release Year, Monitored, and Status — but there's no way to sort by when a book was added to the library. After importing a batch of audiobooks, there's no easy "show me my newest additions first" view.
Describe the solution you'd like
A "Date Added" option in the library sort dropdown.
The Audiobook record doesn't currently store a "date added" timestamp, but AudiobookFile.CreatedAt already records when each file was imported. So the lightweight version of this — no schema change — is to sort by the earliest file-import date per audiobook. Books with no file yet (wanted) simply sort last.
Alternatives
A canonical Added timestamp column on Audiobook (the Sonarr/Radarr convention), set on add and backfilled. That gives every book a date including wanted ones, at the cost of an EF migration.
Additional context
I've implemented the lightweight, no-migration version and opened a PR for it — happy to redirect to the canonical-column approach if you'd prefer that. Just wanted to float the idea per CONTRIBUTING before assuming a direction.
Is your feature request related to a problem?
The Audiobooks library can be sorted by Title, Author, Narrator, Publisher, Release Year, Monitored, and Status — but there's no way to sort by when a book was added to the library. After importing a batch of audiobooks, there's no easy "show me my newest additions first" view.
Describe the solution you'd like
A "Date Added" option in the library sort dropdown.
The
Audiobookrecord doesn't currently store a "date added" timestamp, butAudiobookFile.CreatedAtalready records when each file was imported. So the lightweight version of this — no schema change — is to sort by the earliest file-import date per audiobook. Books with no file yet (wanted) simply sort last.Alternatives
A canonical
Addedtimestamp column onAudiobook(the Sonarr/Radarr convention), set on add and backfilled. That gives every book a date including wanted ones, at the cost of an EF migration.Additional context
I've implemented the lightweight, no-migration version and opened a PR for it — happy to redirect to the canonical-column approach if you'd prefer that. Just wanted to float the idea per CONTRIBUTING before assuming a direction.