Skip to content

[Tagging] Architectural Discovery: Data models for taxonomies #60

Description

@ChrisChV

Description

Research the best possible implementation for the taxonomy data model. Explore different possibilities (JSON vs database relations) for the use cases defined in the reference links below. The supported field types are:

  • Free form field that accepts any text (with autocomplete suggestions).
  • Single select: a selection from a list of options.
  • Multi select: one or more selections from a list of options.

Explore what is the best approach for storing taxonomies in the platform and come up with the database modeling for a taxonomy system that supports those characteristics.

  • These taxonomies will be used to validate and render tag fields on the frontend.
  • The models should also allow conditional nesting for the single select fields, allowing up to 3 levels of linked child items.
  • The data models should also consider that taxonomies can be instance wide or per-organization (check the Users section of the MVP specs for details on the expected permissions).
  • Taxonomies can be turned “on” or “off” per context: instance, organization and course.

Reference documents:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions