---
# System prepended metadata

title: Untitled

---

## Sprint #4 Retrospective:
* members in attendance:
  ![selfie proof of meeting](http://)
  - [x] Jacob
  - [x] Georgia
  - [x] Phoebe
  - [x] Gwen
  - [x] Giorgie
  - [x] Nick
* what worked well
  * we made progress! 
  * added api calls to frontend for folder logic
  * made dashboard functional - summaries link to appropriate pages and real folder info displayed
![](https://i.imgur.com/2QRDj73.png)
  * progress on the studying feature
  * got great feedback from Tim and have a clear picture of what features/fixes we would like to implement! - revised figma accordingly
      * ![](https://i.imgur.com/7GxCPzU.png)
  * revised edit page for clarity and added terms count
![](https://i.imgur.com/lJQQqkH.png)

* what didn't
  * Team members had midterms and were busier than usual
  * we came up with some edits to our designs that will make the app much more usable, but this also means wil
* self assessment on progress
  * where are you in relation to progress towards product and milestones?
    * give an estimate of how far towards your goals you are, do you think you're on track?
        * we are making good progress! 
        * we have a lot to do but have layed out a good plan to get there 
    * lay out *each* of the following weeks till end of term with brief goals for each
      * current week: finish core functionality: updating/implementing dashboard, finish studying feature, start discussing collaboration
      * week 6: finish any remaining week 5 tasks, work on collaboration, implement grouping
      * week 7: collaboration cont, exportation to quizlet
      * week 8: collaboration cont, cont working on prev features if needed or go back to extra features list and add more
      * week 9: same as above
      * week 10: beta deployed
* briefly summarize any other topics/discussions
    * discuss meeting with Tim
    * prioritizing collaboration over exportation to quizlet
    * going over updated figma design that allows for grouping notes 
    * create plan / design for how to handle stats in study flow
    * start designing collaboration 

* to-do (this meeting):
      * create plan for study flow/stats
          * threshold for learning vs mastered?
          * local stats for current session?
          * 2 types: study unlearned, study all
      * create design for collaboration
          * locking
          * sockets
          * sharing
          * simultaneous collaboration

* this week
    * revise dashboard/note summaries
    * connect dashboard to stats
    * wiring for terms page to reset attempts and to go the study page

* studying
    * insecure/eh/confident depends on cumulative stats
        * 75% or better means learned
        * 75% AND >=3 attempts means mastered
        * if neither, you're a failure
        * confidence level instead of right or wrong? - confidence set by user
            * faces?
            * got this!, eh, sos
        * aggregate face instead of percentage learned?
    * study all or study unlearned only
    * study stats
        * cumulative vs in a current session
    * rounds
        * round 1 is all cards, 2 is the ones you got wrong... ect
        * based on session stats stored in state!
    * free-study mode! to do this week
        *  see all the flashcards
        *  mark yourself correct/incorrect (but will only update cumulative stats)
            *  but this doesn't affect the studying flow 
            *  except add a checkmark if your stats indicate this term is now 'learned'
        *  free toggle through, all remain in so when you're done is up to you, not the mode

* studying takeaways/design
    * cumulative rating system
        * curr_state: 0/bad, 1/decent, 2/mastered
            * set to last rating by user
        * still keep number of attempts
    * 2 study modes
        * free-study: toggle through all flashcards, rate by confidence
        * learn-mode: quizzes you on all flashcards, if you mark check, it takes it out of the study pool
            * organized by rounds -- round 1, you study everything, round 2 just all the cards you got wrong in round 1
            * all data stored in state
                * database still reflects total attempts
                * if you get it right in round 1, then it gets moved to confident, if not no change

* Collaboration
    * sharing
    * secondary ownership
        * share table
            * note_id
            * secondary user_id
            * folder_id (optional foreign key)
    * locking
        * optional lock property note -- user_id or null
        * bit of research




Phoebe: flashcard page
Gwen: help with flashcard page, update terms page to reflect confidence scale
Nicholai: collab backend design, 3 folders issues in `Next` on zenhub
Giorgie: edit note summary to match new design, remove other summaries from dashboard, implement clicking into folders and displaying folder views on the dashboard


other to-dos:
- create folder modal
- edit folder modal
- fix delete note modal
- drag and drop notes into different folders