can_be_archived?() in the Item class

• should return true if published_date is older than 10 years
• otherwise, it should return false

• List all music albums
• List all genres (e.g 'Comedy', 'Thriller')
• Add a music album

All data should be preserved by saving collections in .json files.

• books.json
• labels.json

The following options should be available:

• List of games
• List all authors (e.g. 'Stephen King')
• Add a game

Move json into folder data.

Hello there 🙋‍♂️,

Thanks for taking the time to review our project.

• This is the link to our Kanban Board.
• We are 3 team members.
• Team member 1 is @eduardosancho .
• Team member 2 is @aimemalaika .
• Team member 3 is @Bondok6 .

Delivery of the Capstone Project for Microverse.

• Refactor the structure and organize our project.
• Do a final test of the project and make sure everything works as expected.

• All data should be preserved by saving collections in [file_name].json files.

can_be_archived?() in the Book class

• should override the method from the parent class
• should return true if parent's method returns true OR if cover_state equals to "bad"
• otherwise, it should return false

• add_item method in the Genre class
  • should take an instance of the Item class as an input
  • should add the input item to the collection of items
  • should add self as a property of the item object (by using the correct setter from the item object)
• can_be_archived?() in the MusicAlbum class
  • should override the method from the parent class
  • should return true if parent's method returns true AND if on_spotify equals true
  • otherwise, it should return false

Create a schema.sql file with tables that will be analogical to the structure of the classes that you create

• games table (add all properties and associations from the parent Item class as table columns)
• authors table

Create a Book class in a separate .rb file.

• Create a Label class with an association to the Item class (in a separate .rb file).
• All Book class properties visible in the diagram should be defined and set up in the constructor method.
• All Label class properties visible in the diagram should be defined and set up in the constructor method.

Implement methods:

• add_item method in the Label class
• should take an instance of the Item class as an input
• should add the input item to the collection of items
• should add self as a property of the item object (by using the correct setter from the item object)

Implement methods:

• add_item method in the Author class

  • should take an instance of the Item class as an input
  • should add the input item to the collection of items
  • should add self as a property of the item object (by using the correct setter from the item object)

• can_be_archived?() in the Game class

  • should override the method from the parent class
  • should return true if parent's method returns true AND if last_played_at is older than 2 years
  • otherwise, it should return false

Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:

• music_albums table (add all properties and associations from the parent Item class as table columns)
• genres table

• All Item class properties visible in the diagram should be defined and set up in the constructor method. Exception: properties for the 1-to-many relationships should NOT be set in the constructor method. Instead, they should have a custom setter method created.
• Add all methods visible in the diagram.

Implement startup actions:

• Present the user with a list of options to perform.
• Let users choose an option.
• If needed, ask for parameters for the option.
• Have a way to quit the app.

move_to_archive() in the Item class

• should reuse can_be_archived?() method
• should change the archived property to true if the result of the can_be_archived?() method is true
• should do nothing if the result of the can_be_archived?() method is false

• All Author class properties visible in the diagram should be defined and set up in the constructor method.

• Add unit tests for all implemented methods using Rspec.

The following options should be available:

• List all books
• List all labels (e.g. 'Gift', 'New')
• Add a book

• Create a Game class in a separate.rb file game.rb.

• Create an Author class with an association to the Item class (in a separate .rb file author.rb)

Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:

• books table (add all properties and associations from the parent Item class as table columns)
• labels table

• All Game class properties visible in the diagram should be defined and set up in the constructor method.