What is a Legacy Package?

The October 9th update of Doki's packaging system changed the way we bundle Modules in Packages. Read on to understand the difference. Fair warning: this is a bit technical, so if you just want us to help you do something or explain it, reach out to support.


Packages created prior to the October update are considered "legacy" packages. The major difference between a new package and a legacy package is that legacy packages always include all the modules from the course in them, in the order defined in the "Content" listing. This was problematic for dripped courses which expected the modules to be in a specific order. For example, if you change the order of modules after defining the drip schedule with a legacy package, you could mess up the order they were presented to the user since they then wouldn't match the drip schedule. The new system prevents this by saving a snapshot of the module order and included modules when you create the package.

It may be helpful to understand where each type of "Package" gets its modules with the two systems:

Legacy

  • Resource Library - Includes all modules in the order defined in the content outliner.
  • Self-Guided - Includes all modules in the order defined in the content outliner.
  • Auto-drip - Includes modules used in the drip schedule in the order defined by the drip schedule.
  • Class - Includes modules used in the drip schedule in the order defined by the drip schedule.

New

  • Resource Library - Includes all modules in the order defined in the content outliner.
  • Self-Guided - Includes selected modules in the order defined at package creation time.
  • Auto-drip - Includes selected modules in the order defined by the drip schedule at package creation time.
  • Class - Includes selected modules in the order defined by the drip schedule at package creation time.

So you can see that you need to have all your modules defined before packaging with all but the resource library.

Still need help? Contact Us Contact Us