Tagging API Endpoints Within Course

[armintalaie]

Tagging System for courses

Overview

Add tagging functionality at the course level to organize course content

Database Tables

• course_tags table: store course-level tags
  • id: UUID // this can actually be an int
  • course_id: UUID (foreign key)
  • name: text
  • colour: text (optional)
  • created_at, updated_at timestamps
  • parent_id Default is NULL
  • unique constraint on (course_id, name)

API Endpoints

These will be under /courses/{course_id}/tags:

• POST: create a new tag for course

  • Validate tag inputs (name, color)
  • Check user is course admin/maintainer
  • Ensure tag name is unique within course

• GET: list all tags for course

  • Return tags if user has access to course (access? Courses API Endpoints #79 )

• PATCH /{tag_id}: update course tag

  • Check user is course admin/maintainer
  • Update tag properties (name, color)
  • Ensure new name doesn't conflict

• DELETE /{tag_id}: delete course tag

  • Check user is course admin/maintainer
  • Remove tag from all course content

• GET /{tag_id}/content: get tagged content

  • List all course content with this tag
  • Check user course access

Tasks:

• Write migration scripts
• Implement tag validation models
• Add permission checks
• Write CRUD operations
• Add tag colour validation