Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Mentor Views #78

Closed
tamargoadam opened this issue Jul 10, 2020 · 1 comment
Closed

New Mentor Views #78

tamargoadam opened this issue Jul 10, 2020 · 1 comment
Assignees
Labels
frontend This issue is related to the client folder MVP Minimum viable product
Milestone

Comments

@tamargoadam
Copy link

For the system, mentor and tutor will be the same user: no difference in features they will use.
There will not be mentor/teacher switching.
Teachers and mentors can have multiple classrooms. However, they all move in groups.
A mentor can work with two or more teachers.

Proposed Flow:

1.) Once logged in, the Teacher/Mentor is welcomed with a view that displays the classrooms in which s/he works:

image

  • Each classroom displays the number existing students and two buttons: one to view students, and another one to view days/lesson plan.
  • Note: if join code is moved to the classroom rather than session, cards should display number of students, join code, and buttons to view roster and view days

2.) When the teacher/mentor selects "View Roster", this view is displayed. It has a list of students, including the basic information on name, lastname, animal, and basic options on editing, deleting and viewing the information of the student.

image

  • Edit: Useful in case students misspell their first or last names.
  • Remove: In case the teacher wants to remove a student from the classroom.
  • View: In case we want to have more information to display to the teacher/mentor.
  • Two icons were placed top-right: one to return to the main menu (classrooms), and another one to add a student: maybe create a new one, or add one from the system (?)

3.) When the teacher/mentor selects "View Days"(?), this page is displayed. It gathers information of all the days considered for that particular classroom.

image

  • Here, it is important to note that each session has 4 potential operations:
  • View Day- Displays the activities in the day and extra information.
  • Hide - hides the session from the student's view (in case we want to categorize per classroom).
  • Unhide - unhides the session from the student's view (same: in case we want to categorize per session).
    • May implement using toggle
  • Remove - This is an optional feature. It will be available when there are no submissions. However, when submissions have been made, it will be hidden.
  • The top icons involve "main menu" and adding a new session (creating new join code and etc).
  • Note: again, sessions will likely not be the term used for these groupings of activities due to model change.

4.) When the "View Day"(?) button is clicked, the Teacher/Mentor gets to see the activities in the day.

image

  • Hide/Unhide do correspond to what we currently have in the other view (for join code).
  • When pressed the + icon in the top (right), the Teacher/Mentor gets to go to an activity catalogue...
  • Note: the name of the day or other entity under which activities are organized will be displayed, unlikely to be session.

5.) S/he will be able to add activities (created by the content creator...not the teacher) to the session (join code). S/he can search by topic, date (?), name, etc...

image

6.) Finally, when viewing an activity, the view is the same as with the student but without the submissions/load/save feature.

image

@tamargoadam tamargoadam added MVP Minimum viable product frontend This issue is related to the client folder labels Jul 10, 2020
@tamargoadam tamargoadam added this to the 0.4 milestone Jul 10, 2020
@tamargoadam tamargoadam self-assigned this Jul 10, 2020
@tamargoadam
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend This issue is related to the client folder MVP Minimum viable product
Projects
None yet
Development

No branches or pull requests

1 participant