In the end I get two overlapping lists which I mentally have to merge somehow. Currently, I always do that twice: Once using the artist field, once using the performer relationship. ![]() If needed, enhance the relationship framework (like adding an “important performer” checkbox).Īlso, consider searching for all recordings with a certain performer. Again: If those artist strings are really needed, then automatically and dynamically create them as read-only strings from the relationships. That is wasted editor time and an additional source for errors and inconsistency. The need to replicate that info in a poorer way into those artist fields which are there for historic sentiment or whatever doesn’t make any sense to me. On the second point I agree: I want to add the info only once, namely in a structured way as relationships. For the tracks, that’s just how MusicBrainz used to do it and what people preferred to keep doing (It’s also much less effort if you’re dealing with a compilation, for example - I definitely wouldn’t want to waste time selecting the appropriate composers and performers for every track).ĭoes it make ontological sense then to associate a release with someone who had nothing to do with the release itself? Come on. It doesn’t make ontological sense to associate a recording with someone who had nothing to do with the recording itself. It just isn’t a single person, it comprises the Conductor, Performers/Orchestra/Choir on the piece. All music players have an album artist and track artist fields and these need a value, including for classical so make sense for MusicBrainz to at least try to generate these values.Īnd I do not agree there is no such thing as a Track artist for Classical, there is. Similarly it is more complex for applications to try and decode relationships than just use the standard fields. So using more relationships (at least with the current UI) is not going to make things any easier. Yes it can and I use them in a very similar way in SongKong/Jaikoz as well.īut look at the answers on your How to help people with classical editing? post, the majority complain about the UI and the difficultly of adding relationships, because adding a relationship is more difficult than simply filling in a field that has been presented such as Track Artist. Why so? All the data could be generated from relationships and put in the right places if so desired
0 Comments
Leave a Reply. |