Skills Assignment SA5: Model Associations

Required Demos-n-Deets demos:

• One-to-Many Associations
• Nested-Resource Pages

Optional demos (for now): Everything else in the “Model Associations” section of the Demos-n-Deets.

Active Reading

Follow the general instructions for active reading for the above required demos.

What to submit:

• For the One-to-Many Associations demo, 3 screenshots:
  • sa5-ar-01: one of the Quiz model class,
  • sa5-ar-02: one of the Question model class, and
  • sa5-ar-03: one of the db/schema.rb file.
• For the Nested-Resource Pages demo, 7 screenshots:
  • sa5-ar-04: one of a Question index page that includes several rows in the table,
  • sa5-ar-05: one of the Question new/create form,
  • sa5-ar-06: one of the Question edit/update form,
  • sa5-ar-07: one of the config/routes.rb file,
  • sa5-ar-08: one of the QuestionsController class,
  • sa5-ar-09: one of the app/views/questions/index.html.erb view template, and
  • sa5-ar-10: one of the app/views/questions/new.html.erb view template.

In the above screenshots, code which is too long to be captured in one screenshot may be split up into multiple screenshots.

Important! All screenshots must include your computer’s desktop in the background so that it is recognizable as your desktop. Also, all screenshots of web pages must display the entire URL of the page in the browser’s location bar. (Watch out, as some browsers like to hide parts of the URL unless you click on it.)

Practice Test

Before proceeding, be sure to read the general description and instructions for the practice tests.

Start with the base project on the album-db branch of this repo: https://github.com/memphis-cs/practice-apps-2023-08fall

The aim of this project is enable users to manage a database of music albums. The project already includes an Album model class and a Track model class, as per this class diagram:

Along with these model classes, the app includes the standard resource-CRUDing pages and UI features for Album model objects (but not for Track objects). It also includes model validations and database seeds. (You can ignore the test fixtures and model tests for this assignment.) It is recommended that you initialize and run the base app at this point, so you can see what’s there.

Task to perform:

• Add a one-to-many has-many/belongs-to model association between the Album and Track model classes, as per this class diagram:

• Update the db/seeds.rb file to use the association.
• Add the standard nested-resource-CRUDing pages and UI features for Track objects (as demonstrated in the Nested-Resource Pages demo). Make these pages and features work in a manner consistent with how they worked in the demo.

What to submit:

• sa5-pt-01: Screenshot of the code for the Album model class
• sa5-pt-02: Screenshot of the code for the Track model class
• sa5-pt-03: Screenshot of the code in the db/schema.rb file (after all migrations have run).
• sa5-pt-04: Screenshot of the code in the db/seeds.rb file
• sa5-pt-05: Screenshot of the browser displaying the Track index page, including several rows in the table
• sa5-pt-06: Screenshot of the browser displaying the Track new/create form
• sa5-pt-07: Screenshot of the browser displaying the Track edit/update form
• sa5-pt-08: Screenshot of the code in the config/routes.rb file
• sa5-pt-09: Screenshot of the code in the TracksController class
• sa5-pt-10: Screenshot of the code in the app/views/tracks/index.html.erb view template
• sa5-pt-11: Screenshot of the code in the app/views/tracks/new.html.erb view template

In the above screenshots, code which is too long to be captured in one screenshot may be split up into multiple screenshots.

Important! All screenshots must include your computer’s desktop in the background so that it is recognizable as your desktop. Also, all screenshots of web pages must display the entire URL of the page in the browser’s location bar. (Watch out, as some browsers like to hide parts of the URL unless you click on it.)

Explanation Video

Before proceeding, be sure to read the general instructions for the explanation videos.

Start with the base project on the basketball-roster-editor branch of this repo: https://github.com/memphis-cs/practice-apps-2023-08fall

The aim of this project is enable users to create and edit basketball team rosters. The project already includes a Team model class and a Player model class, as per this class diagram:

Along with these model classes, the app includes the standard resource-CRUDing pages and UI features for Team model objects (but not for Player objects). It also includes model validations and database seeds. (You can ignore the test fixtures and model tests for this assignment.) It is recommended that you initialize and run the base app at this point, so you can see what’s there.

The video can begin after you have cloned, initialized, and run the base app.

Task to perform:

• Add a one-to-many has-many/belongs-to model association between the Team and Player model classes, as per this class diagram:

• Update the db/seeds.rb file to use the association.
• Add the standard nested-resource-CRUDing pages and UI features for Player objects (as demonstrated in the Nested-Resource Pages demo). Make these pages and features work in a manner consistent with how they worked in the demo.

In the video, be sure to use all features that you create, so that it’s clear that they work. Don’t forget to enter invalid data into the forms.