Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Vincent Kars]

If you use a field with multiple values e.g. Artist the tree view will display all individual values.
A nice option to find e.g. all work the artist is involved.



In this example the Artist field contains Gideon Kremer ; MArtha Argerich.
Correct this by editing Martha Argerich in the tree view.



Change MArtha into Martha



Say goodby to the multiple values in the Artist field.
The same happens if you use drag/drop in the tree view.

Now I understand why I lost a lot of information as I do use the tree view often to normalize my tags.

[darichman]

I agree - I have found this to be a major problem for me. The same thing happens if you rename an artist from its pane entry too - all other artist entries in the list are removed. I would go as far as calling this a bug, and a potentially dangerous one, as it isn't clear the change has been made, and its not what one would expect from simply renaming an artist in a list.

Please consider revising list tag editing?

[Vincent Kars]

It looks like they changed a couple of tags from single value to list style without adapting the interface.
I can only second the request to adapt the interface as the current one result in data loss.

[gvanbrunt]

Yikes. Thanks for sharing this. It would have bit me at one time or another.

+1 to fix this. This is really borderline as a bug, but from a UI standpoint is pretty major.

[Matt]

It's intentional that artist is a list field without a full-blown list editing UI.  This is a compromise to provide list functionality without the complexity of list editing.

However, I agree it's unexpected to lose the list on a rename of an existing value.  This will be changed in v18.

[Vincent Kars]

Thanks

I had a look at the People field.
This one supports multiple values and the editing goes right.
I kindly ask you to consider to use this mechanism for the Artist field as well

Vincent

[Matt]

I had a look at the People field.
This one supports multiple values and the editing goes right.
I kindly ask you to consider to use this mechanism for the Artist field as well

As I said above, the edit-style behavior is intentional.

There was a lot of discussion about this when the changes were made, and I think it's a good compromise.

[gvanbrunt]

As I said above, the edit-style behavior is intentional.

There was a lot of discussion about this when the changes were made, and I think it's a good compromise.

I don't have an issue with the edit-style behavior. A warning that the change may break things would be fine. Or better yet it only affected the the one item you were changing.

[Matt]

The reported problem is fixed here:
http://yabb.jriver.com/interact/index.php?topic=74446.0

[Vincent Kars]

Thanks

Vincent

[Vincent Kars]

It works if one edits a value in place (F2) in the navigation tree.
The moment one does a drag/drop e.d. MArtha Argerich on Martha Argerich all multiple values are destroyed and replaced by a single value.
I kindly ask you to correct this as well.

[Matt]

A drag-n-drop is a set, not a rename.

In other words, dragging 'Bob Dylan' to 'Abba' should change the files to 'Abba', not add 'Bob Dylan' as one of the artists.

[Vincent Kars]

Sorry but I disagree completely.

I have a tag list style People
I have a tag list style Artist.

If I drop MArtha on Martha in People , the value is added to the multiple values
If I drop MArtha on Martha in Artist , the value destroys all multiple values.

In all common decency, one cannot expect the user to know this
Both implementations I do think counter intuitive
Both implementations have an highly unwanted impact on the consistency of the data

I kindly ask you to consider implementing
-   Consistent behavior in all list style tags
-   Do a replace in case of a drag/drop