Struct musicbrainz_rs::entity::event::Event
source · pub struct Event {Show 15 fields
pub id: String,
pub name: String,
pub event_type: Option<EventType>,
pub cancelled: Option<bool>,
pub time: String,
pub setlist: Option<String>,
pub tags: Option<Vec<Tag>>,
pub relations: Option<Vec<Relation>>,
pub rating: Option<Rating>,
pub aliases: Option<Vec<Alias>>,
pub annotation: Option<String>,
pub genres: Option<Vec<Genre>>,
pub life_span: Option<LifeSpan>,
pub disambiguation: Option<String>,
pub type_id: Option<String>,
}
Expand description
An event refers to an organised event which people can attend, and is relevant to MusicBrainz. Generally this means live performances, like concerts and festivals.
Fields§
§id: String
§name: String
The name is the official name of the event if it has one, or a descriptive name (like “Main Artist at Place”) if not.
event_type: Option<EventType>
The type describes what kind of event the event is. The possible values are: Concert, Festival, Launch event, Convention/Expo, Masterclass/Clinic
cancelled: Option<bool>
The cancelled field describes whether or not the event took place.
time: String
The time is the start time of the event.
setlist: Option<String>
The setlist stores a list of songs performed, optionally including links to artists and works. See the setlist documentation for syntax and examples.
relations: Option<Vec<Relation>>
Relationships are a way to represent all the different ways in which entities are connected to each other and to URLs outside MusicBrainz.
rating: Option<Rating>
§aliases: Option<Vec<Alias>>
Aliases are alternate names for an event, which currently have two main functions: localised names and search hints. Localised names are used to store the official names used in different languages and countries. These use the locale field to identify which language or country the name is for. Search hints are used to help both users and the server when searching and can be a number of things including alternate names, nicknames or even misspellings.
annotation: Option<String>
Annotations are text fields, functioning like a miniature wiki, that can be added to any existing artists, labels, recordings, releases, release groups and works.
genres: Option<Vec<Genre>>
Genres are currently supported in MusicBrainz as part of the tag system.
life_span: Option<LifeSpan>
The begin and end dates indicate when an artist started and finished its existence. Its exact meaning depends on the type of artist:
-
For a person Begin date represents date of birth, and end date represents date of death.
-
For a group (or orchestra/choir) Begin date represents the date when the group first formed: if a group dissolved and then reunited, the date is still that of when they first formed. End date represents the date when the group last dissolved: if a group dissolved and then reunited, the date is that of when they last dissolved (if they are together, it should be blank!). For listing other inactivity periods, just use the annotation and the “member of” relationships.
-
For a character Begin date represents the date (in real life) when the character concept was created. The End date should not be set, since new media featuring a character can be created at any time. In particular, the Begin and End date fields should not be used to hold the fictional birth or death dates of a character. (This information can be put in the annotation.)
-
For others There are no clear indications about how to use dates for artists of the type Other at the moment.
-
disambiguation: Option<String>
The disambiguation comments are fields in the database used to help distinguish identically named artists, labels and other entities. They are visible in the pages for the entities, and also appear in the search results next to their names.
type_id: Option<String>