scorelab / labellab

An Image Analysis and Classification Platform for Machine Learning Researchers

LabelLab

LabelLab is an image analysis and classification platform for Machine Learning researchers. Originally built to classify images of elephants, it has been developed over the years and is now a full-fledged ML utility tool that is able to classify all kinds of images and carry out a number of ML-related tasks in a project-based manner while teaming up with other researchers.

Features

• The user can create a project and add other users as collaborators.
• Inside a project, multiple actions can be performed such as -
  • Uploading images in batches
  • Creating new labels
  • Labelling the uploaded images
  • Creating and training different kinds of models
  • Using the image path tracking feature on labeled images
• Each collaborator can be assigned one or more roles such as images, labels, models, admin, etc which will allow that collaborator to perform tasks specific to that role.
• On basis of their roles, the collaborators are divided into various teams.
• Each team has a chat system to discuss the assigned tasks and progress on the project.
• The project also has an activity tracking system recording all progress in it, which can be filtered by team, project member, category, and entity.
• Besides that, the user can also upload images outside a project and run classifications against a trained model.

Apache 2.0 Licence

See the LICENSE file for details.

Deployment

Host your own LabelLab server for FREE with One-Click Deploy

Documentation

To learn more about the project, check out the Project Wiki

User Guide

Please go though our Code of Conduct first.

Follow these instructions to setup the project in your local system.

• Clone the repository.

git clone https://github.com/scorelab/Labellab.git

• Follow the instructions provided below for setting up each section of the project

  • Backend Setup

  • Frontend Setup

  • Mobile Setup

NOTE: The Node.js API in labellab-server directory is now deprecated and is no longer being used in the project. Instead, use the Flask API in labellab-flask directory.

Contact

• Join the LabelLab Gitter Channel for any queries or discussions regarding the project.
• For learning more about SCoRE Lab and its various other projects, check out our Website

labellab's Issues

Minimum password length requirement not enforced during registration

Describe the bug
validateInput() is used to ensure password length is greater than 8 characters during login. This is not done when the user registers, so a user can create a password of length less than 8 characters but won't be able to login.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Create Account' from the home page.
2. Create an account with a password of length less than 8 characters. e.g. abc123
3. Go to the login screen and enter the credentials of the account just created.
4. Click on the 'Login' button to try loggin in.

Expected behavior
The registration page should show the alert 'Password is not of sufficient Length. It should be atleast 8 characters.' when the user tries to create an account with a password of length less than 8.

Screenshots

The above account is created without an error.

But the following error is shown during login.

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 78

Additional context
I am working on using validateInput() and showing an appropriate error message before an account is registered.

Error while running the node server of labellab-server

labellab-client is working fine but I'm getting following error while running the node server of labellab-server using 'npm start'.

C:\Users\msk\Desktop\open_source\LabelLab\labellab-server\node_modules\passport-oauth2\lib\strategy.js: 100
if (!options.clientID) { throw new TypeError('OAuth2Strategy requires a clientID option'); }
^
TypeError: OAuth2Strategy requires a clientID option
at Strategy.OAuth2Strategy (C:\Users\msk\Desktop\open_source\LabelLab\labellab-server\node_modules\passport-oauth2\lib\strategy.js: 100:34)
at new Strategy (C:\Users\msk\Desktop\open_source\LabelLab\labellab-server\node_modules\passport-github\lib\strategy.js:62:18)
at Object. (C:\Users\msk\Desktop\open_source\LabelLab\labellab-server\config\github_passport.js:9:2)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object. (C:\Users\msk\Desktop\open_source\LabelLab\labellab-server\routes\auth\routes.js:10:1)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.

I think i've to add my credentials but I can't find that file.
Thanks in advance!

Modal for creation and table for display of project labels

Is your feature request related to a problem? Please describe.
The current interface for adding and displaying labels in the project dashboard is slightly confusing and cluttered:

1. Buttons are not aligned properly when adding a new label.
2. The label name and type can still be edited after label creation but changing these fields does not edit the label.
3. Each label takes up an entire card which is too much space.
4. When adding a new label, user needs to scroll to the bottom of the current list.

Describe the solution you'd like

1. There should be a button at the top of the page for Add New Label
2. Since most of the other components of LabelLab use a modal for creating a new entity, a new label should be added using a modal.
3. After adding a new label, it should be displayed in a table of the format:

S.No.	Label	Type	Delete

Describe alternatives you've considered
N/A

Additional context

1. Each label takes up too much space
2. The fields can still be edited but don't lead to changes being saved
3. To add a new label, user must scroll to the bottom of the page

Ask for project description during project creation

