django project

MODELS (10): You need to create three classes with CASCADING relationship. An example would be: Music Genre > Album > Song. Where each album belongs to a music genre and each song belongs to an Album. Each of those objects when printed or shown in the database should be shown in the following form “id – title” where title (or name) is a charfield you have to specify in the class of that object. You may print them in any way you want as long the string representation of the object starts with id-title (e.g. <id> – <AlbumName> Artist). You should have a VIEWS (30): You are going to create a template for viewing all items in a given list. So since you have created three tables in step 3, you have to specify three url patterns for them. Each url pattern should be <application name>/<table name>. For example, if the url pattern is “music/albums” then the view function should give a context to the template which in turn lists all the albums in the application called “music”. Moreover, you have to have functions that capture the items ids too. For example, if the url is music/albums/1, that should take the user to the details page of the album with id 1. Again, you have to use templates and contexts. If you do not use templates, you are not going to get the grade, and actually you are not going to be able to effectively do the next steps otherwise URLs (30): This is just an example, namings could be different, but patterns should be the same. music/genres >> lists all genres in your database music/albums >> lists all albums in your database music/songs >> lists all songs in your databse music/genres/pop >> show the details of that genre (if any) and list all albums of “pop” genre music/albums/avaz >> show details of that album and list all songs in the album called “avaz” FORMs (60): You should create a form that has a radio-button next to each item in the list of items you show in the previous sections (e.g. list of albums, list of songs …etc). If the user selects one item, there should be a “submit” button also to tweak the BooleanField of that selected item. For example, in class we had is_favorite, so the user could make a ‘song’ favorite or not-favorite using the radio-button and the submission button. If the item is already marked as favorite, then reclicking on the “submit” button should clear the item from being favorite; that is, it is no more favorite