Crime Tracker Logic

---

This contain the backend logic of crime-tracker client app.

This system is made up of two different users having different roles admin and officer.

The system can have multiple admins having level of permissions to take certain actions.

Before allowing other officers to get registered into the system, officer are sent a one time code which would be used when creating a new account. If the code expires, request would lead to failure making it more secure from allowing fake users signing up as a officer.

The admin would then be able to grant officer request or reject request.

Permissions

This are the list of permissions present in the system

• Admin

  • Grant other officers requests when registering.
  • View all officers within the system.
  • Engage in predicting crime cases.
  • View all crime evidence.
  • Assign case to be taken care off by other officers within the system.
  • Delete all case only admin not officer .
  • Delete officers from the system.
  • Add Evidence for a particular crime case.

• Users

  • View all officers within the system.
  • Engage in predicting crime cases.
  • View all crime evidence.
  • Add Evidence for a particular crime case.

---

Tasks and Features to be added.

This are the curated list of backend logic yet to be implemented.

• Authication.
  • register admin.
  • generate ontime code for each user who wanna get them selves registered into the system.
  • send the one time code to the officer mail address using node_mailer.
  • validate officer request data sent from client including the code.
  • save officer data in postgresqlDB
• Authorization.
  • generate a jwt_refresh_token && jwt_acccess_token containing users details.
  • send generated token to client which would then be used in route protection.