moved data to its own module

This commit is contained in:
2020-10-01 13:18:30 +02:00
parent 73c9a2825a
commit 07798009e0
3 changed files with 79 additions and 80 deletions

View File

@@ -17,11 +17,12 @@ A lot of the time the best way to learn is to work on a project that uses the sk
## Proposed Solution
Simple navigation across and within learning "modules", enabled by
1) a plugin linking the content with the navigation
2) JSON for every module/submodule indicating their _prerequisites_ and intended learning _outcomes_
1) a plugin linking the content with the navigation
2) JSON for every module/submodule indicating their _prerequisites_ and intended learning _outcomes_
### Creating the JSON Metadata
(see JSON example under "API/Recorded Media" below)
For someone familiar with a unit of learning -- say, a 45-minute tech talk -- they may be able to create the JSON by hand without a lot of trouble.
For large bodies of media, it might be better to try to automate this using transcripts + NLP, perhaps by including existing metadata about the media such as tables of contents, descriptions, etc.
@@ -32,13 +33,13 @@ For large bodies of media, it might be better to try to automate this using tran
## Preexisting Assets
There is a massive and growing body of media which is fodder for annotation and modularization:
1) podcasts
2) conference talks
3) news media
4) MOOCs
5) topical/long-form YouTube
6) docuseries
7) ...
1) podcasts
2) conference talks
3) news media
4) MOOCs
5) topical/long-form YouTube
6) docuseries
7) ...
# API

View File

@@ -3,7 +3,8 @@
import { onMount } from 'svelte';
import Modules from "./Modules.svelte"
import { currentModule } from "./stores.js"
import { currentModule } from "./stores"
import DATA from "./data"
let video, position, interval;
@@ -41,81 +42,11 @@
return module.name
}
}
/* return DATA.modules[0].name */
}
const DATA = {
platform: "YouTube",
uid: "ZPxuohy5SoU",
prereqs: [
"I know Python to some extent.",
"I know data science and ETL to some extent."
],
outcomes: [
"I know how to use Kedro in a basic way."
],
modules: [
{
name: "Intro: Tom Goldenberg",
start: 29,
end: 116,
outcome: "know who Tom Goldenberg is"
},
{
name: "Intro: QuantumBlack",
start: 116,
end: 177,
outcome: "know something about QuantumBlack"
},
{
name: "Intro: Agenda",
start: 177,
end: 242,
outcome: "know what the agenda is"
},
{
name: "Intro: Kedro",
start: 242,
end: 523,
outcome: "know what Kedro is"
},
{
name: "Intro: kedro-viz",
start: 523,
end: 558,
outcome: "know what kedro-viz is"
},
{
name: "Intro: MLFlow",
start: 558,
end: 871,
outcome: "know what MLFlow is"
},
{
name: "installing Kedro and prereqs",
start: 871,
end: 939,
outcome: "have pandas/conda and kedro installed"
},
{
name: "create a virtual environment",
start: 939,
end: 1038,
outcome: "have an activated virtual environment for playing with kedro (`kedro info` produces something)"
},
{
name: "create a kedro project",
start: 1038,
end: 1175,
outcome: "create a new kedro project"
},
],
}
</script>
<main>
<h1>Modulearn</h1>
<Youtube bind:this={video} videoId={DATA.uid} />
<Modules on:selectModule={onSelectModule} modules={DATA.modules} />
</main>

67
modulearn/src/data.js Normal file
View File

@@ -0,0 +1,67 @@
export default {
platform: "YouTube",
uid: "ZPxuohy5SoU",
prereqs: [
"I know Python to some extent.",
"I know data science and ETL to some extent."
],
outcomes: [
"I know how to use Kedro in a basic way."
],
modules: [
{
name: "Intro: Tom Goldenberg",
start: 29,
end: 116,
outcome: "know who Tom Goldenberg is"
},
{
name: "Intro: QuantumBlack",
start: 116,
end: 177,
outcome: "know something about QuantumBlack"
},
{
name: "Intro: Agenda",
start: 177,
end: 242,
outcome: "know what the agenda is"
},
{
name: "Intro: Kedro",
start: 242,
end: 523,
outcome: "know what Kedro is"
},
{
name: "Intro: kedro-viz",
start: 523,
end: 558,
outcome: "know what kedro-viz is"
},
{
name: "Intro: MLFlow",
start: 558,
end: 871,
outcome: "know what MLFlow is"
},
{
name: "installing Kedro and prereqs",
start: 871,
end: 939,
outcome: "have pandas/conda and kedro installed"
},
{
name: "create a virtual environment",
start: 939,
end: 1038,
outcome: "have an activated virtual environment for playing with kedro (`kedro info` produces something)"
},
{
name: "create a kedro project",
start: 1038,
end: 1175,
outcome: "create a new kedro project"
},
],
}