Decide a schema for AI-extracted episode resources from datatalksclub.github.io

Open
#465 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
content

Research direction

This is a design decision, not a code task: first compare the resources: shape in the upstream datatalksclub.github.io episodes (name/type/url/context) with the show-note shape in DataTalksClub/content (title/url). Then find the website parser that rejects other shapes and the legacy converter that would overwrite the new lists. Done means a recorded choice (new field, extended schema, merge, or drop) agreed with maintainers.

Written by the indexing model from the issue text.

Description

content decision needs grooming

Upstream datatalksclub.github.io (3a444397) added AI-extracted resources: lists to ~203 podcast episodes, shaped name/type/url/context (sometimes no url). DataTalksClub/content already uses resources: for show-note links shaped title/url, and the website parser rejects any other shape; the legacy converter would overwrite the new lists with show-note links. These were left out of the Sep–Oct content port. Needs a decision: adopt (new field or extended schema plus parser change), merge, or drop.

Dominant language
Python
Stars
0
Forks
0
Avg merge
32m
Merged PRs (30d)
8

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 DataTalksClub/website

All issues in DataTalksClub/website

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.