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

Invalid Year.

• Whe users add an item and add the year 2012, it displays invalid year, would be great if we update the placeholder to show to the users how the date input should be entered, or to update the to accept the year in the format 2022, 2012, 2018 etc

Set up Environment

• Set up Linters
• Set up Rspec

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

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

The following options should be available:

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

• Create a Book class in a separate .rb file.
• All Book class properties visible in the diagram should be defined and set up in the constructor method.

Implement methods:

• 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

• Create an Item class in a separate .rb file.
• All Item class properties visible in the diagram should be defined and set up in the constructor method.

• Implement methods:

• Implement
  • can_be_archived?() in the Item class
    • Should return true fi published_date is older than 10 years
    • otherwise, it should return false
  • 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 not do nothing if the result of the can_be_archived?() method is false

The following options should be available:

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

• Add unit tests for all implemented methods.

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

Document your project in a professional way in the Readme file

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

• can_be_archived?() in the Item class
• should return true if published_date is older than 10 years
• otherwise, it should return false
• 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

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

• 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)

• Add unit tests for all implemented methods.

• The following options should be available:
• List all books
• List all labels (e.g. 'Gift', 'New')
• Add a book

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

Implement Methods:

• can_be_archived?() in the Music Album class
  • should override the method from the parent class
  • should return true if the parent's method returns true AND if on_spotify equals true
  • otherwise, it should return false
• Add Unit Testing for all implemented methods

Once you have finished the development of the project, you should record a video presenting the features of the project you built. It is a video with a maximum length of 5 minutes. The content of the video should include:

• A description of the project.
• A demo of the project features.
• You should also highlight some interesting piece of code or something you built that you are very proud of.
• You all should appear in the video and talk about the project.

For recording the video you can use the Zoom recording features while in a call with your peers.

• Create Genre class with an association to the Item class (in a separate .rb file).
• All Genre class properties visible in the diagram should be defined and set up in the constructor method.
• Implement Methods
  • 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)

Implemented:

• Github Project: https://github.com/Diegogagan2587/catalog-of-my-things/projects/1
• Team members: 3 people
• Assignations:
  • Team member #1: @bohaz | Ricardo Martinez
  • Team member #2: @Diegogagan2587 | Diego Vidal
  • Team member #3: @Khaled-Alaa-1 | Khaled Alaa

• add test for all your implemented classes and methods

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

• 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

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

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

• Create a main.rb file that will serve as your console app entry point.
• 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.

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