# ScholarX: February Edition **URL:** \ **Category:** ScholarX\ **Created:** [October 28, 2021, 4:31pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359 "2021-10-28T16:31:11Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\ **Post date:** [October 28, 2021, 4:31pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/1 "2021-10-28T16:31:11Z")
As we are successfully done with the pilot program. We started gathering feedback from the mentors, mentees and from the scholarX team as well. After having multiple discussions with the feedback we started getting ready for the ScholarX 2022. We got some good [requirements](https://docs.google.com/document/u/1/d/1Ihq5_WETVkQRaDmgvSJjFN3TNdft-EW8dz3wIXgourI/edit?usp=sharing) from ScholarX team. We had discussions about whether we are going to use the architecture or not can come to the conclusion that we are going to use the same architecture without redesigning the whole thing again. We will be changing the flow and there will be new states. One of the main things that going to change is that we are going to have this hybrid mentor selecting method where admins first select mentees for the mentors and the mentor does the selecting from them. This thread will be updated with the other documents in the upcoming weeks. Here are the [meeting notes](https://pad.riseup.net/p/Kjapmu5nirPqgexK6kJI-keep) if you are interested. ---
**Author:** ![Pasindu\_Rupasinghe](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/pasindu_rupasinghe/32/612_2.png) [@Pasindu\_Rupasinghe](https://sef.discourse.group/u/Pasindu_Rupasinghe)\ **Post date:** [October 29, 2021, 2:29am UTC](https://sef.discourse.group/t/scholarx-february-edition/359/2 "2021-10-29T02:29:14Z")
Hi all, As we discussed this Monday (2021/10/25) ScholarX Squad standup call I was assigned to identify the flow and design the flow diagram of the ScholarX February Edition. To initiate this task I had a call with @jaye and finalize the flow diagram as accordingly. Flow diagram design - ![](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/6a17952b6807e0ec190f1bc679b866f8f639efc9.jpeg) This will be the link to the figmaJam board of this flow diagram. [Link ](https://www.figma.com/file/HcS9JHEtHvn08qpQBGBxcB/ScholarX-v2) When identifying the assigned mentees to the mentor stage I divided it into three sub-main flows, 1. Admin - Mentee Filteration 2. Mentee approval Flow (by Mentors) 3. Wild card round (by Admins) * * * 1. Admin - Mentee Filteration ![](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/6051a3393fc884a13a3d37aa3f13c358933074e6.jpeg) * * * 1. Mentee approval Flow (by Mentors) ![](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/938b72a7a8422c59a0217074f3144c38f7894d0a.jpeg) * * * 1. Wild card round (by Admins) ![](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/6ed5bd0c4a071572b9ce4972894cc9bed32301c7.jpeg) * * * Those flow diagrams will be also visible on the [figmaJam](https://www.figma.com/file/HcS9JHEtHvn08qpQBGBxcB/ScholarX-v2) board. Also to reflect the decisions of the application status, we assigned some values for those decisions. Hereby I will add a table including those status values, stage according to the status code, and also the person who will replace the status code. | Status code | Meaning | By whom this status code will replace | | --- | --- | --- | | Pending | Initial state of the application. The application (i.e. Mentee) is not yet reviewed. | Default | | Assigned | Metee assigned to a mentor by admin | Admin/ Mentor | | Pool | Mentee is reviewed by an admin, but not assigned to a mentor | Admin | | Discarded | Mentee has been discarded by admin due to incompleteness or the application isn’t suitable for further review | Admin | | Rejected | Mentee rejected by the mentor | Mentor | | Approved | Mentee approved for by the mentor | Mentor | | Failed\_From\_WildCard | Mentee rejected from the wild card round | Admin | We added comments on the [figmaJam](https://www.figma.com/file/HcS9JHEtHvn08qpQBGBxcB/ScholarX-v2) board for Those stages with the status code and also the assigned mentor on the current stage. Please leave your suggestions here as well as your comments to improve this flow diagram. Thank you. ---
**Author:** ![jaye](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/jaye/32/810_2.png) [@jaye](https://sef.discourse.group/u/jaye)\ **Post date:** [October 29, 2021, 6:05am UTC](https://sef.discourse.group/t/scholarx-february-edition/359/3 "2021-10-29T06:05:22Z")
Thanks, @anjisvj for initiating the thread! Also thanks @Pasindu_Rupasinghe for posting a detailed update on the flow. @Gravewalker what you said was true; we were able to find many little scenarios that didn’t come to our minds on the initial discussion. We came up with some extra fancy status codes; we can rename them later, both Pasindu and I was terrible at naming them. 😁 As Pasindu has stated, the intention of introducing new status is to reflect the decisions taken by each role. ex: If the status is `POOL` that means the application is reviewed by an admin, but not assigned to a mentor because they think there are no mentor fits for the application at that moment. Go check out the [figmaJam](https://www.figma.com/file/HcS9JHEtHvn08qpQBGBxcB/ScholarX-v2) and let us know your thoughts. @Pasindu_Rupasinghe, I would highly recommend you convert it into a blog. > “In order for connection to happen, we have to allow ourselves to be seen—really seen.” > —Brené Brown Excerpt From Show Your Work!: 10 Ways to Share Your Creativity and Get Discovered Kleon, Austin ---
**Author:** ![Pasindu\_Rupasinghe](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/pasindu_rupasinghe/32/612_2.png) [@Pasindu\_Rupasinghe](https://sef.discourse.group/u/Pasindu_Rupasinghe)\ **Post date:** [October 29, 2021, 6:37am UTC](https://sef.discourse.group/t/scholarx-february-edition/359/4 "2021-10-29T06:37:49Z")
Thank you! @jaye > [@jaye](#): > > I would highly recommend you convert it into a blog. Also thanks for the suggestion! 😁 ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [October 30, 2021, 1:54pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/5 "2021-10-30T13:54:46Z")
Me and @kumuditha_udayanga were working on the wireframes of the ScholarX February Edition. 2021-10-28T18:30:00Z we had a discussion with @anjisvj and created the initial wireframes for the new program states. I used components created by Heshan in version 1.0. Link: [https://app.diagrams.net/#G1870vcUE9U2\_D7dDnUMqav\_Og8bkb21kv](https://app.diagrams.net/#G1870vcUE9U2_D7dDnUMqav_Og8bkb21kv) > **[SX February.drawio](https://drive.google.com/file/d/1870vcUE9U2_D7dDnUMqav_Og8bkb21kv/view?usp=sharing)** > > Google Drive file. ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [November 10, 2021, 12:54pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/6 "2021-11-10T12:54:38Z")
These are the updated wireframes. Admin Dashboard: ( **Outdated** ) ![SX February-Admin-New.drawio](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/5c4deecbbfbcb1c9249bcaaa13d467ad3ca8c61b.jpeg) Mentor’s workflow: ![SX February-Mentor -New.drawio](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/8c1323000273c7cc650404f1074745f01ca34fda.jpeg) Mentee’s workflow: ![SX February-Mentee - New.drawio](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/5d65da6c8bd69b2d7bd3f8019402fbcced145678.jpeg) Note: Homepage and the User Login Flow are similar to what we had in version 1. **Updated Admin Dashboard** ([ScholarX: February Edition - #8 by piumal1999](https://sef.discourse.group/t/scholarx-february-edition/359/8)): ![SX February-Admin-New.drawio (2)](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/4488c8d0d03f3021eefbb3281f205ad827f9e3a5.jpeg) ---
**Author:** ![Gravewalker](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/gravewalker/32/12_2.png) [@Gravewalker](https://sef.discourse.group/u/Gravewalker)\ **Post date:** [November 13, 2021, 2:52am UTC](https://sef.discourse.group/t/scholarx-february-edition/359/7 "2021-11-13T02:52:14Z")
The main API endpoints can be found here, > **[ScholarX Version 2 API Endpoints](https://docs.google.com/document/d/1SFxgduCtF8rz7Mc6SKAA91hF4C6gQIITM9FkobyFWIU/edit?usp=sharing)** > > ScholarX Version 2 API Endpoints Admins Endpoints to get the list of mentors There should be an endpoint Approve/Reject mentor by the mentor Id There should be endpoints to get the mentee applications by primary mentor (and maybe secondary... There could be some endpoints that I’ve missed and some I’ve left out because it’s already implemented. Need to go through these and have a discussion. ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [November 13, 2021, 10:03pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/8 "2021-11-13T22:03:59Z")
**Update:** 2021-11-12T18:30:00Z We had a discussion to decide whether we need a separate UI to assign mentees in a mentor specific way (select a mentor-\>add mentees to the remaining slots). If we use that way, when the admin clicks a mentor it will load a UI very similar to the ‘Manage mentees’ view. In that UI, all the mentees will be shown. So we decided to use the existing wireframe with a small update. (A sidebar to show mentor slot count) ![SX February-Admin-New.drawio (2)](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/4488c8d0d03f3021eefbb3281f205ad827f9e3a5.jpeg) ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [November 14, 2021, 9:36am UTC](https://sef.discourse.group/t/scholarx-february-edition/359/9 "2021-11-14T09:36:48Z")
I updated the existing ERD with some of the new attributes. [https://app.diagrams.net/#G1upQ34lQZ8Qlak5Ix35BxOjzLhjEJcuXj](https://app.diagrams.net/#G1upQ34lQZ8Qlak5Ix35BxOjzLhjEJcuXj) ![ScholarX February Edition ERD.drawio (1)](https://global.discourse-cdn.com/free1/uploads/sef/original/1X/5d1483370929282252199e74456b442f2d3fb261.jpeg) Can we use enums for the data required for filtering? (category, field of expertise). Or is it possible to do it within the frontend itself as plain text? ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [November 20, 2021, 12:53pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/10 "2021-11-20T12:53:17Z")
> [@Gravewalker](#): > > The main API endpoints can be found here, > > [https://docs.google.com/document/d/1SFxgduCtF8rz7Mc6SKAA91hF4C6gQIITM9FkobyFWIU/edit?usp=sharing](https://docs.google.com/document/d/1SFxgduCtF8rz7Mc6SKAA91hF4C6gQIITM9FkobyFWIU/edit?usp=sharing) > > There could be some endpoints that I’ve missed and some I’ve left out because it’s already implemented. I went through this document again by comparing the existing endpoints. As I found, we need 2 new admin endpoints and 1 minor change in a non-admin endpoint. New endpoints: 1. Set assigned mentor of a mentee 2. Change the state of a mentee Minor changes: 1. Update the “Get my mentee applications of a program” endpoint to get only 1 mentee application Other than that, we’ll have to update the DTOs since we are introducing some new attributes for mentees and mentors. ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [November 21, 2021, 11:28am UTC](https://sef.discourse.group/t/scholarx-february-edition/359/11 "2021-11-21T11:28:30Z")
When a mentor is applying for the program, we need to ask for the details needed for the filtering and mentor profile. Up to now, these are the things we are going to ask from the mentor: 1. Category - Asking to select 1 category from the given categories (Life Sciences, Computer Science, Physical Science, Engineering, Other etc.) - This can be used for filtering 2. Area(s) of Expertise - Like subcategories (Microbiology, Neuroscience etc.) - I think it is not practical to provide pre-defined options, because there can be hundreds of fields. - So this can’t be used for filtering - Getting their answer as plain text 3. Institution - University or the place that they work at - Same as the previous one - Getting their answer as plain text 4. Position - Could be phD, SE etc - Getting their answer as plain text 5. Bio - Small description about them - We can skip this if this is not needed since we are getting the LinkedIn profile 6. No. of Mentee Slots - Number of mentees they can mentor 7. Projects(optional) - Some details about their projects - Getting their answer as plain text According to the above details, only the category can be used to filter the mentors. And other fields will be shown on the mentor profile. Is it ok for the February edition, or do you have any other suggestions? [@EngTeam](https://sef.discourse.group/groups/engteam) @jaye @akshika47 @Dharana_J ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [November 27, 2021, 3:55pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/12 "2021-11-27T15:55:38Z")
These are the fields we are going to add to the mentee profile. We ask these things from the users when they are applying to be a mentee. 1. Primary Mentor - Choose from a drop-down list 2. University - Plain text input 3. Course/Major - Plain text input 4. Year of Study - Plain text input 5. Intent for a mentor - Small description - Plain text input 6. Reasoning for the choice - Small description - Plain text input Let me know if anything is missing. cc: @jaye @anjisvj @Gravewalker @cmdrGuyson ---
**Author:** ![Gimhan\_minion](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/gimhan_minion/32/109_2.png) [@Gimhan\_minion](https://sef.discourse.group/u/Gimhan_minion)\ **Post date:** [December 1, 2021, 7:49pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/13 "2021-12-01T19:49:17Z")
> > > \## Purpose > The purpose of this PR is to fix #218 > > \## Goals > To add new mento…r details to the model class > > \## Approach > Add the following fields to the Mentor Model > > \- Category (category) > \- Area(s) of Expertise (expertise) > \- Institution (institution) > \- Position (position) > \- Bio (bio) > \- No. of Mentee Slots (slots) > > \### Screenshots > !\[image\](https://user-images.githubusercontent.com/60275681/144302869-2ab78608-43bc-485a-aefa-872d8ce4be06.png) > (Screenshot of generated mentor table) > > \## Checklist > \- \[x\] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets. > \- \[x\] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices ) > \- \[x\] My code follows the style guidelines of this project > \- \[x\] I have performed a self-review of my own code > \- \[\] I have commented my code, particularly in hard-to-understand areas > \- \[\] I have made corresponding changes to the documentation > > \## Test environment ---
**Author:** ![jaye](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/jaye/32/810_2.png) [@jaye](https://sef.discourse.group/u/jaye)\ **Post date:** [December 2, 2021, 1:21am UTC](https://sef.discourse.group/t/scholarx-february-edition/359/14 "2021-12-02T01:21:58Z")
@anjisvj @piumal1999 Have you defined the scope and a deadline for the current sprint? It seems there are only 2 issues in the current sprint. [https://github.com/orgs/sef-global/projects/5/views/1](https://github.com/orgs/sef-global/projects/5/views/1) ---
**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\ **Post date:** [December 5, 2021, 12:04pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/15 "2021-12-05T12:04:00Z")
## Development Sprint #1: Scholarx [February Edition](https://sef.discourse.group/t/scholarx-february-edition/359) ### **From:** 2021-12-04T18:30:00Z to 2021-12-11T18:30:00Z **Frontend** : - [Remove dynamic mentor questions from the admin view](https://github.com/sef-global/scholarx-frontend/issues/252) - @kumuditha_udayanga - [Remove mentor confirmation UI and the relevant API](https://github.com/sef-global/scholarx-frontend/issues/260) - @cmdrGuyson - [Migrate Travis CI workflows to Github Actions](https://github.com/sef-global/scholarx-frontend/issues/259) - @anjisvj **Backend** : - [Remove confirmMentor endpoint and service method](https://github.com/sef-global/scholarx/issues/223) - @Gimhan_minion - [Endpoint used for Approve/Reject mentees is not validated](https://github.com/sef-global/scholarx/issues/226) - @piumal1999 - [Mentors should be able to update all fields using applyAsMentor endpoint](https://github.com/sef-global/scholarx/issues/228)- @piumal1999 cc: @jaye @Gravewalker ---
**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\ **Post date:** [December 11, 2021, 2:39pm UTC](https://sef.discourse.group/t/scholarx-february-edition/359/16 "2021-12-11T14:39:07Z")
## Development Sprint #2: Scholarx [February Edition](https://sef.discourse.group/t/scholarx-february-edition/359) ### **From:** 2021-12-11T18:30:00Z to 2021-12-17T18:30:00Z **Frontend** : - [Add the mentor search in the manage mentees view](https://github.com/sef-global/scholarx-frontend/issues/257) - @kumuditha_udayanga - [Remove mentor confirmation UI and the relevant API](https://github.com/sef-global/scholarx-frontend/issues/260) - @cmdrGuyson - [Update Admin Change State UI](https://github.com/sef-global/scholarx-frontend/issues/267) - @sumedha **Backend** : - [Remove confirmMentor endpoint and service method](https://github.com/sef-global/scholarx/issues/223) - @Gimhan_minion - [Create an admin endpoint to change mentee states](https://github.com/sef-global/scholarx/issues/243) - @kumuditha_udayanga - [Create an admin endpoint to change assigned mentor of a mentee](https://github.com/sef-global/scholarx/issues/228)- @piumal1999 - [Update Program State column length](https://github.com/sef-global/scholarx/issues/253) @sumedha cc: @jaye @Gravewalker