kmccormick
(Kyle McCormick)
March 4, 2025, 3:58pm
1
Please see:
opened 01:57PM - 14 Jun 23 UTC
depr
content libraries misc
_Please first read the parent DEPR ticket, [[DEPR]: All Legacy Studio Frontends]… (https://github.com/openedx/edx-platform/issues/36275)._
### Proposal Date
2025-02-19
### Target Ticket Acceptance Date
2025-03-14
### Earliest Open edX Named Release Without This Functionality
Provisional migration path available to admins by **mid-April 2025 (Teak).**
All Legacy library frontends, including the _ability to view or edit Legacy Library content_ removed as early as **2025-09-08 (Ulmo)**. Official migration path will be available to course authors, using an MFE frontend page.
Removal of legacy library backend support as early as **2026-02-08 (Verawood)**. Migration path will be enforced if not already executed during Ulmo.
### Rationale
Starting in Sumac, the new Libraries (Beta) feature became available, with its frontend entirely implemented in the [Authoring MFE](https://github.com/openedx/frontend-app-authoring). In Teak, Libraries (Beta) will have achieved parity with Legacy Libraries, and also added many features beyond what Legacy offered. In Ulmo, the new Libraries feature will be improved even further. You can track the progress of the project on the [Libraries Overhaul board](https://github.com/orgs/openedx/projects/66).
In addition to the legacy frontend issues mentioned in the [parent DEPR ticket](https://github.com/openedx/edx-platform/issues/36275), maintaining both Legacy Libraries and Libraries (Beta) adds maintenance burden and complexity for developers, and it causes confusion and duplicated work for Studio users.
### Replacement
"Libraries (Beta)", a.k.a "New Libraries", formerly known as "V2 Content Libraries", soon to be known simply as "Libraries"
### Migration
https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4831379492/Legacy+Content+Libraries+Migration+Plan
### Removal
For Ulmo: All legacy library authoring pages, including:
* the legacy library listing
* the legacy library editor
* the legacy interface for configuring V1 (randomized) library content blocks
* the legacy library settings pages
For Willow(?):
* The parts of CMS which support V1 libraries
* The parts of modulestore which support V1 libraries
* `studio_post_duplicate` https://github.com/openedx/edx-platform/issues/35192
* The various parts of the platform that are special-cased the deal with `library_root`
### Deprecation
We will ensure that the release notes contains details on at each stage of the migration and deprecation. We may show deprecation warnings in the UX. Follow the Migration Plan (linked above) for up-to-date details.
### Additional Info
N/A
Note: The Legacy Libraries deprecation is actually a sub-ticket of [DEPR]: All Legacy Studio Frontends , which was already announced separately . I am just re-communicating the Legacy Libraries deprecation because it also includes backend changes and a content migration.
1 Like