[mb-users] "Edit All" - Is it problematic to understand?

[Steve Wyles]

On Tue, 18 Jul 2006, Age Bosma wrote:
>
> Not at all, it's not for the sake of changing 'something'. Wasn't this 
> discussion raised because people had issues with this page? Since this 
> appears to be the case I'm trying to help out with suggestions which might 
> improve it. If in the end no better solution has been found than there's no 
> reason to change anything.

Yes, it's a matter of evaluation. Look at it, might it work better if 
slightly changed and not cause another problems. If no better, leave it as 
it is.


>>>> What about:
>>>>   [track name]        [track time] [x] Remove
>>>>   [track artist name]              [x] Change
>>> I like this one. It is much clearer since the checkbox is labelled with
>>> the action it will cause. Then it is not problem that they are in the same

Yes, the label at the side aids the usage. Mistakes are far less likely to 
happen.

> [#] [track name       ] [track time] [G.C.] [x] Remove
>    Review: [Open Edits | All Edits]
>    [track artist name]              [G.C.] [x] Change
>    Review: [Open Edits | All Edits]
>
> -> Acceptable for me as well, this would reduce the width a bit again. The 
> guess case buttons could even be positioned before the review options as 
> well.

One problem here is you can't scan down the list of tracks/artists without 
being distracted by the Review options. It might not be a problem, but it 
needs checking.

There is also another issue (which I've already raised on a ticket), if 
you've already made changes and use the review edits links, you can't get 
back to the edit screen without losing those changes. There is no warning 
that this will happen. if somebody has made a lot of changes and uses 
review edits just to quickly check something, they are going to be really 
pissed!

> If the 'Guess All' button only works for the track titles then I think this 
> should be reflected in its label as well, e.g. 'Guess All Tracks'.

Yup or similar wording.

>
> The section underneath the track listing could use some extra attention as 
> well. E.g. the 'Guess' button looks like it will only apply to the 'Language' 
> field while it does for 'Language' as well as 'Script'. The same goes for the 
> 'Show full lists' button.

Yes, those need moving fractionally to better refer what they are linked 
to.

> The 'Attribute' and 'Language' guess buttons should be consistent as well. Or 
> both 'Guess Attributes'(mind the second upper case) and 'Guess Language' or 
> both just 'Guess'.
> What about:
>
> Release Type    : [type]     Status: [status] [Guess]

I'm concerned about this guess on release type. The submitter is more 
likely to know what the release is than any coding. It is probably worse 
than the submitter actually making a guess at what it is, at least they 
have some insight into where it came from etc. I think the preferences in 
order here should be.

1. The submitter specifically sets it from fact.
2. The submitter makes an educated guess.
3. Allow the code to guess or leave it unknown.

Correcting the wrong type will always need to go to a vote for a 
non-autoeditor, where as, it can always be set from unknown without a 
vote.

Steve