$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

These are the firm requirements needed before we can relaunch Libraries in a Community Release:

  1. The Library authoring environment includes the latest text editor, problem editor and video editor, and static asset support.

  2. The Library authoring environment supports the ability to create multiple subsets of components for reuse.

  3. The Library authoring environment supports tags and taxonomies as the primary mode of managing components.

  4. The Library authoring environment has keyword search and the ability to filter/facet by tags.

  5. The Library block supports both static reuse and randomized reuse.

    1. Product definition for overriding, course local copies

  6. The Library block and the Library authoring environment are designed in a user-friendly and intuitive way.

  7. Full support for Library ---> Library import/export

  8. Libraries are built on/migrated to Learning Core.

  9. Architecture plan to support better library/course behavior, interactions

  10. A solid migration plan for getting V1 libraries into the new library environment.

  11. The right branding.

  12. Full support for Course ---> Library import/export [This could be post-MVP]

Major epics/milestones to get us to the Libraries Relaunch


Estimations for remaining work:

The Library authoring environment includes the latest text editor, problem editor and video editor.

This seemed like it was a toggle issue but also has a contingency on the V1 - V2 migration.

The Library authoring environment supports the ability to create multiple subsets of components for reuse.

Need UI estimates first, then implementation estimates.

Is there technical discovery that needs to be done?

The Library authoring environment supports tags and taxonomies as the primary mode of managing components.

Already underway, estimates https://docs.google.com/spreadsheets/d/1HFS3h8HI9P-AJUVHX-ZtY0u_yLAeSdmObns8ORw9kvs/edit#gid=0

The Library authoring environment has keyword search and the ability to filter/facet by tags.

Already underway, estimates https://docs.google.com/spreadsheets/d/1HFS3h8HI9P-AJUVHX-ZtY0u_yLAeSdmObns8ORw9kvs/edit#gid=0

The Library block supports both static reuse and randomized reuse.

Is this the extend of the remaining technical work? https://github.com/openedx/edx-platform/issues/33640

The Library block and the Library authoring environment are designed in a user-friendly and intuitive way.

Need UI estimates for any improvements.

Full support for Library ---> Library import/export

Needs more product definition. Is partial import/export required? Preserve version history?

Libraries are built on/migrated to Learning Core.

?

Architecture plan to support better library/course behavior, interactions

~3-4 of dev time

Migration plan

What the process looks like. What the intermediate state is. Expected behavior.
Needs UI.

https://docs.google.com/spreadsheets/d/1dNUwHJvRvalbe3aUbdDCQhIfM_4L1BB1a1TsROiE39Y/edit#gid=109012158

  • No labels