Page Comparison

...

• Sumac

  • Learning Core is getting rolled out to prod for the first time

  • LC Components, Collections, Assets for Libraries v2

• Teak

  • LC Units, Sections in Subsections for Libraries v2

  • Migration path for Libraries v1->v2

• Ulmo

  • Remove Libraries v1

  • Standalone assets (files and uploads) for Libraries v2

  • Standalone assets (files and uploads) for Courses

    • LearningPackage for each course

    • LearingCoreContentstore

    • Slow, major migration (~1TB for 2U?)

    • Rollout questions… all-at-once, or mixed mode?

    • Benefits of asset conversion would be:

      • Cheaper storage

      • Faster/easier querying (particularly if we hook it up to a search backend).

      • May cause higher latency if we maintain the same URLs

• Verawood

  • LC Components for Libraries

    • Components with children?

      • Some in edx-platform

        • a/b test, randomize, etc

        • Each of these is a Selector

          • Selected content is a Variant (some list of PubEnts)

          • selector.get_or_create_variant_for_user(args) -> Variant

          • Is this a generalization of learning_sequences?

          • Kinda but not really. LSeqs is built as a pipeline of processors which can hide or remove content. Intersection of the resulting sets is the users' outline

      • Some outside? Do we support? Or deprecate customization of get_children ?

        • Do not break callers of get_children

        • Do deprecate the ability to customize it, though

        • End result is that get_children is the responsibility of the runtime / edx-platform:

        • Code Block
          class XBlock: def get_children(...): yield from self.runtime.get_children(self.usage_key)

    • Ideas

      • Just migrate leaf components

        • get_item(leaf_block) → LC
          get_item(parent_block) → splitmongo

      • Implement Unit and below at LC level

      • Thing to watch out for: how to juggle the two different runtimes used for field data persistence.

• Misc

  • Eventually

    • Leaf blocks can define views with arbitrary python

    • Parent blocks (containers?) are declarative, an external system looks at the rules they declare to determine the course tree

...