Designs
Spec
The sidebar in the migration flow should help users understand:
- Description of new content libraries
- what to expect after migration
- how to migrate
- additional links to documentation
The sidebar has the following sections with associated text:
What’s different in the new Content Libraries experience?
In the new Content Libraries experience, you can author sections, subsections, units, and many types of components. Library content can be reused across many courses, and kept up-to-date. Content libraries now support increased collaboration across authoring teams.
What happens when I migrate my Legacy Libraries?
All legacy library content is supported in the new experience. Content from legacy libraries will be migrated to its own collection in the new Content Libraries experience. This collection will have the same name as your original library. Courses that use legacy library content will continue to function as usual, linked to the migrated version within the new libraries experience.
How do I migrate my Legacy Libraries?
There are three steps to migrating legacy libraries:
1 - Select Legacy Libraries
You can select up to 50 legacy libraries for migration in this step. By default, only libraries that have not yet been migrated are shown. To see all libraries, remove the filter.
You can select up to 50 legacy libraries for migration, but only one destination v2 Content Library per migration.
2 - Select Destination
You can migrate legacy libraries to an existing Content Library in the new experience, or you can create a new destination. You can only select one v2 Content Library per migration. All your content will be migrated, and kept organized in collections.
3 - Confirm
In this step, review your migration. Once you confirm, migration will begin. It may take some time to complete.
Library Migration Documentation
{To be added once documentation is created}
Designs
Spec
The sidebar in the migration flow should help users understand:
The sidebar has the following sections with associated text:
What’s different in the new Content Libraries experience?
In the new Content Libraries experience, you can author sections, subsections, units, and many types of components. Library content can be reused across many courses, and kept up-to-date. Content libraries now support increased collaboration across authoring teams.
What happens when I migrate my Legacy Libraries?
All legacy library content is supported in the new experience. Content from legacy libraries will be migrated to its own collection in the new Content Libraries experience. This collection will have the same name as your original library. Courses that use legacy library content will continue to function as usual, linked to the migrated version within the new libraries experience.
How do I migrate my Legacy Libraries?
There are three steps to migrating legacy libraries:
1 - Select Legacy Libraries
You can select up to 50 legacy libraries for migration in this step. By default, only libraries that have not yet been migrated are shown. To see all libraries, remove the filter.
You can select up to 50 legacy libraries for migration, but only one destination v2 Content Library per migration.
2 - Select Destination
You can migrate legacy libraries to an existing Content Library in the new experience, or you can create a new destination. You can only select one v2 Content Library per migration. All your content will be migrated, and kept organized in collections.
3 - Confirm
In this step, review your migration. Once you confirm, migration will begin. It may take some time to complete.
Library Migration Documentation
{To be added once documentation is created}