starred/audiobookshelf-advplyr

Fork 0

mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-03-02 22:46:55 -05:00

[Enhancement]: "Details View" similar to Windows Explorer #918

New issue

Open

opened 2026-02-20 10:04:44 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 10:04:44 -05:00

Owner

Originally created by @hobesman on GitHub (Jan 26, 2023).

Describe the feature/enhancement

I'd like an optional view where books are listed with one row per book, with a number of customizable columns. The columns to pick from would include the enterable metadata fields as well as things like file size, duration, number of chapters, number of audio files, and perhaps path, too. Album art width. Basically any aspect that abs is aware of, could be an optional column. Perhaps bitrate too if abs scans that.

Then, to be able to pick and choose which columns to display, and in what order, resize them, and then click on a column to sort by that attribute.

Some of these might be useful for finding your next listen, but what I'm picturing it helping me with is metadata managing. Figuring out which books are missing chapters or only have one or two chapters. Which books have low-res art. Which books are 6GB and should be converted down. Which books are missing asin. Missing narrator. Having a series name but missing series number. Lots of possible uses.

With that in mind, it might make sense to limit this to admins, or at least make it an admin's option to decide who to grant this ability to.

Originally created by @hobesman on GitHub (Jan 26, 2023). ### Describe the feature/enhancement I'd like an optional view where books are listed with one row per book, with a number of customizable columns. The columns to pick from would include the enterable metadata fields as well as things like file size, duration, number of chapters, number of audio files, and perhaps path, too. Album art width. Basically any aspect that abs is aware of, could be an optional column. Perhaps bitrate too if abs scans that. Then, to be able to pick and choose which columns to display, and in what order, resize them, and then click on a column to sort by that attribute. Some of these might be useful for finding your next listen, but what I'm picturing it helping me with is metadata managing. Figuring out which books are missing chapters or only have one or two chapters. Which books have low-res art. Which books are 6GB and should be converted down. Which books are missing asin. Missing narrator. Having a series name but missing series number. Lots of possible uses. With that in mind, it might make sense to limit this to admins, or at least make it an admin's option to decide who to grant this ability to.

deekerman added the

enhancement

label

2026-02-20 10:04:44 -05:00

deekerman commented

2026-02-20 10:04:44 -05:00

Author

Owner

@advplyr commented on GitHub (Apr 9, 2023):

Is this the same as #729?
It seems like these should be merged

@advplyr commented on GitHub (Apr 9, 2023): Is this the same as #729? It seems like these should be merged

deekerman commented

2026-02-20 10:04:44 -05:00

Author

Owner

@hobesman commented on GitHub (Apr 9, 2023):

In my mind they're separate. This is more geared toward library/metadata management, whereas the other "description" view is more aimed at browsing for the next book to listen to. Ideally the aesthetic would take precedence over other considerations. Whereas this request is about the ability to sort, to display as much information in as dense a way as possible and still be functional.

Just my thoughts.

@hobesman commented on GitHub (Apr 9, 2023): In my mind they're separate. This is more geared toward library/metadata management, whereas the other "description" view is more aimed at browsing for the next book to listen to. Ideally the aesthetic would take precedence over other considerations. Whereas this request is about the ability to sort, to display as much information in as dense a way as possible and still be functional. Just my thoughts.

deekerman commented

2026-02-20 10:04:45 -05:00

Author

Owner

@advplyr commented on GitHub (Apr 9, 2023):

You see these as being different list views entirely?

@advplyr commented on GitHub (Apr 9, 2023): You see these as being different list views entirely?

deekerman commented

2026-02-20 10:04:45 -05:00

Author

Owner

@hobesman commented on GitHub (Apr 10, 2023):

I do.

One could be called like "Summary view" and one referred to as "Data view" or "table view" or something.

From: advplyr @.>
Sent: Sunday, April 9, 2023 6:20:24 PM
To: advplyr/audiobookshelf @.>
Cc: hobesman @.>; Author @.>
Subject: Re: [advplyr/audiobookshelf] [Enhancement]: "Details View" similar to Windows Explorer (Issue #1444)

You see these as being different list views entirely?

—
Reply to this email directly, view it on GitHubhttps://github.com/advplyr/audiobookshelf/issues/1444#issuecomment-1501275926, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCYJJMAFJVMGBBO4KBZ2O3XANN5RANCNFSM6AAAAAAUHR27FM.
You are receiving this because you authored the thread.Message ID: @.***>

@hobesman commented on GitHub (Apr 10, 2023): I do. One could be called like "Summary view" and one referred to as "Data view" or "table view" or something. ________________________________ From: advplyr ***@***.***> Sent: Sunday, April 9, 2023 6:20:24 PM To: advplyr/audiobookshelf ***@***.***> Cc: hobesman ***@***.***>; Author ***@***.***> Subject: Re: [advplyr/audiobookshelf] [Enhancement]: "Details View" similar to Windows Explorer (Issue #1444) You see these as being different list views entirely? — Reply to this email directly, view it on GitHub<https://github.com/advplyr/audiobookshelf/issues/1444#issuecomment-1501275926>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHCYJJMAFJVMGBBO4KBZ2O3XANN5RANCNFSM6AAAAAAUHR27FM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

deekerman commented

2026-02-20 10:04:45 -05:00

Author

Owner

@stefan786 commented on GitHub (Mar 24, 2025):

Can I +100 this request? I'd love to be able to fine tune my book metadata, and an Explorer like table view would be perfect for that (as opposed to opening every single book and finding the ones in series that are missing a narrator or have deviating info).

Customizable columns would be chef's kiss.

@stefan786 commented on GitHub (Mar 24, 2025): Can I +100 this request? I'd love to be able to fine tune my book metadata, and an Explorer like table view would be perfect for that (as opposed to opening every single book and finding the ones in series that are missing a narrator or have deviating info). Customizable columns would be chef's kiss.