Prompt for the TrackApp

Please create a React-JS application for the TrackModule. The application  has to offer the following views for the user interface: 
    1. AlbumView 
    2. ArtistView 
    3. CreatorToolUsageView 
    4. PodcastEpisodeView 
    5. StreamEventView 
    6. TrackView 
    7. TrackArtistView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 7 views are defined below.

1. The AlbumView must contain the following fields: 
    - name: Label   type: Label 
    - name: ReleaseDate   type: DATE 
    - name: Title   type: STRING 
The data source for the [Label] select control should be loaded from the relative URL: 
    "/CountryService/label"   (HTTP-GET) 
An existing Album entity should be loaded from the relative URL: 
    "/TrackService/album/{id}"   (HTTP-GET) 
If a new Album entity has been created, the new entity should be posted to the relative URL: 
    "/TrackService/album"   (HTTP-POST) 
If an existing Album entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrackService/album/{id}"   (HTTP-PUT) 
If an existing Album entity has to be deleted, the following relative URL should be called: 
    "/TrackService/album/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Track columns: 
    - column: Title 
    - column: IsPodcastMusic 
    - column: IsExplicit 
    - column: DurationSeconds 
    - column: Album 
The table should have the title "Tracks" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/track/album/{id}"

2. The ArtistView must contain the following fields: 
    - name: Country   type: Country 
    - name: IsGhostArtist   type: BOOL 
    - name: IsVerified   type: BOOL 
    - name: Name   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing Artist entity should be loaded from the relative URL: 
    "/TrackService/artist/{id}"   (HTTP-GET) 
If a new Artist entity has been created, the new entity should be posted to the relative URL: 
    "/TrackService/artist"   (HTTP-POST) 
If an existing Artist entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrackService/artist/{id}"   (HTTP-PUT) 
If an existing Artist entity has to be deleted, the following relative URL should be called: 
    "/TrackService/artist/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following CreatorToolUsage columns: 
    - column: Podcast 
    - column: Artist 
    - column: UserAccount 
    - column: StartedAt 
    - column: CreatorTool 
The table should have the title "CreatorToolUsages" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/creatortoolusage/artist/{id}" 
Add a HTML table to the view with the following TrackArtist columns: 
    - column: Role 
    - column: Artist 
    - column: SortOrder 
    - column: Track 
The table should have the title "TrackArtists" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/trackartist/artist/{id}" 
Add a HTML table to the view with the following RoyaltyRecipient columns: 
    - column: Label 
    - column: Type 
    - column: Artist 
    - column: NameOverride 
The table should have the title "RoyaltyRecipients" und the data must be loaded from the server with the following relative URL: 
    "/CountryService/royaltyrecipient/artist/{id}"

3. The CreatorToolUsageView must contain the following fields: 
    - name: Artist   type: Artist 
    - name: CreatorTool   type: CreatorTool 
    - name: Podcast   type: Podcast 
    - name: StartedAt   type: DATE 
    - name: UserAccount   type: UserAccount 
The data source for the [Artist] select control should be loaded from the relative URL: 
    "/TrackService/artist"   (HTTP-GET) 
The data source for the [CreatorTool] select control should be loaded from the relative URL: 
    "/PlaylistService/creatortool"   (HTTP-GET) 
The data source for the [Podcast] select control should be loaded from the relative URL: 
    "/CompanyEntityService/podcast"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing CreatorToolUsage entity should be loaded from the relative URL: 
    "/TrackService/creatortoolusage/{id}"   (HTTP-GET) 
If a new CreatorToolUsage entity has been created, the new entity should be posted to the relative URL: 
    "/TrackService/creatortoolusage"   (HTTP-POST) 
If an existing CreatorToolUsage entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrackService/creatortoolusage/{id}"   (HTTP-PUT) 
If an existing CreatorToolUsage entity has to be deleted, the following relative URL should be called: 
    "/TrackService/creatortoolusage/{id}"   (HTTP-DELETE)

4. The PodcastEpisodeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: DurationSeconds   type: LONG 
    - name: HasMusic   type: BOOL 
    - name: Podcast   type: Podcast 
    - name: ReleaseDate   type: DATE 
    - name: Title   type: STRING 
The data source for the [Podcast] select control should be loaded from the relative URL: 
    "/CompanyEntityService/podcast"   (HTTP-GET) 
An existing PodcastEpisode entity should be loaded from the relative URL: 
    "/TrackService/podcastepisode/{id}"   (HTTP-GET) 
If a new PodcastEpisode entity has been created, the new entity should be posted to the relative URL: 
    "/TrackService/podcastepisode"   (HTTP-POST) 
If an existing PodcastEpisode entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrackService/podcastepisode/{id}"   (HTTP-PUT) 
If an existing PodcastEpisode entity has to be deleted, the following relative URL should be called: 
    "/TrackService/podcastepisode/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following StreamEvent columns: 
    - column: Track 
    - column: PodcastEpisode 
    - column: SubscriptionPlan 
    - column: StartedAt 
    - column: Country 
    - column: IsCountedForRoyalty 
    - column: UserAccount 
    - column: DurationSeconds 
