Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

Version 1 Next »

Part of: https://github.com/openedx/edx-platform/issues/32457

There are two generations of Content Libraries in the platform. The Open edX user interface has referred to them by different names across releases, so to disambiguate, we use the code-names “V1” and “V2”.

Previous Releases: Cypress through Palm

Studio has a feature called Libraries; in essence, they are bare-bones problem banks. These libraries have a very minimal authoring environment. They support only Problem, Video and Text components. They support OLX import/export. Library content is stored in MongoDB. To disambiguate across releases, we will call this feature V1 Libraries.

The only way to use V1 Library content in a course is to add “library_content" to the course’s Advanced Module List, and then add Randomized Content Module components to the course’s units. Each learner will see a (configurable) number of components, selected from the entire library, and optionally filtered to a particular problem type. To disambiguate across release, we will call this component V1 Library Content Component.

These features can be globally disabled using the Django setting FEATURES['ENABLE_CONTENT_LIBRARIES'].

Previous Releases: Olive through Redwood

The V1 Library Content Component is renamed to Library Content, and it is available on all courses without having to configure the Advanced Module List. A Show Reset Button option is added to the component. Otherwise, the feature is unchanged.

Current Release: Sumac

A new Libraries (Beta) feature is introduced. It features a much richer authoring environment, allowing authors to organize, tag, sort, and filter their library, and empowering authors to manage a much higher volume of content than would have been suitable in the V1 Libraries environment. It initially supports Problem, Video, and Text components. Content is stored in MySQL and indexed in Meilisearch. To disambiguate across releases, we’ll call these V2 Libraries.

Subsets of V2 Libraries can be randomized into course content via the new Problem Bank component. Subsets of V2 Libraries can be statically shown in courses via a new Library Content component. To disambiguate, we’ll call this the V2 Problem Bank and V2 Library Content Component, respectively.

V1 Libraries are still available for authoring, but they have been renamed Legacy Libraries.

V1 Library Content Components can still be edited and created, but they have been renamed to Legacy Library Content.

Upcoming Release: Teak

Following Release: Ulmo

  • No labels