Maya - CSC4790-Fall2024-Org/Sororify GitHub Wiki
Sep 8 - Sep 14
- What I did this week: discussed next steps for project, researched django and api capabilities
- What I plan for next week: after db connection is established, configure different urls for RBAC
- Blockers faced: knowing what steps needed to come first
jdob: ✅
Sep 15 - Sep 21
- What I did this week: two team meetings for troubleshooting, creating serializers, researching axios
- What I plan for next week: work on api and endpoint creation
- Blockers faced: choosing what db to use, then establishing connection
jdob: ✅
Sep 22 - Sep 28
- What I did this week: established ability to read and write from database, displaying results
- What I plan for next week: connect the algorithm to create bump groups
- Blockers faced: encountered some issue with port numbers for GET/POST request (resolved)
jdob: ✅
Sep 29 - Oct 5
- What I did this week: worked on connecting algorithm, researched switching languages for the algorithm
- What I plan for next week: continue working to implement the matching algorithm
- Blockers faced: encountered some blockers when trying to connect the algorithm with the front end, need better documented code for backend vs frontend teams
jdob: ✅
Oct 6 - Oct 12
- What I did this week: (grace hopper this week so not too much progress) formatted json data into the correct data structures to send into the algorithm
- What I plan for next week: determine if we will need to switch language for algorithm to JavaScript, implement matching
- Blockers faced: ran into blockers surrounding the formatting of the data in the database and how to parse it (resolved)
jdob: ✅
Oct 13 - Oct 19
Fall Break, no status needed
Oct 20 - Oct 26
- What I did this week: converted pre-established algorithm to JavaScript, edited data formatting into an onClick and set up percent calculations to be triggered once data was formatted correctly
- What I plan for next week: edit results so that name is displayed along with PNM number, parameterize functions in algorithm so it can apply to each sorority (only been working with one so far)
- Blockers faced: issues with console not displaying some results correctly
jdob: ✅
Oct 27 - Nov 2
- What I did this week: edited finalMatches so that full name can be displayed along with PNM number and percent match
- What I plan for next week: parameterize functions in algorithm to apply for all sororities
- Blockers faced: didn't have much time this week, more progress to come next week
jdob: ✅
Nov 3 - Nov 9
- What I did this week: parameterized functions in algorithm so they can apply to all sororities
- What I plan for next week: enter more data into database, discuss how to format infoPage results in the db to account for different sororities
- Blockers faced: didn't have all the data required in infoPage collection to test enough
jdob: ✅
Nov 10 - Nov 16
- What I did this week: more data into db, testing and tweaking algorithm for different sororities
- What I plan for next week: address blockers, disuss with Moriah
- Blockers faced: running into issues with infoPage when there is more than one entry in the db
jdob: ✅
Nov 17 - Nov 23
- What I did this week: fixed issue with multiple entries in info surveys, resolved bug with number of PNMS being matched
- What I plan for next week: meet with group to discuss final steps
- Blockers faced: smooth sailing this week
jdob: ✅
Nov 24 - Nov 30
Thanksgiving Break, no status needed
Dec 1 - Dec 7
- What I did this week: testing functionality, worked on poster, practiced lightning talk, and prepped for sprint 3 presentation
- What I plan for next week: n/a
- Blockers faced: n/a