The table should have the title "StreamEvents" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/streamevent/podcastepisode/{id}" 
Add a HTML table to the view with the following PlaylistItem columns: 
    - column: AddedAt 
    - column: Track 
    - column: AddedByUser 
    - column: PodcastEpisode 
    - column: Playlist 
    - column: SortOrder 
The table should have the title "PlaylistItems" und the data must be loaded from the server with the following relative URL: 
    "/PlaylistService/playlistitem/podcastepisode/{id}"

5. The StreamEventView must contain the following fields: 
    - name: Country   type: Country 
    - name: DurationSeconds   type: LONG 
    - name: IsCountedForRoyalty   type: BOOL 
    - name: PodcastEpisode   type: PodcastEpisode 
    - name: StartedAt   type: DATE 
    - name: SubscriptionPlan   type: SubscriptionPlan 
    - name: Track   type: Track 
    - name: UserAccount   type: UserAccount 
The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: 
    "/SubscriptionPlanService/subscriptionplan"   (HTTP-GET) 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [Track] select control should be loaded from the relative URL: 
    "/TrackService/track"   (HTTP-GET) 
The data source for the [PodcastEpisode] select control should be loaded from the relative URL: 
    "/TrackService/podcastepisode"   (HTTP-GET) 
An existing StreamEvent entity should be loaded from the relative URL: 
    "/TrackService/streamevent/{id}"   (HTTP-GET) 
If a new StreamEvent entity has been created, the new entity should be posted to the relative URL: 
    "/TrackService/streamevent"   (HTTP-POST) 
If an existing StreamEvent entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrackService/streamevent/{id}"   (HTTP-PUT) 
If an existing StreamEvent entity has to be deleted, the following relative URL should be called: 
    "/TrackService/streamevent/{id}"   (HTTP-DELETE)

6. The TrackView must contain the following fields: 
    - name: Album   type: Album 
    - name: DurationSeconds   type: LONG 
    - name: IsExplicit   type: BOOL 
    - name: IsPodcastMusic   type: BOOL 
    - name: Title   type: STRING 
The data source for the [Album] select control should be loaded from the relative URL: 
    "/TrackService/album"   (HTTP-GET) 
An existing Track entity should be loaded from the relative URL: 
    "/TrackService/track/{id}"   (HTTP-GET) 
If a new Track entity has been created, the new entity should be posted to the relative URL: 
    "/TrackService/track"   (HTTP-POST) 
If an existing Track entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrackService/track/{id}"   (HTTP-PUT) 
If an existing Track entity has to be deleted, the following relative URL should be called: 
    "/TrackService/track/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following StreamEvent columns: 
    - column: Track 
    - column: PodcastEpisode 
    - column: SubscriptionPlan 
    - column: StartedAt 
    - column: Country 
    - column: IsCountedForRoyalty 
    - column: UserAccount 
    - column: DurationSeconds 
The table should have the title "StreamEvents" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/streamevent/track/{id}" 
Add a HTML table to the view with the following RoyaltyLine columns: 
    - column: StreamsCount 
    - column: RoyaltyRecipient 
    - column: AmountUsd 
    - column: AmountEur 
    - column: Track 
    - column: RoyaltyStatement 
    - column: SharePercent 
The table should have the title "RoyaltyLines" und the data must be loaded from the server with the following relative URL: 
    "/MarketRegionService/royaltyline/track/{id}" 
Add a HTML table to the view with the following PlaylistItem columns: 
    - column: AddedAt 
    - column: Track 
    - column: AddedByUser 
    - column: PodcastEpisode 
    - column: Playlist 
    - column: SortOrder 
The table should have the title "PlaylistItems" und the data must be loaded from the server with the following relative URL: 
    "/PlaylistService/playlistitem/track/{id}" 
Add a HTML table to the view with the following TrackArtist columns: 
    - column: Role 
    - column: Artist 
    - column: SortOrder 
    - column: Track 
The table should have the title "TrackArtists" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/trackartist/track/{id}" 
Add a HTML table to the view with the following TrackLabel columns: 
    - column: Label 
    - column: Track 
The table should have the title "TrackLabels" und the data must be loaded from the server with the following relative URL: 
    "/CountryService/tracklabel/track/{id}"

7. The TrackArtistView must contain the following fields: 
    - name: Artist   type: Artist 
    - name: Role   type: STRING 
    - name: SortOrder   type: LONG 
    - name: Track   type: Track 
The data source for the [Artist] select control should be loaded from the relative URL: 
    "/TrackService/artist"   (HTTP-GET) 
The data source for the [Track] select control should be loaded from the relative URL: 
    "/TrackService/track"   (HTTP-GET) 
An existing TrackArtist entity should be loaded from the relative URL: 
    "/TrackService/trackartist/{id}"   (HTTP-GET) 
If a new TrackArtist entity has been created, the new entity should be posted to the relative URL: 
    "/TrackService/trackartist"   (HTTP-POST) 
If an existing TrackArtist entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrackService/trackartist/{id}"   (HTTP-PUT) 
If an existing TrackArtist entity has to be deleted, the following relative URL should be called: 
    "/TrackService/trackartist/{id}"   (HTTP-DELETE)