Data:Performances.json/doc

This is a subpage documenting Data:Performances.json. To change the data, edit that page; to change the data's documentation (seen below), edit this one.

Introduction

This data is the center of the "Angelina Jordan Performances Database". Its primary use is in the "Performances" page, which uses the Module:Performances. But it is also used in other articles, for example in the "2017 Christmas tour" one (also via Module:Performances).

Overall structure

One entry per performance

It consists of a list of performance entries, where there typically is exactly one entry for each act of singing (or playing an instrument) for a single piece of music (i.e. typically a song). This includes song snippets, rehearsals, sing-alongs in possibly even lip-syncing.

There are currently some execmptions to this:

• In some rare cases, where a vocal recording was used for several song versions (like the Piano Diaries and "Artist" versions for "If I Were a Boy", there are currently seperate entries for each version.
• Similar, if a raw recording exists that was also professionally released with a different producation level (like four songs from her 2021 Online Christmas Special, which were streamed and later reworked released on her 2023 Christmas EP.
• If e.g. both a lyrics video and a music video exist from the same track, they also currently have two entries (this should likely be changed).
• If a song is performed sevearal times within a rehearsal session, that was recorded in a single video, seperate entries are not required.

Order of entries

Though the order of the entries typically is not relevant for its rendering (as the data gets sorted there), it is encouraged to follow these rules when adding a performance:

• The overall list is sorted by Song titles (A-Z)
• Within a given song title, the individual performances are sorted chronologically (earliest to latest)

Note, that this should be based on the likely actual order, not on what the date fields actually hold. E.g, if you have two performances, like one from 2014-07-03, and a differnt one, of which you know it was very likely in Nov. or Dec. that year, you'd put that latter also last in the list, even though the sorting by date would positions it earlier (as it's only hast "2014" in its date field.

Entry format

So far, the follwing fields are in use (bold ones are mandatory, and it is encouraged to follow the order listed):

• "song": title of the song exactly as used in the Songs article
• "event": a description of the occasion it was performed. This may include pseudo events, such as "Socials" for Instagram/TikTok posts which were not better classified yet. If the event was an actual event which does or could have it's own article in this wiki, it should have the title of such an article and those follow naming conventions of those.

Note: there is currently a discussion going on on the talk page of the data page about how this field and its content might be handled differently in the future.

• "date": This field should start with the date of the event as precisely as known in ISO format, e.g. "2014", "2024-12", or "2014-12-25". It may have qualifications afterwards, like "?", "+/- 1 month" etc.; these are not strictly governed yet.
• "type": classification of the type of event, please choose on from of the following:
  • "recording" (this is assumed as default if "type" is ommited): a performance recorded, that does not better fit the other possible entries
  • "live": sung truely live, i.e. in front of a studio audiance, or on live TV. In this sense, the performances of her "2021 Christmas show" were not "live".
  • "track": a produced version of a performance, typically released on a (digital) single, EP, or album.
  • "music-video": just what you think
  • rehearsal: something from a practice session
  • soundcheck: someting from the actual sound-check or an on-stage rehearsal
• "pos": To describe the position of a performances with a date, e.g. to describe the order several songs were played in a concert. If two performances cannot be distinguished by the upper fields content alone, this field is required, e.g. for the different performances of most song titles is her 7pm and 9:30pm 2024 Las Vegas concerts. The format of this field is not yet strictly goverend, but should be choosen to be sortable and meaningful. E.g. use "1", "2", ... if the order is known, but "a", "b" is not.
• "with": accompaining musicans; other persons not directly involved in the performance should rather be mentioned in a "comment".
• "comment": for additonal remarks
• "url": Link to the performance in a video. If possible, it should encode start and end times. For YouTube links the end time should be included as "end=<seconds>". All YouTube videos that can be played via the embedded YouTube player should be encoded with "https://www.youtube.com/watch?v=...", even Shorts. Not embedded-playable YouTube videos should begin with "https://youtu.be/..."

Note: there is currently a discussion going on on the talk page to enable multiple video reference for a performance

• "duration": an indication of the length of the recordings, such as:
  • "full": contains entire song (this is the default assumed if ommited)
  • "short": was song in an abbreviated, but closed form
  • "fragment": either sung or recorded only partly