Level 2 features define data contained in the system and how it inter-relates.
option to merge in upstream changes
- author creates project A includes content from project A, project A changes
grab variably sized chunks of existing content of varying granularity
linking content to calendar dates (advance, reverse, goto, block on conditional)
flexibility/adaptability of learning experiences
- single content item that interacts with learner in adaptive way
- step A prompts learner for a choice that later determines how content B is presented
- step A infers user work or performance and gives content that is appropriate to that learner at step B
- content has rules for what it presents to each learner
flexible workgroups
- dynamic and quick workgroups (individual, whole class, at table, today's buddy, etc)
- groups share/review work of other groups
- every action linkable to a group
capturing/recording learner experience
- summaries and queries on the experience of the learner
system-wide tracking
Matt Fishbach writes: Shared Datapool for new Scaffold Questions. If we add new scaffolding that allows a project to present discrete multi-choice questions to the user, we should think about how these questions are stored and shared. I'd love to see a system where:
- While creating a project an Author can review a subject-sorted database of questions which they can use in the project (this collective pool grows over time as more and more people create projects). Questions can be used across different projects.
- Student Created Questions. I'm hoping we can allow advanced students to create new questions for a project, which if approved by the teacher can be added to the pool of questions that can appear for future users of the project (perhaps even giving credit to the original writer of the question).