An author page has no series axis: no way to see which series an author has, or to get from the author to one of them

Aperta
#952 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
frontend

Direzione di ricerca

Read fe/src/views/library/CollectionView.vue and fe/src/utils/seriesUtils.ts; the author collection route is /collection/author/:name. The proposed frontend-only shape is a strip of distinct series from loaded book memberships, falling back to catalog Series, with links to /collection/series/:name and counts. Confirm the preferred scope with the issue author first: the post asks which shape maintainers would take, notes multiple open PRs touching the view, and says no implementation has been written.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Reading canary a630572e. The ask this comes from is the common one, "all of series X by author Y". Today the route from an author to a series goes through the library grid grouped by series, or through Add New, because the author page knows nothing about series beyond a per-book label.

What is there:

  • The author page is the generic collection view (fe/src/views/library/CollectionView.vue, route /collection/author/:name). Series shows up only as text on each card, from formatSeriesMemberships (fe/src/utils/seriesUtils.ts:27), and as a sort option. Nothing on the page aggregates across books.
  • For owned books the data is already loaded: AudiobookSeriesMembership carries SeriesName, SeriesAsin, IsPrimary and SortOrder, and a book can hold several. Catalog books in the author response carry only the single Series string (MetadataController.Models.cs:84), with no memberships and no ASIN.
  • A series has its own collection page, with a hero, cover mosaic, monitoring and a total count (CollectionView.vue:99-200), reached from the library grid's series grouping (AudiobooksView.vue:91-92) or through GET api/v1/metadata/series/books (MetadataController.cs:352). The destination exists. The link from the author to it is what is missing.

For lineage: Readarr does not group the author's book list by series. It keeps a flat Books tab and a separate Series tab on the author page, and each series links to its own view where the whole series can be monitored. I would follow that rather than group the main list, for two reasons in this codebase. Sectioning here happens after pagination (paginatedAudiobookSections partitions the 50-item slice), which only works today because the in-library sort keeps the two availability sections contiguous, and series would straddle page boundaries. And a grouped list would key owned books off the membership table and catalog books off the single string, so adding a book would silently move it between groups.

The smallest shape I can see is a strip above the list with the distinct series names from the loaded books' memberships, falling back to the catalog Series string, each one a link to /collection/series/:name with a count. Frontend only, no new API. It covers the series the author response already knows about, which is the case in the ask. A fuller version would be an endpoint that returns an author's series from Audible, so that a series with nothing in the library yet also appears, at the cost of extra catalog round trips.

Is a series strip on the author page something you would take, and in which of those two shapes? I have not written either. CollectionView.vue has several open PRs on it (#673, #724, #725, #841, #884, #885, #887), so I would rather not put a diff across it uninvited. If you would take the strip, say so and I will send it once those settle, or leave it to whoever is already in that file.

Disclosure: drafted with Claude Code at my direction; I read the cited code at the stated commit and reviewed this before posting.

Lingua principale
C#
Stelle
901
Fork
70
Merge medio
16h 27m
PR unite (30g)
60

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Listenarrs/Listenarr

Tutte le issue di Listenarrs/Listenarr

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.