Forum Discussion
AI course creation alters source text too much
We have a similar problem. We have our IDs create a finalized storyboard, then use developers to create the course in Rise. This works well in not changing the finalized text, but one MAJOR downside is the Magic Lesson Importer only does one lesson at a time. We have automated tools to "split" a storyboard into smaller files to use the Magic Lesson Importer, but it compounds our work time if the lesson is short. Can someone please let me know if it's on the roadmap to import an entire storyboard that creates multiple lessons in Rise that the developers can then go in and massage?
Hi ChrisWilliams-f,
Thanks for sharing more about how your team builds courses.
I can see why preserving finalized storyboard content while speeding up course assembly is important to your workflow. It also sounds like having to split approved storyboards into multiple files adds unnecessary work for your developers.
I'd be interested to hear a little more about your storyboards. Approximately how many lessons does a typical storyboard contain before you split it into separate files? Also, if Magic Lesson Importer could process an entire storyboard, how would you expect it to determine where one lesson ends and the next begins?
Understanding more about your process and how your storyboards are organized helps us better understand how a capability like this could support teams like yours.
EricSantos​ A typical storyboard could contain anywhere between 2-55 lessons, depending on the size of the course. We have successfully built agents to parse a storyboard and create separate files when it sees H1 style. If the Magic Importer could leverage that same logic to know when to create a new Lesson, that would be helpful.
Thanks, ChrisWilliams-f! That's really helpful context.
Knowing that your storyboards can range from just a couple of lessons to more than 50, and that your team is already using Heading 1 styles to programmatically split them, paints a much clearer picture of your workflow. I also appreciate you sharing how you'd expect Magic Lesson Import to determine lesson boundaries.
Thanks for sharing those details. They help our product team better understand what an ideal import experience would look like for your team.
