View Issue Details

IDProjectCategoryView StatusLast Update
0016522MMW 5Tagging / organizing (properties / auto-tools)public2023-09-21 22:19
Reporterpeke Assigned To 
PriorityurgentSeveritytweakReproducibilityalways
Status newResolutionopen 
Product Version5.0 
Target Version5.2Fixed in Version5.0.1 
Summary0016522: Make it easier for users to understand what metadata fits into each field for AudioBooks
Description1. Unlike podcasts where instead of Album we show Podcast and Album is in all UI elements replaced as Podcasts (Including Tree Icons , Search, Properties, ...) Audio Books are handled and Normal Music Albums, We should change that and for Audio Books we should do the same (Including Tree Icons , Search, Properties, ...)

Audio Books should be handled more like Podcasts and have similar options/view where there will be clearly shown what was unplayed, downloaded, Audio Books Directories, ... as it will improve user experience.

Attached both Audio Books and Podcast browser pictures showing differences.

2. In Advanced Search also do not have criteria AudioBook where Podcast is available. Not sure about other types but Audio Books and Podcasts are specific.
TagsNo tags attached.
Attached Files
Audio Books Browsing.png (98,177 bytes)   
Audio Books Browsing.png (98,177 bytes)   
Podcast browsing.png (100,649 bytes)   
Podcast browsing.png (100,649 bytes)   
AudioBooks criteria.png (121,569 bytes)   
AudioBooks criteria.png (121,569 bytes)   
Fixed in build2404

Relationships

related to 0018030 closedLudek Bookmarks indicator not available in List view 
related to 0015998 closedpetr Sort indicators are missing/labelled incorrectly outside of music views 
related to 0017896 resolvedmichal 5.0.1 string review 
related to 0020250 closedLudek Audiobooks: Author field maps to composer 

Activities

rusty

2020-09-17 23:03

administrator   ~0059597

Regarding 1) I think that most users use 'Audiobooks' for anything that is spoken. e.g. for Audiobooks, Comedies, Course Lectures, Speeches, etc.).

With that in mind, we might want to consider the following changes:
Audiobooks --> Spoken Word

Note: I had originally also thought about the following changes, but realized that they would be limiting in terms of how users use MM for the various types of spoken word usecases.
Album --> Book/Album (not great because the string is too big.)
Artist --> Author/Artist (not great because the string is too big but Author would be too limiting)
Album Artist --> Album Author/Artist (string is too big)

rusty

2020-09-18 16:33

administrator   ~0059600

There was some offline discussion re. field names and the conclusion seemed to be that there isn't much benefit in changing most of the names because doing so would make the headers verbose and/or less applicable to other forms of Spoken Word audio (lectures, courses, comedy, etc.).

With that in mind, the suggested approach would be to:
1) take the same approach as is used with Classical music i.e. to include descriptive text next to the following field names in the Properties dialog without changing the headers:
Title (title; episode title)
Artist(s) (narrator; performer)
Album (book title; course title; performance)
Album Artist(s) (author; performer)
Track# (part; chapter)

2) Within AudioBook views that display tracks, add (by default) a play 'Status' indicator column to the left of 'Title' (similar to the indicator that appears in the Podcast > Subscriptions > <SubscriptionName> view).

3) If possible, the 'Play' button that appears in the 'Info panel' of Album views should initiate playback from the last played bookmark. Ideally, it should indicate the 'Next up' track that will continue playing so that the user can see what's going to play.


Possible changes to consider in the future:
4)Change Type and Node:
Audiobooks --> Spoken Audio
note: this isn't critical, and shouldn't be done if it's complicated

Ludek

2021-05-12 16:49

developer   ~0063150

Item 1) is fixed in 5.0.1.2404

rusty

2021-05-12 21:27

administrator   ~0063155

Verified item1) in 2404.

Ludek

2021-10-05 19:30

developer   ~0064990

2) was resolved in course of 0018030

3) Targeted to 5.1

4) Not sure about this wording change, I would rather defer for now