General Planning Implementation Tasks of Managing Playlist in Chinook

[jcareyes]

This task list area will be completed once the implementation plan has been outlined. This area is where one created the task list that is associated with the milestone. The tasks that are outlined in this area, are the tasks that are counted for the milestone.

• [ ] Create Data Models
• Create Queries
  • [ ] Track_FetchTracksBy
  • [ ] PlaylistTrack_FetchPlaylist
• Create Transaction Services
  • [ ] AddTrack
  • [ ] RemoveTracks
  • [ ] MoveTracks
• Create WebPage
  • [ ] #2

[jcareyes]

UI Experience

This comment outlines the action that can happen on the forms. Action are in response to the user interacting with the form, pressing button or controls.

PRG Post Redirect Get

• Using routing parameters {searchType?}/{searchValue?}/{playlistName?}
• PRG clicking the Clear empties bound properties and routing parameters (page only)
• PRG clicking the Fetch will retrieve the existing playlist for the specified playlist name {playlistName?}
• PRG clicking the Fetch Artist Tracks or Fetch Album Tracks will retrieve the tracks for the indicated search and display in a table using routing parameters {searchType?}/{searchValue?}
• Post/PRG clicking the Add(+) on the track will attempt to add the track to the playlist <<<???>>>
• rule: unique track on the playlist
• rule: playlist name needs to be unique for the user
• rule: appended track to playlist
• Post/PRG clicking the Remove Tracks will matter to remove 1 or more tracks from the playlist <<<???>>>
• rule: re-sequence the playlist track numbers leaving no gaps.
• Post/PRG clicking the Move Tracks will attempt to reorganize the order of the playlist: Playlist_MoveTracks(...)

  • rule: all tracks require a re-sequence track number
  • rule: track numbers must be greater than 0
  • rule: track numbers must be unique
  • rule: tracks numbers must not introduce holes

---

Track Selection for Artist or Album and Managing Specified Playlist

[jcareyes]

Data Models

The data models are the C# classes that will be coded in the folder(ViewModels) that holds the data classes in our solution. These classes represent the query class models and the command class model (CQRS)

---

Query Model

Artist and Album Track Fetch

public class TrackSelection
{
    public int TrackID {get; set;}
    public string SongName {get; set;}
    public string AlbumTitle {get; set;}
    public string ArtistName {get; set;}
    public int Milliseconds {get; set;}
    public decimal Price {get; set;}
}

Current Playlist Tracks

public class PlaylistTrackInfo
{
    public int TrackID {get; set;}
    public int TrackNumber {get; set;}
    public string SongName {get; set;}
    public int Milliseconds {get; set;}
}

---

Command Models'

Colors Yellow: Data Coming In Green: Primary Keys being auto generated Blue: Program will be creating Red: Where it can be used

Add Track

No model class, individual parameters

Remove Tracks

UserName and PlaylistName are individual parameters. Requires TrackID list in a List (no data model)

Move Tracks (Re-sequence playlist)

public class PlaylistTrackMove
{
    public int PlaylistTrackID {get; set;}
    public int TrackID {get; set;}
    public int TrackNumber {get; set;} // New Track # 
}

[jcareyes]

Business Processing Requirements

This comment will describe the various methods that will be used for Commands (CQRS) that alter the database. Queries are read only and require on average no complex processing. However, commands require business rules validations and manipulations of one or more tables and/or records. Therefore, the processing of commands should be outlined.

Include the method signature and a bullet list of processes

Add Track

void PlaylistTrack_AddTrack(string playlistName, string userName, int trackID)

• Check track exist (trackID) [Check if the physical track exists in the catalogue collection (track list)]
  • [NO]: add an exception
• Check playlist exist (playlistName, userName)
  • [NO]: add an exception
  • [YES]: check track is not already on playlist.
  • [YES]: add an exception
  • [NO]: generate the next track number
    • If the tracklist does not exist
    • create a new playlist record
    • set track number to 1
    • Add track to playlist (append)
• Check for any errors.
  • [YES]: throw list of all collected exceptions
  • [NO]: save all changes to database