...
V1 Libraries will be removed as soon as TeakUlmo. This living document explains how we currently plan to migrate convert existing V1 Library content and references over to V2. We will update it with higher-fidelity mocks/screenshots over time and eventually transfer this information into the official release notes.
Contents:
| Table of Contents | ||
|---|---|---|
|
...
Content Libraries in upcoming releases
General migration notes
Each V1 Library will be convertible to a collectionwithin a V2 Library. The conversion process will be very straightforward. In general, V1 Library Content references in courses will continue to work seamlessly, whether or not its source material has been converted.
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.
...
Teak->Ulmo Migration Path
...
New in Teak (preliminary UI / exact interface TBD): A system with two legacy libraries, one which has been converted to MyCollection within MyV2Library.The Legacy Libraries tab will show a list of V1 Libraries that are in the system. V1 Libraries that were already migrated converted to the V2 environment will continue to be indicated as they were in Teak. V1 Libraries that are not yet migrated converted will feature a prominent “Migrate Now” call-to-action, allowing library authors to select a destination V2 Library or V2 Library Collection.
...
In order to eventually remove MongoDB as a dependency of Open edX, there will be a future release where the Legacy Libraries (or Legacy Collections)tab is removed and V1 Libraries Content becomes completely unavailable. Operators who wish to preserve their V1 Library contents will need to perform the migration described above before upgrading to such a future release.
We expect that any remaining un-migrated Un-converted V1 Library Content Components will continue working in isolation, but will be unable to receive content updateswill work, with some caveats, depending on technical constraints that may arise during the eventual retirement of MongoDB from the platform stack. The DEPR process will be used to communicate any future change in support level to un-converted V1 Library content.