v1.0

The final version of Delta for 492.

Website: https://guarded-journey-12008.herokuapp.com/#/

Example user login information:

Username: username
Password: password

Example files for upload are found below:
ex00.csv
ex01.csv

RC1 Milestone

This release follows the protocol lined out here. Note that we are making a webapp.

Website

The link to the website is here.

All the issues stated in the RC1 Milestone were completed. When appropriate, a screenshot illustrating the completion is also present.

Example user

Username: testuser
Password: password

Example files

Please see the example files listed below.
ex01.csv
ex00.csv

Deliverables:

1. Git tag created.
2. Git tag pushed.
3. Webapp published.

v0.5

Please pay attention to this release instead of the tag, as this release has some example csv files to upload. However, if you want the binaries, you would check out this page since it contains those.

Here is the URL for the website: https://guarded-journey-12008.herokuapp.com/#/login

Each issue within the Beta Release Milestone has instructions / an example of how it was completed.

Deliverables:

1. Git tag was created.
2. Git tag was pushed. We also created a release so we could have uploadable files.
3. Webapp was published.

Example username password combo:
Username: test
Password: password
You can also just create an account.

Example files to upload:
ex01.csv
ex00.csv

Proof of Concept

Marks the 0.1 version of the application. Completion of requirements for 490.

PoC video: https://youtu.be/5YO0MI_8BMM

URL: https://guarded-journey-12008.herokuapp.com/#/

NOTE: Organization can only be added by admins. Regular users cannot add or edit organizations.

ValafarLab organization key: password
Organization X organization key: mykey

Three example csv files can be found below.

ON HOW EACH POC REQUIREMENT IS FULFILLED:

1. #49 : Deploy to Heroku. Here's the URL: https://guarded-journey-12008.herokuapp.com/#/
2. #50 : Bootstrap usage. Everything on the site uses Bootstrap classes. An example is with the NavBar:
   
3. #51 : Navbar. See here:
   
4. #52 : Create an SPA with React. The website uses React as the Front End and Django as the Back End.
5. #53 : Use Redux. Redux is used to store user credentials.
6. #54 : Use Axios. Axios is used to make HTTP requests from the frontend to the backend.
7. #56 : Knox. Knox is used to provide tokens for actions that require logged-in users.
8. #57 : Mysql. The app uses mysql database to store data.
9. #58 : Register. Users can register here
10. #59 : Register under an organization. If you register and provide a valid organization key, you can register under and organization. See the following:

Registering and entering a correct organization key...

Notification that you are correctly registered...

Verification that you are under an organization...

Note that if you register with an invalid key / no key passed, you will see the following notification that you are not under an organization:

11. #60 : Register, but not under organization. Please see the above images for proof of this. You can choose to not register under an organization by providing an invalid organization key, or simply no key at all.

12. #61 : User can log in. See here

13. #62 : User can view a customized home screen.
    Here is the home screen:
    
    NOTE: ALL GRAPHS SHOW DUMMY DATA. THIS IS MADE CLEAR IN THE APP BY USING THE VERBAGE "WILL SHOW" RATHER THAN "IS SHOWING". WE DO NOT YET HAVE THE CAPABILITY TO OBTAIN THE DATA REQUIRED FOR GRAPH CREATION, NOR DO WE KNOW WHAT GRAPHS THE CLIENT WOULD LIKE. THIS IS DUE TO THE FACT THAT THE TEAM RESPONSIBLE FOR DATA COLLECTION (MEMBERS OF VALAFAR LAB) DO NOT YET HAVE ALL THE DATA, AND DUE TO THE FACT THAT THE CLIENT IS NOT YET SURE OF WHAT TYPES OF GRAPHS WOULD BE NECESSARY. THUS WE INCLUDE GRAPHS ONLY TO PROVE TO THE CLIENT THAT WE CAN PROPERLY USE CHART.JS LIBRARY.

14. #63 : Delete account. See the following "Remove Account?" button:
    
    NOTE: AS PER CLIENT REQUEST, DELETING THE ACCOUNT ONLY MARKS IT AS INACTIVE. THUS WHEN YOU DELETE AN ACCOUNT, YOU CAN NO LONGER LOG IN, BUT THE ACCOUNT INFORMATION REMAINS ON THE WEBSITE.

15. #64 : Logout. See the following "Logout" button on the navbar:
    

16. #65 : Customized profile page. The profile page allows users to view their information, and edit it. See the following image:
    

17. #66 : Edit profile information. All profile information can be edited on the profile page. See the following image:
    

18. #69 : Downloading data. Can download the data at the download page. See the following image:
    

19. #70 : Search for certain data. See the following two images for an example of searching for "Session".
    Without search text:
    
    With search text (note that only entries with "Sess" in the title are shown):
    

20. #71 : Multiple files download. To download multiple files, simply check all the files you want. See the following image for an example of downloading two files:
    

21. #72 : User can upload files. Uploading of files can be done via the upload page. See the following image:
    

22. #73 : User can view uploaded files. Files that are uploaded AND MARKED AS PUBLIC can be viewed at the download page. See the following image:
    
    If a file you uploaded is NOT MARKED PUBLIC, then you will have to go to the Personal Community Page. See here:
    

23. #74 , #75 Deletion of files. Can delete files at the Personal Community Page. See the following image:
    

24. #76 : Update files. You can click on the "Edit" button of a file you uploaded to edit it. See the following two images:
    
    And when you click edit, the following image is seen. Note the fields that are greyed (like ID) are not allowed to be changed.
    

25. #77 : View registered organization's uploads. Going to Organization Community page, you see the following image:
    
    Clicking on the organizations that are registered, you can see any files under them. Note here that "registered organization" means that the organization is registered with the system, not that you are registered with the organization. You will only be able to view public files that people who are registered under the organization have uploaded. See the following image:
    

26. #79 : Color scheme. The general color scheme was followed. Note that the color scheme is a guideline, and will me more rigidly defined in 492.

27. #80 : Upload files through the font-end web app. #72 was proving that files could be uploaded via HTTP, this proves that we can do it via a front end GUI. See the prior images regarding file uploads.