by ZvezdanD » Mon May 25, 2009 10:22 am
onenonymous wrote:Until ZvezdanD adds support to enable the semicolon as a field separator and use each values as a sub-node (hint hint
) you'll have to try it some other way. Easiest is probably ZvezdanD's suggestion to use a Classification field
...
Another possibility, although more complicated is to create multiple MagicNodes using each language as it's own filtered group.
Thanks for clarifying this, you are much better explaining it than me. However, I think you didn't understand my explanation why it is not possible with Magic Nodes to get multiple values from the Custom field. It is not a problem with a support for separators. You could already use a semicolon as a separator. For example, if I have a field organized like this: vocal:Bono; guitar:The Edge; bass:Adam Clayton; drums:Larry Mullen, Jr. I could use the following mask and get displayed nodes with guitarists: Guitarists\<Custom 1|Exclusive Right of
|Right until:;>
However, you cannot use such mask to display same track for two or more guitarists in two or more sub-nodes, because Custom field is not natively multi-item field. The point is - you could have several values of different type separated with some character(s), but you cannot have multiple values of same type. I cannot add a support for such thing. This is something which MM developers should do and because of that I wrote that I give a vote for this requirement. You know, every existing multi-item field is linked with corresponding tables: Artist, Composer, Conductor and Lyricist fields with ArtistsSongs and Artists tables, Album Artist field with ArtistsAlbums and Artists, Genre with GenresSongs and Genres, Tempo, Mood, Occasion and Quality with ListSongs and Lists. Custom fields are not linked with any additional table. If we want to have it multi-item, MM devs should define a new table(s) for individual items. But, since this is custom field and different people put different things into it, I suppose it could be very hard to use it as a multi-item field, so I hardly believe that MM will ever add support for such thing.
So, currently you have only two possibility with Magic Nodes to get multi-item values for some data that not belongs to some natively multi-item field: 1. you could use some existing multi-item field as a replacement, or 2. you could use the Group option and define one mask for each item using the Filter qualifier (if you have many languages, you would have many masks, as onenonymous explained).
[quote="onenonymous"]Until ZvezdanD adds support to enable the semicolon as a field separator and use each values as a sub-node (hint hint :-)) you'll have to try it some other way. Easiest is probably ZvezdanD's suggestion to use a Classification field
...
Another possibility, although more complicated is to create multiple MagicNodes using each language as it's own filtered group.[/quote]
Thanks for clarifying this, you are much better explaining it than me. However, I think you didn't understand my explanation why it is not possible with Magic Nodes to get multiple values from the Custom field. It is not a problem with a support for separators. You could already use a semicolon as a separator. For example, if I have a field organized like this: vocal:Bono; guitar:The Edge; bass:Adam Clayton; drums:Larry Mullen, Jr. I could use the following mask and get displayed nodes with guitarists: Guitarists\<Custom 1|Exclusive Right of:guitar:|Right until:;>
However, you cannot use such mask to display same track for two or more guitarists in two or more sub-nodes, because Custom field is not natively multi-item field. The point is - you could have several values of different type separated with some character(s), but you cannot have multiple values of same type. I cannot add a support for such thing. This is something which MM developers should do and because of that I wrote that I give a vote for this requirement. You know, every existing multi-item field is linked with corresponding tables: Artist, Composer, Conductor and Lyricist fields with ArtistsSongs and Artists tables, Album Artist field with ArtistsAlbums and Artists, Genre with GenresSongs and Genres, Tempo, Mood, Occasion and Quality with ListSongs and Lists. Custom fields are not linked with any additional table. If we want to have it multi-item, MM devs should define a new table(s) for individual items. But, since this is custom field and different people put different things into it, I suppose it could be very hard to use it as a multi-item field, so I hardly believe that MM will ever add support for such thing.
So, currently you have only two possibility with Magic Nodes to get multi-item values for some data that not belongs to some natively multi-item field: 1. you could use some existing multi-item field as a replacement, or 2. you could use the Group option and define one mask for each item using the Filter qualifier (if you have many languages, you would have many masks, as onenonymous explained).
