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”.
...
| Table of Contents | ||
|---|---|---|
|
Content Libraries in
...
past releases
| Info |
|---|
In all Open edX releases since Cypress, Content Libraries (all versions) can be globally |
...
disabled by setting |
Cypress through Redwood
Studio had a feature called Libraries; in essence Content Libraries. In practical terms, they are were bare-bones problem banks. These libraries had a very minimal authoring environment. They supported only Problem, Video and Text components. They supported OLX import/export. Library content was stored in MongoDB.These are V1 Libraries.
...
Starting in Olive, the V1 Library Content Component was renamed to Library Content, and it became available on all courses without having to configure the Advanced Module List.
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. OLX import/export is not yet supported. Content is stored in MySQL and indexed in Meilisearch. These are 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. These are the V2 Problem Bank Component 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.
...
To new Waffle flags are introduced: contentstore.new_studio_mfe.disable_new_libraries and contentstore.new_studio_mfe.disable_legacy_libraries, which can be toggled on in order todisable the V2 and V1 experiences, respectively. These flags exist in addition to the FEATURES['ENABLE_CONTENT_LIBRARIES'] Django setting which, when set to False, disables both the V1 and V2 library experiences entirely
...
V1 Libraries and V1 Library Content Components are still available to be used, although there may be warning encouraging authors to use V2 Libraries for all new content.
Provisional Migration Path:From Django Admin, site-global staff will have the option to select one or more V1 Libraries and perform the Migrate Legacy Library to new Library Collection admin action. The staff member will be able to specify any existing V2 Library or V2 Library Collection as the target of the migration.
...
The V1 Libraries authoring environment will no longer be available. In courses, existing V1 Library Content Components will continue working, but they will be unable to receive updates from V1 Libraries.
Migration Plan: The Legacy Libraries tab will show a list of V1 Libraries that are in the system. Libraries that were already migrated to the V2 environment will continue to be indicated as they were in Teak. Libraries that are not yet migrated will feature a prominent “Migrate Now” call-to-action, allowing library authors to select a destination V2 Library or V2 Library Collection.
...