2. Description

2.1 The Client

Clients or Users of this software will be able to access and view "reports" that pertain to their business. A "report" is a document that is used to track any incidents or situations that may happen inside a business. These reports will contain up to 5 text fields to denote the contents of the incident, and also contain "profiles" of the people involved. Profiles are elaborated on later, but for now, knowing that these profiles contain images of the person they are about will suffice to explain the following.

This system is expanded upon by the use of camera system connected to a Facial Recognition program. A business will have a camera pointed towards their point of entrance, and record all patrons entering their establishment. Due to this, the camera will be able to see their faces. A facial detection program will run to check for faces, and once it detects a face, it will save a picture of it. This picture will be send to a Facial Recognition program that will then check against all the images saved in the profiles mentioned earlier. By use of this system, the Facial Recognition can automatically detect if an unwanted person attempts to enter an establishment.

Along with the reports describe above, clients will also be able to create 'profiles' of patrons that they document in their report. A profile can contain basic identification information, such as that you might find on a drivers license. They will also include an image, a 'status', and an 'involvement'. The status will be a value along the lines of 'Banned', 'Watched', 'Cleared' etc. An 'involvement' will denote whether the party was a 'suspect' 'victim' or a 'witness'.

When a client logs into the system they will be greeted with a homepage containing the most recently recorded reports, and a search bar that will allow them to search for any other report they may wish. Since this is a business oriented system, there will be two main types of accounts: Admin and Employee. Under the hood, a Business account is also created. These will all be elaborated on in another part of the wiki

2.2 The Database

The database for this project is split into multiple parts. Due to the Micro-service architecture design, there will be a separate database for Authentication, Accounts, Reports, and Images. However, they will all share a type of foreign key relation to each other. Ideally we would like these to be all on the same resource server, but we are broke college students so we rigged this solution together for now.

In essence, every entity in the databases will be connected via a "Business Id".
Specific Table formats will be uploaded at a later date.

Image servers runs on a python server with a database, as new images are sent to the image server the database is updated with a folder structure that represents the database schema. Folder structure is as follows Base folder -> Business ID -> Profile Id -> Image File.