Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

 Template

Please include:

  • Overview: 1-2 sentences that describe the project

  • Problem: 1-2 sentences that describe the primary user problem, challenge or barrier

  • Use cases: As a [course author author/instructor/learner], I need to be able to [do something] because/in order to [achieve a specific outcome].

  • Discovery approach: What questions would you ask to explore solutions to this problem?

Status

EARLY DRAFT

Contributing Team

Marco Morales

Earlier Discovery

N/A

Linked Initiatives

N/A

Overview

This effort is looking to update the Course Updates feature in Studio that educators use to post updates in their courses. The proposed changes include the ability to schedule or trigger course updates, automatically cross-post them as an email and discussions post, and more. These changes are meant to help our course instructor experience echo that of similar course management platforms which streamline these kinds of course communications.

Overview

This effort is looking to update the Course Updates feature in Studio that educators use to post updates in their courses. The proposed changes include the ability to schedule or trigger course updates, automatically cross-post them as an email and discussions post, and more. These changes are meant to help our course instructor experience echo that of similar course management platforms which streamline these kinds of course communications.

Abstract

We would like to help simplify the an educator’s experience by making it easier to community course updates with students. Today, you can use the Course Updates feature to post an update in Course Home, but you cannot schedule these updates. You must also copy the contents of this post to the Bulk Email tool to broadcast this message, and optionally create a post in the Discussion forums to echo this.

Context & Background

  • The Course Updates feature was recently converted to use new front end technology, but previous to this change Updates had remained relatively unchanged since their initial implementation in Studio circa 2013.

  • Course Updates were intended as a primary in-platform mechanism for educators to reach out to students for instructor paced courses. Updates were never reimagined to work for self paced courses, and are thus less used today than they were from 2012-2015. Incorporating self-paced learning triggers for new updates is one way to reimagine how updates could be used in courses.

  • When the Course Home was updated to be powered by the learning MFE in 2019 (question) we decided to only show the most recent update, a short term compromise as we focused on releasing the MFE to production. How updates are rendered in course home, including whether or not students have actually read previous updates, is an improvement we can address now.

  • Generating in-platform updates is not enough to reach learners, but we never automatically sent out course updates via email and instead expect educators to duplicate these updates via the bulk email tool and discussion forums.

Scope & Approach

  • …

Value & Impact

  • …

Concept Sketches

…

Milestones and / or Epics

 Template Detail

Any relevant background information about the Initiative. What key pieces of information are important for newcomers to understand about the nature of the problem or pain point, the current user experience, etc. Please use the following format:

Milestone 1: [Title]

  • [1-2 sentence abstract. Include key user stories if appropriate]

  • [Impact metric]

  • [Link to Epic where it may exist in GH, jira, etc]

Initiative 1: Default On Advanced Components in Studio Unit Pages

Goal: …

  • …

Screens:

Initiative 2: Course Components Page in Studio (+ Add Advanced workflow)

Named Release

 Template Detail

First Named Release to include this initiative. Alphabetical named releases are generally cut in early April and early October. Based on the removal date, what named release would be the first without this code? Please reach out to the Build Test Release working group (#wg-build-test-release in Slack) if you're not sure. Use the letter, if you're not sure of the name.

This is TBD based on community interest and funding.

Timeline

 Template Detail

Recognizing that many Initiatives evolve incrementally, please include a brief scope of the Initiative timeline. Please include a target Named Release, with contingencies if necessary.

TBD

Proposed By

Marco Morales , and team @ Schema Education

  • No labels