Add date model to existing Ruby project

Background: We run a holiday listings website where registered users can enter vacation listings and events. Currently they can log into their account and fill out a form in order to create, edit or delete listings. Besides entering ordinary information like title, description or price, they can also specify on which dates their listings are available. Status Quo: Right now, the listing dates are implemented as a JSON object inside the listing model, which will not allow for sorting or searching for specific dates or date ranges. Goal: The contractor should modify our solution with an extra dates model, so that it is theoretically possible to search or filter for events on specific dates or date ranges. The implementation of such a search or filter mechanism in the frontend is not part of this job. Hence, the contractor should implement the database changes as well as the form in the backend view for the registered users. Preferably, the registered users doesn’t need to change the view for defining dates according to the respective listing. Dates should be manageable within the same form where details of the listings are defined (please also see the attached screenshots). If the implementation is easier, using an extra view we need to discuss this beforehand. Specs Overview: - Each listing or event can either have no specific date, one date or more dates (no maximum number of dates). - The registered user can add dates only to his own listings - Dates are alway bind to one specific listing - The registered user can create, edit or delete dates - Dates are displayed on the listing detail page as currently implemented Rails 4 / Ruby 2 / Bootstrap Template DB: Postgres / Heroku