Extract source-backed lab timetable entries with effective dates

Open
  • Is something wrong?
#31 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, node.js
Domain
backend, data

Research direction

Read AGENTS.md and docs/PROJECT_CONTEXT.md, then review src/labs.js, src/resources.js, and src/pdf.js alongside issue #30, which must land first. The issue asks for a new schedule model and conservative extraction from HTML tables and text PDFs, with synthetic fixtures covering the listed edge cases. Discuss the design with the maintainer before implementation; completion means the acceptance fixtures pass and unsupported entries cannot become confirmed schedules.

Written by the indexing model from the issue text.

Description

area:backend area:docs priority:high status:blocked type:feature

Part of #28 · Target: Scheduling / v0.5

Goal and scope

Define normalized entries with course/group, local weekday/start/end/room, timezone, explicit teaching period or selected dates, source/page and checkedAt. Parse supported HTML tables and text-PDF layouts conservatively; retain ambiguity and overlapping versions.

Implementation starting points

src/labs.js, src/resources.js, src/pdf.js, new schedule model. Follow AGENTS.md and docs/PROJECT_CONTEXT.md; reuse existing authorization, safe-error and synthetic-fixture patterns. New runtime dependencies need a documented reason.

Dependencies and readiness

Depends on #30. Discuss the design before starting implementation; dependent contracts must land first.

Out of scope

No OCR, roster-based group inference, implicit indefinite recurrence or automatic calendar writes.

Acceptance criteria and test plan

Synthetic HTML/PDF fixtures cover date ranges, two groups, unknown end/room/timezone, overlapping versions, image-only and partial sources. Source/page references survive extraction; unsupported entries cannot become confirmed schedules.

Run the relevant offline tests, npm run check and git diff --check; runtime changes also require npm test and npm audit. Report checks not run. No faculty credentials or private course material are required for a contribution.

Contributing

Comment here before starting so the maintainer can coordinate the approach and avoid duplicate work. Fork the repository, branch from master, and open a focused PR referencing this issue. No assignee or delivery deadline is set; required checks and review apply.

Dominant language
JavaScript
Stars
0
Forks
0
Avg merge
1h 20m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mahmutmft/courses-mcp

All issues in mahmutmft/courses-mcp

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.