Is your feature request related to a problem? Please describe.
The project description is an essential piece of information about the project and it is displayed on the dashboard with the project name as well. It would make sense to ask the user for the project description while they are creating a project, instead of creating every project with the default Image labelling description.

Describe the solution you'd like
The Create Project popup should ask the user for the project description as well as the project name.

Describe alternatives you've considered
N/A

Additional context
N/A

Bugs in the labeller

Describe the bug
there are a few bugs that i have discovered in the labeller:

1. the app crashes on clicking different polygon labels simultaneously

To Reproduce
Steps to reproduce the behavior:

1. Go to 'labeller'
2. click on two different polygon labels
3. Click on back button twice
4. See error

Expected behavior
the app shouldn't crash

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOs
• Browser [e.g. chrome, safari] Chrome
• Version [e.g. 22]

Additional context
I am working on this issue for now.

Cannot import TOKEN_VALUE from ../constants/index

Describe the bug
this comes written in the console when we first run our client-side server.

To Reproduce
Steps to reproduce the behavior:

1. Run 'npm start in labellabs-client folder'
   see error

Expected behavior
the client side server should have started without any errors.

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOs Catalina
• Browser [e.g. chrome, safari]chrome

Use Mockgoose instead of deleting entries from database everytime while testing

Is your feature request related to a problem? Please describe.
we always delete our created entries from our database after the tests on every route instead we could use mockgoose to automatically do that for us and it is uses the memory store which does not have persistence. And also our tests should be independent of the development database. So, using this would be a good practice
Describe the solution you'd like
use mockgoose to provide a wrapper around our development database and make our development database independent from the changes within our tests also, automating the delete queries after every test.

Additional context
i would love to know to opinions of the maintainers here!

Will we have to make app only for android or for both android and IOS?

Add contributing guidelines in contributing.md or update the readme.md with contribution guidelines

Is your feature request related to a problem? Please describe.
Add contributing guidelines

Describe the solution you'd like
Add contributing guidelines in contributing.md or update the readme.md with how to start contributing.

Describe alternatives you've considered
Update readme.md

Additional context
Lots of newcomers are claiming on several issues which is acting as a barrier for other contributors to pick up the issue and fix.

Add tests for react components and also fix the present react app component test.

Describe the bug
Add tests for react components and also fix the present react app component test.

To Reproduce
Steps to reproduce the behavior:

1. Cd to 'labellab-client'
2. Do npm install
3. Do npm run test
4. See test fails

Expected behavior
App test should pass

Desktop (please complete the following information):

• OS: [e.g. iOS] Ubuntu
• Browser [e.g. chrome, safari] Chrome
• Version [e.g. 22] 18.04

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

HotKeysPanel not opening on clicking the open HotKeys button

Describe the bug
when we click the hotkey button in the sidebar it does not respond at all.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'the labler'
2. Click on 'the hotkeyicon'
3. See error

Expected behavior
the hotkeyspanel should have opened

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]MacOs

Additional context

Error in MongoDB Connection String

ERROR:
Inside lablabel-server folder:
When I tried to run nodemon server, It shows
MongoParseError: Invalid connection string

When I added mongodb:// prefix in mongoURI i.e. mongodb://localhost:27017/my-db, It fixed the problem.

POSSIBLE SOLUTION:
So, I think mongodb:// prefix is also required in mongodb connection string.

Improving the UI of labels route

Describe the bug
the create new label and the create buttons are at very odd positions. I am trying to make them look more appealing. also the the upcoming submit button also does not have any bottom-margin.
To Reproduce
Steps to reproduce the behavior:

1. Go to 'one of your projects'
2. Click on 'project labels'
3. See error

Expected behavior
a visually appealing position of create label button and create new label button
Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOs
• Browser [e.g. chrome, safari] chrome
• Version [e.g. 22]

Additional context

Use concurrently to run client and server with single command

Is your feature request related to a problem? Please describe.
Currently, developers have to open 2 different terminals and execute separate commands to start the server and the client.

Describe the solution you'd like
The concurrently NPM package can be added as a dev dependency and used to run the front-end and back-end using a single command.

Describe alternatives you've considered
N/A

Additional context
N/A

the analytics table does not get updated in real time.

Describe the bug
the analytics table does not get updated real-time the page has to be refreshed to update it

To Reproduce
Steps to reproduce the behavior:

1. Go to 'the project analytics tab'
2. Click on 'if some labels have been recently added the will not be displayed'
3. refresh the page
4. the analytics table will get updated

Expected behavior
the table should have been updated in real-time

Additional context
working on it!

UI fixes in the dashboard

