Rails application development with rails_admin - New Feature

An existing ROR application (ruby 2.0, rails 4.1) that requires a new feature. Must be familiar with rails_admin. Feature brief: "Background: Customers provide updated data each year in paper based form. The administrators then update the data in the platform manually. We need to make this process quicker and more efficient. There are three steps overall - Yearly annual forms creation (rake task). Annual form updates (draft vs ready changes). Data update (including statistics). *Annual Rake Task User Story* -As a developer, I can run a rake task to create the annual returns for the current year, which will copy the relevant data from the clubs and their management committee and relationships into the annual form tables. It needs to archive existing annual returns (mark any items that are still status pending as archived). The new annual returns will then be available to process in the app. *Listing User Story* -As a user I can see a list of club annual returns for the current year. On this index page, we will show club name, club number, a status (Pending Update and Updated), Year (created_. I can filter by club name, number and status. A link to the annual form will be available (no other links). *Annual Return Form User Story* -As a user I have specific page that allows me to change the existing details of a club. -If changes are not ready to be applied I can save the "annual update" as a draft. -If changes are ready, then I can set these changes as “Ready!” (save and merge - will need a secondary confirmation popup). -Ability to update the management committee the same way we do it for an entity. -Once approved the changes will then update the associated club and committee members. Architecturally -> We need to create the equivalent of the entity, entities_user and users models and create annual versions of these. I.e annual_entity, annual_entities_user, annual_users. A copy of all the clubs (only clubs will be updated annually and the details needed for the annual returns i.e not all fields) and their managing committees will be made into this via a rake task (I.e rake run annualreturns:create(2016) will copy the relevant current club details into the annual tables). We can then subsequently update these via rails admin. A standard rails_admin index page, but the links (not the standard edit, delete ones) will then take them to a special annual return form (this will need to be a rails “custom action”). Save as draft will just update the annual return tables. Clicking on Ready should then go and find the original entity and override the attributes with the changes made. We should track the user who made the change and ensure that the papertrail changes is the same person."