HAS_MUSIC_GENRE Party Category

Description

Connects a :Representation node to a :MusicGenre.

This relationship can also be used to connect a party of role EventSeries to a :MusicGenre.

Label

:HAS_MUSIC_GENRE

Valid nodes

From	Relationship	To	Cardinality
Representation A node with the :Representation label with an active REPPED_AS relationship to a :RepArea { name: "Musician"} node	:HAS_MUSIC_GENRE	MusicGenre A node with the :MusicGenre label	1..n
EventSeries A node with the :EventSeries label	:HAS_MUSIC_GENRE	MusicGenre A node with the :MusicGenre label	1..n

Properties

HAS_MUSIC_GENRE uses the standard relationship properties.

CREATE

1. If the :Party does not have a :Role of type Client or Talent, reject the request.
2. If the :Party already has an active relationship to a :MusicGenre of the same name, reject the request.
3. The :Party or :EventSeries must have at least one active :HAS_MUSIC_GENRE relationship

DOESN'T THIS APPLY ONLY TO TOURING ARTISTS?

For :MusicGenre you might think we would require that the :Party have an active REPPED_AS relationship to a :RepArea { name: "Musician"} or whatever is appropriate. In practice this will cause much engineering to keep track of activating and de-activating genres based on :RepArea, as well as be invalid for talent roles where we do not represent the party at all.

UPDATE

The relationship can be freely updated by DMO personnel, except for the id property, within the bounds of the other global business rules described elsewhere.

DELETE

A DELETE operation is treated as a deactivation.

Examples