...
A component can exist as both a standalone component and as part of a unit
View-only and Edit modes/Managed vs externally managed vs unmanaged
Requirements TBD
Managed content item - any level of content (section, subsection, unit, component) that exists in a library.
Externally managed content item - any level of content that exists in a library that is ‘connected’ to an external CMS.
Unmanaged content item - any course content not from a library
Functional requirements: Course Side
Units can be reused in Courses
Units can be
...
reused via the Course Outline page in a
...
course
...
...
Library search can be accessed from within the course
...
so authors can find which units they want
Units can be updated in a library and synced at the course level
Users receive notifications about content updates made in a library
Users can review and accept/deny content updates
Users can edit/modify re-used units, subsections and sections with options to keep or break the library sync [This requirement needs to be fleshed out in more detail based on user needs and what’s feasible]
...
Accept the updates and override any local edits that may have been made to the unit
Accept the updates while keeping any local edits that may have been made to the unit
Deny the updates
A refresh of the library will update the course, but will not affect unmanaged content (unless its parent is removed).
Units can be edited locally
Happy path and edge cases TBD
Course authors can add content, in the course, to library-managed content items. For example, a course author can add an LTI component to a unit that is contained in a subsection that is managed by a library.
UX/UI Needs
Library-side
Libraries must support a creation workflow for creating new units, subsections and sections
Libraries must support an editing workflow/editor environment for units, subsections and sections
In-context sidebars must be expanded such that each unit, subsection and section has a sidebar.
Needs discovery: Are previews necessary? Even possible?
Library Home must contain one tab each for units, subsections and sections, where users see a filtered view by content type
All of the searching, sorts and filters that apply to components must be extended to units, subsections and sections.
...