Use-cases

 

MVP

NISHTHA

(Check with program if they can send discussion forum link to just 500-1000 people. Because verification of profiles at the same time needs some complex integration to do with DIKSHA)

  • NCERT

    • Course 1

      • Batch 1

      • Batch 2

    • Course 2

      • Batch 1

      • Batch 2

 

  • Public Categories

    • Textbooks, Content

    • DIKSHA Announcements

  • Private Categories

    • Course Batches

    • DIKSHA Groups

    • Vidyadaan Projects

  • Courses

    • TenantId-CourseId-BatchId - 2134763-do_23456-3282003

      •  

Extended schooling - Groups

  • State

    • District

      • Block > Cluster (Can be skipped for MVP, since this info might not be there for all users)

        • School 1

          • Group 1 - we will use group creator’s school association to map this hierarchy

          • Group 2

        • School 2

          • Group 1

          • Group 2

  • Custodian org (non-verified users without a state/school info)

    • (Geo-based hierarchy? Unless verified locations, not going on this route)

    • Group 1

    • Group 2

    • Group 3

Vidyadaan

  • Tenant

    • Project 1 (all contributors to a project get access)

      • General

      • Collection 1 (Check with Solution Manager if the categories can be frozen - so that no new topics can be created within a collection. Any generic discussion could happen in General).

        • Content 1 (topic)

        • Content 2 (topic)

      • Collection 2

    • Project 2

      • General

      • Collection 1

      • Collection 2

Authoring tool

(Check with SM about hierarchy and permissions: All people with creation access get access to all categories under this)

  • Tenant 1

    • General discussions

    • Best practices

    • Content 1

      • (Questions as topic)

    • Content 2

      • (Questions as topic)

  • Tenant 2

Collection/content level discussions (use tags as do_id or similar)

  • Tenant 1

    • Course 1

      • General

      • Content 1

      • Content 2

    • Textbook 1

      • General

      • Content 1

      • Content 2

  • Tenant 2 (reuses course1 from tenant 1)

    • Course 2 (clone of Course 1 structure)

      • General

      • Content 1 (sibling of Course 1 > Content 1 etc.)

      • Content 2.1 ( derivative of Content 2 (child) )

Tenant level discussions

  • Tenant

    • District

      • Block

        • Cluster

  • Board

    • Medium

      • Class

        • Subject

Prefer TDBC instead of BMCS because of scope for administrative push to ensure good moderation / resolution of questions happen. Else you’ll have experts from different locations, but no accountability.

Mainstream

User’s view when they come into https://<sunbird>/discussions

(This might be redundant since DIKSHA discussions should ideally be directly accessed through DIKSHA portal or mobile app, in context, with intelligent ordering based on popularity/proximity/relevance - without having to navigate through a tree of categories)

Using '>' below since Confluence doesn’t allow more than 4 layers in bullets.

  • DIKSHA Announcements

  • DIKSHA Help

  • Tenant name

    • Announcements

      • Administration announcements

      • School HM announcements

      • <topics as individual announcements for the teaching force (or students)>

    • Discussions

      • District

        • Block > Cluster

          • School (private - to school members)

            • Group (private - to group members)

    • Courses

      • Course name

        • Batch

          • District (avoid this and below, unless far too many users)

            • Block > Cluster

    • Books

      • Subject

        • Book title

          • District

            • Block > Cluster

 


Open Questions:

  • Category management by org admins? - they have DIKSHA groups and can manage discussions using them

  • How do we moderation @ scale for open categories (e.g Textbook)?

    • one way discussion like announcements?

    • throttling topics

    • ability to flag topics - reputation to be impacted by flags

    • reputation based access to create topics, reply, and moderation

  • How do we get answers @ scale for open categories (e.g Textbook)?

  • Get topics and influencers from same location, profile..

ToDos:

  • Hide the category dropdown in post topic/reply screen

  • Hide the breadcrumbs

((( IGNORE ALL THE TEXT BELOW, BELOW ARE OLDER THOUGHTS KEPT AS AN INITIAL GUIDE )))

End-user Experience

User - Teacher

  1. Teacher should be able to see a discussion forum when she creates a group with other teachers/students.

  2. Teacher should be able to join forums that are of interest to her.

  3. Teacher should be able to leave non-mandatory forums that she is part of.

  4. Teacher should be able to mute non-mandatory forums that are not of interest to her.

  5. Teacher (if she’s an admin) should be able to set forum visibility to public/private/only-tenant/only-server-admins, in order to keep conversation within that forum private from various groups, or invite interactions from outside the group, as she sees fit.

  6. Teacher sees a space within the portal where she can see:

    1. Discussions that she’s participating in or watching.

    2. Popular/trending discussions in:

      1. the forums that she’s part of.

      2. areas of her interest (E.g. Physics subject) ordered by her (a) language mediums, (b) geography, (c)boards .

      3. Across the platform with priority for her (a) tenant.

    3. Discussions that members within her group(s) are participating in (e.g. liking, voting, commenting, asking etc.).

    4. Shortcuts to the various discussion forums that she is part of

      1. Courses that she’s taking

      2. User groups that she’s in

      3. Collections she’s played / downloaded (e.g. textbooks she’s using)

  7. Teacher can go to discussion boards, and based on permission:

    1. See ongoing discussions (sort by trending, new, recently updated etc.)

    2. Start a discussion

    3. Reply as a post on a discussion

    4. Vote/like/comment on a post within a discussion

    5. Flag any post / discussion with accompanying reason

  8. Teacher should be able to inspect other user profiles (by clicking on that user’s name/profile) in order to:

    1. see all comments/posts by the user (ala reddit/quora)

    2. follow the user, to be notified of their activity in their forums feed (ala linkedin)

    3. report user (for any objectionable content, consistent breaking of rules), and pointing to specific posts that are examples of said unruly behaviour.

User - School administrator / resource person

  1. Resource person should be able to create a group between them and the various teachers that come within their sphere of influence. Once they do, it should automatically have a discussion forum attached.

  2. Resource person should be able to join forums with their peers (resource people and their managers).

  3. All use-cases above with teachers apply here as well.