After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 681567 - Multiple Albums Found dialog is not user-friendly
Multiple Albums Found dialog is not user-friendly
Status: RESOLVED DUPLICATE of bug 674926
Product: sound-juicer
Classification: Applications
Component: interface
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-08-10 00:04 UTC by Steve Rainwater
Modified: 2012-08-10 07:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Steve Rainwater 2012-08-10 00:04:31 UTC
Note: I'm using v3.4.0 but didn't see it in the version dialog so I selected "unspecified" version.

When extracting a CD, I'm sometimes presented with an apparently meaningless dialog that's titled "Multiple Albums Found". It presents a selection box with the name of the album and artist repeated anywhere from two to as many as ten times. To proceed I have to randomly select one of the copies of the name.

My selection doesn't appear to affect the extraction process, so if the it really doesn't matter, why even present the selection to the user? 

On the other hand, if there is actually something important or meaningful going on here, the wrong information is being presented to the user. Is there really some difference between those 10 different selections? Then the information that's *different* is what should go in the dialog, not the information that's the same! For example if it's a question of the same CD with different barcodes or release dates, put the barcode and release date in the dialog so the user a) has some basis to understand why the dialog is there and b) has some information on which to make a selection other picking one at random.
Comment 1 Christophe Fergeau 2012-08-10 07:21:33 UTC

*** This bug has been marked as a duplicate of bug 674926 ***