Data talk:Performances.json

Multiple-year events vs. annual events

The multiple-year events currently being shown at Performances just "happen to be" events that span multiple years in the data set. There's not much difference between, say, "Allsang på Grensen" and the "Kongsberg Jazz Festival", except that the former only uses that one label for every instance and the latter uses different labels for different years. There's also little difference between those things and, say, "God Sommer Norge", except that she only appeared on that show once. So I think for consistency all events that happen more than once, regardless of whether she participated in them more than once, should be listed under their generic names (e.g., "Kongsberg Jazz Festival") with a separate field identifying which instance of the event we are talking about (e.g., "2017" for the KJF, maybe "Season 6" for NGT, and "Larkollen", etc., for "Christmas concert tour 2017"). But see also my comment in the next section. - dcljr (talk) 21:19, 16 August 2025 (UTC)

Splitting event field

The "event" field is currently doing a lot of work here. I think we should consider breaking down the information into more narrowly-defined fields, like "city", "country", "venue", "social" (for TikToks, etc.), and so forth, reserving "event" for 'real' event names, like "Rotary Club Convention", and let Module:Performances worry about constructing unique labels (used as linked page titles) depending on which information is present. (The result could be overridden when necessary by using another field.) I assume it is possible somehow to use a "computed" field in keys= (i.e., a field constructed within the module itself, not in the call to the module)? That way users wouldn't need to figure out / remember any naming conventions when adding information, so long as they understand the meanings of the separate fields. - dcljr (talk) 21:19, 16 August 2025 (UTC)

I basically agree to your suggestions, also in regards to the previous section. But as just explained in Talk:Performances#Repeated_'id's, I think it's more a configuration task, and a construct to combine those individual fields could be done there. It's possible to use a template for that to ease the config, and that template could then also be used elswehere when linking to the event entry. I think we could make the id generation optionally independent from what is displayed in the table header, though that might have the disadvantage that it becomes more difficult/less obvious what is the right id to link to it. --Most2dot0 (talk) 09:17, 17 August 2025 (UTC)

Performance != video

Currently we acknowledge (in the structure of Data:SongsToVideos.json) that a song can have many videos associated with it and that many songs can be in a single video. But what about the fact that many videos can document the same performance (i.e., videos shot by different people at the same time)? How is that going to be handled? Seems like this will require another dataset (and a decision on a standard naming scheme for performances). - dcljr (talk) 21:19, 16 August 2025 (UTC)