Describe the bug
there are some UI issues in the dashboard like not appropriate spacing is provided between menus and the project cards
To Reproduce
Steps to reproduce the behavior:

1. Go to 'dashboard'
2. try to resize your browser window
3. See error

Expected behavior
there should have been left some margin between those two

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]MacOs
• Browser [e.g. chrome, safari]Chrome

Additional context
i will provide additional responsive UI changes if i find any

Clearer project page navbar

Is your feature request related to a problem? Please describe.
It is hard to discern the navbar when a project page is opened. The background colour of the navbar merges with the background colour of the body and the Dashboard button is very small and not aligned properly.

Describe the solution you'd like

1. If the colour of the body is to be kept the same, a shadow can be added to the bottom of the navbar to help differentiate it from the body.
2. The Dashboard button must be of a larger size and should have proper padding.

Describe alternatives you've considered
An alternative solution for the colour could be to set the body of the project page to the same colour as that of the home page - #e5e5e5. This would make the navbar easy to see like in the home page.

Additional context

The Dashboard button is too small and not aligned properly and the navbar is hard to differentiate from the body.

the profile picture does not get updated or even added for the first time

Describe the bug
inside the profile a user cannot cannot change their profile picture

To Reproduce
Steps to reproduce the behavior:

1. Go to 'your profile'
2. Click on 'change profile picture'
3. 'select a profile picture'
4. the profile picture does not get changed

Expected behavior
the profile picture should have been updated.

Additional context
on it

the image link does not seem to be working

Describe the bug
on the project images tab when an image is clicked the image does not lead to its 'static/uploads/' link

To Reproduce
Steps to reproduce the behavior:

1. Go to 'the project image tab'
2. Click on 'one of the images'
3. See error

Expected behavior
this should probably show the image along with its labels.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
i think that the link is itself leading to nowhere I'll look into it though.

the "/api/v1/project/get" and the "/api/v1/users/info" routes are not working

Describe the bug
when the landing page is loaded there come bugs referencing to this issue and the projects keep loading indefinitely

To Reproduce
Steps to reproduce the behavior:

1. Go to 'landing page'
2. Click on 'open the console'
3. See error

Expected behavior
when a new user logs in no projects should be visible in their profile and when an existing user with some projects comes it should show the projects

Desktop (please complete the following information):

• OS: [e.g. iOS] macOs catalina
• Browser [e.g. chrome, safari] chrome
• Version [e.g. 22]

Additional context
I'm on it to figure out why this is happening

No way to update the name of the label after creating it

Is your feature request related to a problem? Please describe.
after creating a label there is no way one can update its name

Describe the solution you'd like
change the name of the label after creating it

Docker-compose.yml overwrites working directory of Dockerfiles

Describe the bug
Containers started by docker-compose up server shows "cannot find module......" after npm start. The reason is that docker-compose.yml sets working_dir to a different value of WORKDIR of labellab-server/Dockerfile. And CMD of labellab-server/Dockerfile takes effect after working_dir of docker-compose.yml. Hence the error.

To Reproduce
Steps to reproduce the behavior:

1. Go to project directory
2. Run docker-compose up server

Expected behavior
Containers started normally

Screenshots

Desktop (please complete the following information):

• OS: MacOS

submit button not submitting the image with the edited labeldata

Describe the bug
the submit buttom in the labller is not submitting the image with the edited labeldata

To Reproduce
Steps to reproduce the behavior:

1. Go to 'make some changes to your image in the labler '
2. Click on 'submit button'
3. See error

Expected behavior
the submitted image should have been updated.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
working on it!

Images are not deleted from the server only deleted from the database

Describe the bug
images when deleted from the database are not deleted from the server

To Reproduce
Steps to reproduce the behavior:

1. Go to 'project images.'
2. Click on 'delete image'
3. open uploads folder
4. see persisted image

Expected behavior
the image should have been deleted from the server as well

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOS
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

the /analytics and the /summary links are not working from the dashboard

Describe the bug
the links the /analytics and /summary are not working from the dashboard menu

To Reproduce
Steps to reproduce the behavior:

1. Go to 'dashboard'
2. Click on 'analytics/summary from the menu'
3. See error

Expected behavior
the analytics and the summary links should have redirected to their routes

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOs
• Browser [e.g. chrome, safari]Chrome
  Additional context
  this might be due to the absence of the required data models to perform labelling analysis. Trying to find that out.
  working on it!

Unable to retrieve images in labeller

Describe the bug
Clicking on Edit on an image opens up to a blank screen.

To Reproduce
Steps to reproduce the behavior:

