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

  1
  • Cluster 1

    • > 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

...

• 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)

...

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

...