- The vision compiling diversity data and using it as a teaching tool to bring to light internal biases and ways to be more conscious with regard to inclusiveness and diversity.
- We wanted to take this survey beyond the former version and build in historical data of all classes into the future. This added feature will allow facilitators and administrators to evaluate the data of past classes and cohorts providing Code Fellows staff the ability to accurately assess the DEI atmosphere.
- This project will revolutionize the existing survey data, making it more user friendly and offering the opportunity to cache historical DEI data from all students past and present.
- This product will drastically improve the awareness of internalized biases, discrimination and privilege based on a multitude of factors inspiring a more inclusive and self-aware team and learning environment for all students.
Allow the Admin user to...
- Access the survey.
- Complete the survey.
- View data on a stylized graph.
- Compare data by multiple students in one class.
- See how many students participate in the survey.
- Data from other schools and students will not be visible.
- New students' data from other schools cannot be added.
- What will your MVP functionality be?
- Access and complete the survey.
- Store immediate survey data in the DB.
- Render a stylized graph of the immediate data.
- What are your stretch goals?
- Cache historical data.
- Develop a graph modeling historical data.
- Allow the user to access historical data and trends.
- What stretch goals are you going to aim for?
- The ability to store historical data.
- User will be able to complete the survey and submit data.
- User will be able to access a stylized graph of the immediate data.
- User will be able to secure data and login information.
-
Security
- Our app will use Auth0 to make sure we have authorized users
- This will allow us to track and personalize to our users
- Our backend will validate requests to make sure it is coming from our front end
- Managing the uses of our api and databases so only our users are able to access those resources
-
Database
- Each item belongs to a single location
- The two databases will be a Student database and a Class database
- There will be a identifier in the DB associated with the class
- Each student will have a single class
ClassSurvey = {
ClassNumber : Number,
Identifier : String,
ClassCount : Number,
Instructor : String,
thumbnail : String, //url
note: String //optional
}-
begin by running:
-
git clonethen copy and pastegit@github.com:Meltingpot-Data/techperspective-front.git -
Do the same for the backend repo:
-
git clonethen copy and pastegit@github.com:Meltingpot-Data/techperspective-back.git
- run:
cd techperspective-front - then (installs node modules):
npm install - then (installs dependencies):
npm i express bootstrap nodemon cors dotenv mongoose jwt bcrypt base-64 supertest sqlite3 jsonwebtoken - repeat step two for 'back'
- Your are going to need to create a
.envin order to use the server, follow the guide in the provided.sample.envfile.
- Click on the provided link here: Survey Admin Portal
-
run:
npm startTo test the server -
run:
npm run testTo run the tests
Erik Program Management, React, JavaScript, teamwork, bootstrap-react Joey Front-end Design, creative, communication, leadership, team building, all-around BA Emily Front-end design, layout and CSS Ryan Cool bird Dad, testing/bug hunting, Master of parrot gifs Michael Backend creation, Javascript development and problem solving
How are we going to utilize these strengths?
- Emily and Joey will take point on the creative styling and UI.
- Ryan and Michael will tackle the backend development.
- Joey and Erik will co-lead the team and ensure all docs and details are submitted and taken care of.
- Joey wants to work on leadership and project management.
- Erik wants to work on communication and making his presentations sound more natural.
- Emily would like to refine her teamwork skills.
- Michael Would like to improve his communication and public speaking.
- Ryan endeavors to hone his technical skills.
- 9:00am to 6:00pm 12pm-2pm lunch designed but open to interpretation.
- Morning standup to go over what is planned.
- Afternoon (~5:00PM) will be bringing all the code together and planning for the next day/
- Conflict Resolution
- One-on-one discussion,
- Mediation with another group member,
- Group discussion,
- Elevate to the next level as necessary.
- Joey 12AM cutoff (but is an insomniac - available for friends at all times)
- Erik 12AM
- Emily 12AM (EST)
- Michael 12AM
- Ryan 12AM but also available whenever
- Slack
- Remo
- Zoom/Discord
- As needed but will have planned lunch
- If we start to fall behind?
- Reevaluate what is MVP for us
- Communication on off hours
- Slack
- text (for urgent needs)
- Everyone will be sharing at stand up and stand down.
- Frame responses with mutual respect.
- Joey is going to do his best to check his internal biases and assumptions of others.
- Erik speak up in challenging situations and bravery.
- Emily wants to work on not being so mean to men and take action to reduce stressful situations.
- Michael wants to ensure all voices are heard.
- Ryan wants to work on examining his assumptions.
- We will be creating a task list to manage things from our Trello board.
- LiveShare on VS code.
- Frontend and backend will live on the GitHub
- Making an organization
- Working on own branches
- Push to staging and test
- Otherwise push as needed
- Two other reviews for main
- One for staging
- Merging hopeful once a day but as necessary
- This amazing final project was thoughtfully created and masterfully crafted by the master-minds of Erik Savage, Michael Metcalf, Joey Hernandez, Emily Landers, and Ryan Lee!