1. Go to existing project
2. Add a label (Bounding Box)
3. Add an image
4. Click on Edit for the image
5. See error

Expected behavior
Clicking on Edit for the image should open up the labeller.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 79

Additional context
I was able to fix this issue by changing imageUrl in the labeller component.

Does not have a PR template

The project needs a PR template.

Error while registering!

I've successfully connected to mongodb and started lablabel-server and client but I'm getting following error while registering a user.

Unhandled Rejection (TypeError): Cannot read property 'msg' of null
C:/Users/msk/Desktop/open_source/LabelLab/labellab-client/src/actions/index.js:74

User ML model section

• The images which were taken should have a function inside the path tracking feature to track the location of the images.

• User should be able to switch/choose between various ML models for testing their project.

GSOC 2019 Idea

@ivantha According to the Official GSOC-2019 list of project ideas of Score Lab , there is one Idea which is on Implementing the Label Lab Web Application . I want to work on this Idea and want to take part in GSOC-2019 . I have already introduced myself on Gitter.

Add more unit tests

Is your feature request related to a problem? Please describe.
As of now, there are only the unit tests for auth routes and project routes.

Describe the solution you'd like
There should be tests for each route.

Describe alternatives you've considered
Implement unit tests using Mocha and chai.js

Additional context
It will improve the quality of the code.

Hash the password before saving to db to prevent security issue

Is your feature request related to a problem? Please describe.
Hash the password before saving to DB to prevent the security issue

Describe the solution you'd like
Use bcrypt.js to hash the password and after that save the password

const bcrypt = require('bcryptjs');
bcrypt.genSalt(10, (err, salt)=>{
   bcrypt.hash(newuser.password,salt, (err, hash)=>{
     newUser.password = hash;
    newuser.save(); 
  });
});

Describe alternatives you've considered
Or can use other algo to hash like SHA-256 to hash manually and then assign it to password

The home/add image button does not work when labeling an image

Describe the bug
While we are labeling the image after uploading it....there are 2 buttons above which are home and add image. The home button and add image does not work and we have to go back from the browser to go home.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'start a new project/existing project'
2. Click on 'Add image'
3. After adding the image once you start labeling it...the home button and add button doesn't work

Expected behavior
After clicking the home/add image button it should do what it is supposed to do

Screenshots

Desktop (please complete the following information):

• OS: [ iOS]
• Browser [ chrome]

404 page

Is your feature request related to a problem? Please describe.
404 page can be used for redirecting user from invalid URL.

Cluttered dashboard navbar in mobile view

Describe the bug
In mobile view, the dashboard navbar is very cluttered and hard to use.

To Reproduce
Steps to reproduce the behavior:

1. Open the dashboard.
2. Decrease the viewport width to any value less than 760px.

Expected behavior
Only the most important elements of the navbar should be shown in mobile view and elements should not overlap.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 79

Delete Project doesn't remove images, labels, and projectmembers related to the project

Describe the bug
When a project is deleted, the images, labels, and projectmembers related to that project are not deleted from the database.

To Reproduce
Steps to reproduce the behavior:

1. Create a project.
2. Add images, labels, and project members to the project.
3. Note the number of documents in each of these collections.
4. Delete the project.
5. Note that the number of documents for images, labels, and projectmembers has not changed.

Expected behavior
The images, labels, and projectmembers documents for the project which is being deleted, should also be removed from the database.

Screenshots
Before deletion:

After deletion:

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 79

Additional context
I'm currently working on fixing this bug.

Fix reference to error view

Describe the bug
Upon an error, the server will encounter an exception as it fails to locate 'error.ejs' referred to simply as 'error'.

To Reproduce
Steps to reproduce the behavior:

1. Start the server
2. Send any request that results in the error page to be rendered

Expected behavior
The error page should be rendered (error.ejs in views)

Desktop (please complete the following information):

• OS: Windows
• Browser: Chrome
• Version [e.g. 22]: 79

Proxy port not set correctly

Describe the bug
Initially, the frontend will not be able to send requests to the backend (tested through the login and register routes). This is because all requests are proxied to the port 4000, but the backend (both dev and production) are running on port 3000 by default.

This leads to all requests failing to be fulfilled.

To Reproduce
Steps to reproduce the behavior:

1. cd labellab-client
2. npm install
3. npm start
4. New terminal window
5. cd labellab-server
6. npm install
7. npm start or npm run dev
8. Perform any request on the frontend and observe the error in the frontend console log.

Expected behavior
Requests are fulfilled by the backend.

Screenshots

Backend starting on port 3000


Proxy pointing to the wrong port

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 80

Additional context
Should be solved by updating the proxy value. I can make a pull request for this, given permission.

