User:Most2dot0/Performances-devel
This is a development version for the table/code based parts of the Performances article. It is unstable, and may not work properly at times.
New prototype implementations
Video lists
Early implementation of a switch to support mulitple example videos per performance. Uses "videos"[1]."url" instead of just "url" to access the video.
Todo: also move video specific data into the list, that's currently only "duration", but likely a video specific "comment" should be possible as well.
"Context" field to replace "event" entries
Instead of reading "event", the name of the event is established from the "context" field, which holds an array of 3 to 5 strings. These form a hierarchial description of the context in which the performance took place. The idea is to have this divied into a more abstract part, and a more concret part. The abstract one is:
- Category
- Group (optional)
The concrete one is: (at least one of the first two need to be defined)
- Occasion
- Occurance
- Segment
These actually overlap, so there should be either the "group" be defined, or the "occasion", but not both. BTW, the names were choosen to work for a variety of different contexts, and in itself are not that important. The reason for this overlap is, that there are event series (like the Kongsberg Jazz Festival) where it makes sense to have 3 hierarchies for the occasion (the festival as it exisits over the years), the occurance (an instance, named by the year), and a segment (an individual stage mulit-song performance). On the other side, we have a lot of individual occurances that don't have a similar close umbrella that makes sense to use for grouping (at least not when considering Angelina's participation in other occurances of the same occasion, e.g. a specific TV program). For those occurrences it makes sense to group them under a more abstract theme, like "Guest occurance", "Interview", or "Feature".
Flat listing of current context entries
Error fetching JSON: Page not found or empty
Display example in "All events" table
| All Events | |||
|---|---|---|---|
| Category: Group | |||
| Group • Occurance A [2 Items] | |||
| Group • Occurance-B Segment [1 Item] | |||
| Category: Occasion | |||
| Occasion Occurance Segment [1 Item] | |||
Outer page links
"Group" and "occasion" are handled differently when it comes to construct the links to other wiki pages, so typcially potential articles about the occassion, occurance and segment. There are actually up to three different links created, which concatenete the three items with a blank.
Please hover with the mouse of the verious entries of e.g. #ev Concert Kongsberg Jazz Festival below to get the idea.
Inner page links
"Group" and "oocasion" are handled the same, when it comes to links within this page, so typically from one table to annother. These links are slightly differently displayed, though: between a "group" and an "occurance" there will be a bullet used as speparator, while between an occasion and occurance only a blank will be used.
Also, here occassion and segment are currently always combined, as are the "category" and the "group" or "occasion".
The "Events by year" table does not distighuish segements, and has a link to the correspondig category/group or category/occasion combination in the "All Events" table.
Avoidance of duplicate ids
To avoid duplicate id's, the "All events" table has prefixes to id's of "ev_" and "oc_", and the "Events by year" table uses the year as a prefix.
Context aliase
Since in some instances an entry fits well in more than one group/occasion, a context alias was defined, and has some minimal support from the implementation. So for example, the "Concert/Festival" group can have a link to the "Kongsberg Jazz Festival", which is situated parallel to it in its own "Concert/Kongsberg Jazz Festival" occasion. Similar, the Las Vegas concerts have been grouped together by having "Las Vegas" as an occasion (might be to much, given that Allsang pa Grensen was not), but there are alias links in the "US concert" group.
Further ideas
For a similar reason, a tag system could be introduced. Performances entries could have a "tag" field that holds a list of strings, which could the be used to created tables of events or songs based on these tags.
By event
The tables here include many "pseudo-events", like "Socials", referring to the social media accounts of Angelina and her family members.
See also our list of events Angelina has performed at, which should be limited to "real-world" things like concerts, festivals, and the like.
All Events
[view table data] [edit table data]
Error fetching JSON: Page not found or empty
Events by year
[view table data] [edit table data]
Error fetching JSON: Page not found or empty
By song
See also our list of songs Angelina has sung.
