bc-admissions-create-manage-syllabus-schedules

name: bc-admissions-create-manage-syllabus-schedules description: Use when staff need to create and manage syllabus schedule templates, schedule timeslots, and sync them into cohort timeslots; do NOT use for syllabus JSON/version authoring or macro override content workflows. requires: []

Skill: Create and Manage Syllabus Schedules

When to Use

Use this skill when the user needs to manage class schedule templates under admissions: create/update schedule records, configure schedule timeslots, assign a schedule to cohorts, and sync those template timeslots into cohort timeslots. Do NOT use this skill for syllabus JSON content/versioning (/syllabus/.../version) or for macro-cohort overrides.

Concepts

• A syllabus schedule is a reusable template linked to one academy and one syllabus.
• A schedule timeslot stores recurrent meeting windows for that template.
• A cohort timeslot is the concrete cohort schedule used by downstream flows.
• Syncing from schedule to cohort is a replace operation: existing cohort timeslots for target cohorts are deleted, then recreated from schedule timeslots.

Workflow

1. Set request context first.

   • Send Authorization: Token <token> on protected endpoints.
   • Send Academy: <academy_id> on all /academy/... schedule endpoints.
   • Send optional Accept-Language (for example en or es) if translated error messages are needed.

2. Create or locate a schedule template for the target academy.

   • Create with POST /v1/admissions/academy/schedule.
   • Read academy-local templates with GET /v1/admissions/academy/schedule.

3. Configure schedule timeslots for that schedule.

   • Create with POST /v1/admissions/academy/schedule/<schedule_id>/timeslot.
   • Update with PUT /v1/admissions/academy/schedule/<schedule_id>/timeslot/<timeslot_id>.
   • Delete with DELETE /v1/admissions/academy/schedule/<schedule_id>/timeslot/<timeslot_id>.
   • Read list/detail using the same route family with GET.

4. Attach the schedule to cohorts.

   • On cohort create/update, set schedule to the schedule id.
   • Cohorts without schedule cannot be synced.

5. Sync schedule timeslots into one or more cohorts.

   • Call POST /v1/admissions/academy/cohort/sync/timeslot?cohort=<id[,id2,...]>.
   • This deletes existing CohortTimeSlot rows for those cohorts and recreates them from schedule timeslots.

6. Verify the resulting cohort timeslots.

   • Confirm sync response payload and then read cohort timeslots from cohort endpoints if needed.

Endpoints

Create academy schedule request

{
  "academy": 1,
  "syllabus": 12,
  "name": "Full-Time Morning",
  "description": "Monday to Friday, 09:00 to 13:00",
  "schedule_type": "FULL-TIME"
}

Create academy schedule response (201)

{
  "id": 44,
  "academy": 1,
  "syllabus": 12,
  "name": "Full-Time Morning",
  "description": "Monday to Friday, 09:00 to 13:00",
  "schedule_type": "FULL-TIME",
  "created_at": "2026-04-01T12:00:00Z",
  "updated_at": "2026-04-01T12:00:00Z"
}

List academy schedules response (non-paginated default)

[
  {
    "id": 44,
    "name": "Full-Time Morning",
    "description": "Monday to Friday, 09:00 to 13:00",
    "syllabus": 12
  }
]

Create schedule timeslot request

{
  "starting_at": "2026-05-04T13:00:00Z",
  "ending_at": "2026-05-04T17:00:00Z",
  "recurrent": true,
  "recurrency_type": "WEEKLY"
}

Create schedule timeslot response (201)

{
  "id": 301,
  "schedule": 44,
  "recurrent": true,
  "recurrency_type": "WEEKLY",
  "timezone": "America/New_York"
}

List schedule timeslots response

[
  {
    "id": 301,
    "schedule": 44,
    "starting_at": "2026-05-04T13:00:00Z",
    "ending_at": "2026-05-04T17:00:00Z",
    "recurrent": true,
    "recurrency_type": "WEEKLY",
    "created_at": "2026-04-01T12:15:00Z",
    "updated_at": "2026-04-01T12:15:00Z"
  }
]

Sync schedule timeslots to cohorts request

{}

Sync schedule timeslots to cohorts response (201)

[
  {
    "id": 801,
    "cohort": 1001,
    "recurrent": true,
    "recurrency_type": "WEEKLY",
    "timezone": "America/New_York"
  }
]

Edge Cases

• Missing Academy header on /academy/... endpoints returns 403.
• Missing capability returns 403: schedule list/detail uses read_certificate; schedule create/update/delete uses crud_certificate; schedule timeslot create/update/delete uses crud_cohort (same scope as cohort edits); cohort timeslot sync uses crud_cohort.
• Creating a schedule without syllabus returns missing-syllabus-in-request.
• Creating a schedule without academy in body returns missing-academy-in-request.
• Timeslot create/update fails with academy-without-timezone when academy timezone is not configured.
• Timeslot create/update requires both starting_at and ending_at.
• Sync fails with missing-cohort-in-querystring if cohort query param is absent.
• Sync fails with cohort-without-specialty-mode if a target cohort has no assigned schedule.
• Sync fails with without-timezone when academy timezone is missing.
• Sync is destructive for target cohorts: existing cohort timeslots are removed before recreation.
• schedule_type and recurrency_type are normalized to uppercase accepted values.

Checklist

1. Confirm headers are set correctly (Authorization, Academy, optional Accept-Language).
2. Create or select a valid schedule for the target academy + syllabus.
3. Create at least one schedule timeslot and verify it appears in timeslot GET.
4. Ensure target cohort(s) have schedule assigned.
5. Run sync endpoint with cohort querystring ids.
6. Verify sync response includes created cohort timeslots.
7. Re-check cohort timeslots and confirm they match schedule timeslot recurrence/timezone.