SOS implementation in NL backend

[Ajay-Maury]

Sub-ticket of:- https://github.com/Mission-Prerna/prerna-lakshya-app/issues/424

In NL backend creating a new table for SOS reports as school_results_fraud_reports which will include

• id for unique and will be auto incremented
• udise of school
• cycle_id in which school result marked as SOS
• mentor_id of mentor who marked SOS
• is_fraud as a boolean value
• created_at timestamp of creation
• updated_at timestamp

It can be created multiple times for a school by the same mentor and in the same cycle, so no unique combination of these will be there.

Any examiner mark the listed school as SOS wether he had assessed that particular school or not.

[tushar5526]

@Ajay-Maury is working on adding stricter checks. @Ajay-Maury to add a list of checks that will be added.

[karntrehan]

is_fraud will always be true right? Should we have it then?

[Ajay-Maury]

@Ajay-Maury is working on adding stricter checks. @Ajay-Maury to add a list of checks that will be added.

The following points need to be checked before creating an entry in DB:-

• Cycle exists or not
• Cycle started or not
• Cycled closed
• The given school is assessed or not (If needed can be checked for that the particular examiner is assessed that school or anyone else)
• User is examiner or not

Need to confirm:-

• Can examiner make fraud after closing the assessment cycle
• Can any other examiner mark the school result as fraud or only that examiner who accessed (can be checked on BE)
• Can a school that is not nipun in result be marked as SOS

[Ajay-Maury]

is_fraud will always be true right? Should we have it then?

Changed to is_valid for soft deletion

[rohitsamagra]

• Completed and merged