Status: Ready for handoff
| Table of Contents |
|---|
Handed off for UX/UI mocks and Technical Discovery
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Overview
Key Use Cases
Deliverables
In Scope / Out of Scope
...
Taxonomy Management System (Instance & Organization levels)
Tagging tool (Course & Library levels)
Content search capabilities (Course & Library levels)
In Scope / Out of Scope
Based on the above use cases, we are breaking down on high-level scope as follows:
...
In Scope
...
Out of Scope
...
Taxonomy association at the Instance and organization level.
...
Personal or course-level taxonomy association.
...
Taxonomy authoring through a CSV/JSON import process.
[Stretch] Manual taxonomy creation directly in the platform.
...
Taxonomies will be made available to all courses and libraries within an organization.
...
Ability to free-form tag without an super user-defined field.
...
Ability to create both super user-defined fields for free-form tags and closed (super user-defined fields and values) taxonomies.
...
Ability to make it required for authors to add specific tags.
...
Ability to add/remove tags at unit (outline + libraries) and component (library only for now) levels.
...
Tags will not be visible to learners.
...
Tags will be visible to authors in Studio.
...
Tagging at other levels.
...
Tagging at unit and component level.
...
Search across courses and/or libraries.
...
Free text search and tag-level search at both library and course outline levels.
...
Analytics on learner engagement with tagged content.
...
We will create a product tour for new users.
...
Ability to programmatically add tags on components/units.
MVP Specs
Users
...
Instance-Level Super User: Refers to anyone with the ability to create and manage taxonomies for an entire instance. This is particularly relevant in multi-tenant (i.e., multi-org) instances the platform. This user typically has admin controls through Django Admin. We are proposing that as part of this project, this user type can manage instance taxonomies within Studio to take advantage of what we build without having to go into Django Admin.
...
Org-Level Super User: Refers to anyone with the ability to create and manage taxonomies for an organization. We anticipate that this role will be assigned in the same way that one is granted the ability to create courses and libraries today.
...
Content Author: Refers to anyone with the Staff or Admin role on a Course Team within a Course and/or Library. These users will be able to manage tags using the tagging tool.
...
Users
Instance-Level Super User: Refers to anyone with the ability to create and manage taxonomies for an entire instance. This is particularly relevant in multi-tenant (i.e., multi-org) instances the platform. This user typically has admin controls through Django Admin. We are proposing that as part of this project, this user type can manage instance taxonomies within Studio to take advantage of what we build without having to go into Django Admin.
Org-Level Super User: Refers to anyone with the ability to create and manage taxonomies for an organization. We anticipate that this role will be assigned in the same way that one is granted the ability to create courses and libraries today.
Content Author: Refers to anyone with the Staff or Admin role on a Course Team within a Course and/or Library. These users will be able to manage tags using the tagging tool.
Learner: Refers to anyone engaging in learning on the LMS. Tags will not be visible to learners as part of this MVP.
In Scope / Out of Scope
Based on the above use cases, we are breaking down on high-level scope as follows:
In Scope | Out of Scope |
Taxonomy association at the Instance and organization level. | Personal or course-level taxonomy association. |
Taxonomy authoring through a CSV/JSON import process. [Stretch] Manual taxonomy creation directly in the platform. | |
Taxonomies will be made available to all courses and libraries within an organization. | Ability to free-form tag without an super user-defined field. |
Ability to create both super user-defined fields for free-form tags and closed (super user-defined fields and values) taxonomies. | Ability to make it required for authors to add specific tags. |
Ability to add/remove tags at unit (outline + libraries) and component (library only for now) levels. | Tags will not be visible to learners. |
Tags will be visible to authors in Studio. | Tagging at other levels. |
Tagging at unit and component level. | Search across courses and/or libraries. |
Free text search and tag-level search at both library and course outline levels. | Analytics on learner engagement with tagged content. |
We will create a product tour for new users. | Ability to programmatically add tags on components/units. |
MVP Specs
Features & Requirements
In order to realize this MVP, we believe the following features will be required. Refer to the following flow chart for more details: Tagging MVP Workflows
...