Part of: https://github.com/openedx/edx-platform/issues/32457
...
Previous Releases: Cypress through Palm
Studio has had a feature called Libraries; in essence, they are bare-bones problem banks. These libraries have had a very minimal authoring environment. They support supported only Problem, Video and Text components. They support supported OLX import/export. Library content is was 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 was 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 would 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 This features can could be globally disabled using the Django setting FEATURES['ENABLE_CONTENT_LIBRARIES'].
...
The V1 Library Content Component is was renamed to Library Content, and it is was available on all courses without having to configure the Advanced Module List. A Show Reset Button option is was added to the component. Otherwise, the feature is was unchanged.
Current Release: Sumac
...
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.
Upcoming Release: Teak
The authoring environment for V2 Libraries, still known as Libraries (Beta), will have several new features, including but not limited to: support for certain Advanced components, support for Units, Subsections, and Sections; ability to import content from courses; various general UX improvements.
...
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.
...