Project cards don't show actual project description

Describe the bug
Instead of showing the actual project description, all project cards say Image Labelling App

To Reproduce
Steps to reproduce the behavior:

1. Go to Dashboard
2. Click on Start New Project and create a project with any name. e.g. Project 1
3. Click on the project card.
4. Change the project description by clicking on the pencil icon.
5. Go back to dashboard and look at the project card.

Expected behavior
The Card content should be the projectDescription property of the respective project.

Screenshots
This is the actual description of Project 1:

This is what the card for the project shows in the Dashboard:

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 78

Additional context
I am working on editing the Card Content to show the project description.

npm install

as per your readme file
i clonet he repository, but to setup react js server there is no npm installation file present. can you help me setup.

Add image button does not work after used once.

Describe the bug
the Add image button does not work after one has uploaded the image

To Reproduce
Steps to reproduce the behavior:

1. Go to 'one of the projects'
2. Click on 'the add image and add an image'
3. Scroll down to 'try to add another image'
4. See error

Expected behavior
another image should have been added

Desktop (please complete the following information):

• OS: [e.g. iOS]MacOs
• Browser [e.g. chrome, safari]chrome
• Version [e.g. 22]

Additional context
working on it

Register route not working

Describe the bug
The register route is not working as the endpoints were tested in postman also the error page is not being rendered.

To Reproduce
Steps to reproduce the behavior:

1. Start the server
2. Go to the register route
3. See the console for errors

Expected behavior
The user should have been registered

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOs catalina
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
I am working on it!

Update the readme.md with the correct steps to run server and other.

Describe the bug
Update the readme.md with the correct steps to run the server and other. As of now, before installing the dependencies it's starting the server using npm start.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Readme.md'
2. And check the steps to run server-side
3. See

Expected behavior
Before starting, install dependencies.

Also provide some information about the .env file. i.e what should be added and what may be ignored

Error in mongo URI

Describe the bug
the current URI given is not correct. It is missing a condition when there is no username and password set for the database also 'mongodb://'+ dbUser + ':' + dbPass + '@' + dbCluster + '/' + dbName is the correct form rather than dbHost + '://'+ dbUser + ':' + dbPass + '@' + dbCluster + '/' + dbName

Delete project button in web app

Is your feature request related to a problem? Please describe.
Although there is an API end-point for deleting a project, I am unable to find a button in the client for deleting a project.

Describe the solution you'd like
There should be a Delete Project button below the sidebar in the project page which deletes the corresponding project.

Describe alternatives you've considered
N/A

Additional context
N/A

Ignore case for project search

Is your feature request related to a problem? Please describe.
It becomes cumbersome to exactly match the upper cases in a project name while searching for a project.

Describe the solution you'd like
Searching projects by project name should ignore case sensitivity.

Describe alternatives you've considered
N/A

Additional context

In above case, Project 1 should have been shown as a result but wasn't.

there is no way to delete an uploaded image before submitting it

Describe the bug
the image cannot be updated after we have uploaded it but not submitted it
To Reproduce
Steps to reproduce the behavior:

1. add an image
2. there is no delete the uploaded image button there before submitting and the add image button does not work

Expected behavior
one should be able to change the uploaded image as sometimes the size of the image might be alot or we wish to change an image before submitting.

Additional context
this can be a bug if the add image image button should be functional or a feature if we need to add a delete button.
i am waiting for a suggestion from the maintainers before working on it

In the README.md file to run labellabs-client

Describe the bug
there are no instructions on how to run the clientside-server
it should say Run the Node server in the labellab-client folder: instead of
Run the Node server in the labellab-server folder:

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Add tests for users, classification and image routes.

Is your feature request related to a problem? Please describe.
tests for these routes are missing i was thinking adding them using mocha and chai.js

Describe the solution you'd like
i was thinking of using mockgoose as a wrapper to mongoose but its just a suggestion would love to hear inputs!

Describe alternatives you've considered
using mocha.js and chai.js to write test cases for users, image, classification routes

there is no warning coming for the minimum size of the image to be uplaoded

Describe the bug
there is no warning coming for the minmum size of the image that can be uploaded

To Reproduce
Steps to reproduce the behavior:

1. Go to 'create a new project or go to an existing one.'
2. Click on 'project images'
3. Scroll down to 'select an image of size greater than 150 kb and try submitting it'
4. See error

Expected behavior
there should have been a warning displayed that the size of the image to be uploaded is too large

Desktop (please complete the following information):

• OS: [e.g. iOS] Mac Os catalina
• Browser [e.g. chrome, safari] chrome

Additional context
working on it!