-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
RFCRequest For CommentsRequest For Comments
Description
This memo tries to lay out the needs and objectives of using TLS in a classroom setting and think about how they might be implemented within the current system. Based on previous conversations, here are the components considered:
- 'tls-teacher', a new role that will have the ability to create a 'tls-class' and admit students to this class.
- 'tls-class' is a data structure that is created and owned by (one or more) 'tls-teacher's. It holds the members of the class, which are registered as 'tls-user's by the teacher, upon request, and at the same time enrolled in the 'tls-class'. The class has a period of activity, after which the students will revert to be 'ordinary' tls-users.
- The 'tls-class' also holds a list of reading materials, which contains pointers to complete or partial texts that are available in the TLS. For the sections contained in the class, the display of SWL annotations will be blocked for the time of the class or until the owner of the class releases them. Students will be able to create their own annotations, which are visible to themselves and the teacher.
- Since all existing annotations can be seen by the guest user without login, the students still have the means to see the these annotations, a fact the teacher has to bear in mind when using assignments within the TLS for grading.
- For students enrolled in the class, the list of texts will display on the home screen upon login, in the place of the current list of recently visited texts. The teacher might add additional information to this list.
- The teacher might define an enrollment period, during which he can admit students to the system and to his class. The students will apply in the sign-up screen, to which the classes will be added as options.
Comments?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
RFCRequest For CommentsRequest For Comments