Skip to content

GraphSRS V? Improvements #45

Description

@Marviel

This is a list of issues and improvements we'd like to make to GraphSRS in future versions.

Issue: Nodes require differing taxonomies / Taxonomies Don't Apply Across All Concepts...

Example: If I am learning music, I could start trying to REMEMBER note name <> sound combinations, then try to UNDERSTAND what notes fit together, etc. But actually, one of the best ways to start learning music (at least, for me) is to start trying to play a song I know.

In the current GraphSRS learning taxonomy model, all nodes share a taxonomy, and that taxonomy has a shared ordering for every node -- which means that creation would come last.

I suppose this does depend on one's definition of Creation.

Create was defined in Bloom's taxonomy as "Creating new works".

Perhaps in my given example, the taxonomy is actually the same, and one must simply remember the notes to a song.

But for music, this skill tree still feels... wrong.

Like, for instance, a low node on the skill tree for music comprehension would be "recognize a note" which doesn't really have a "create" phase. Would "create" be the ability to create a note recognition exercise for someone? What's the utility in that?

No, I think this model falls down for some topics, perhaps quite frequently. We need better definitions here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions