We need to set the status of the contacts from flight_passenger or primary to be untracked once the incubation period ends that can be run at the end of every day.

Running rake db:seed throws this error.

Errno::ENOENT: No such file or directory @ rb_sysopen - /Users/user/coronaRM/data/traveller_2.csv
/Users/user/coronaRM/db/seeds.rb:46:in `populate_traveller_from_data_file'
/Users/user/coronaRM/db/seeds.rb:72:in `<main>'

I think there should be a condition for checking if the file exists in the populate_patients_from_data_file and populate_traveller_from_data_file method.

or better these should be moved to a rake task if it is not used for bootstrapping the database.

The bulk of the project was done in a matter of 1.5 days and the requirements evolved with a fast-paced call centre in Pathanamthitta. So the code quality has taken some hits, a lot of logic has leaked on to views and there are lot of unneeded model fields.

This is a long running issue to fix those inconsistencies.

The current user search form searches using id, and can be accessed by everyone. Create a new form in the admin dashboard page that can search through name, phone number, and flight details.

The project could not be analyzed because of build errors. Please review the error messages here. Another build will be scheduled when a change to a manifest file^* occurs. If the build is successful this issue will be closed, otherwise the error message will be updated.

_{This is an automated GitHub Issue created by Sonatype DepShield. GitHub Apps, including DepShield, can be managed from the Developer settings of the repository administrators.}

_{* Supported manifest files are: pom.xml, package.json, package-lock.json, npm-shrinkwrap.json, Cargo.lock, Cargo.toml, main.rs, lib.rs, build.gradle, build.gradle.kts, settings.gradle, settings.gradle.kts, gradle.properties, gradle-wrapper.properties, go.mod, go.sum}

Currently the system is hosted on Heroku and the entire data needs to be exported everyday evening. We need to move this to background dynos to prevent the app from crashing.

Now Panchayat is added as a single field on the users schema. Refactor it out as a separate table with relation to district.

Panchayat: name belongs_to:District

The association should be added with the existing Panchyat field, so as not destroy existing data. The call center executives will enter the data from the dropdown.