...
Authors can create subsets of components for the sake of grouping like components together as a method of content organization and management.
For example, I want to create a subset of evergreen videos about how to do peer-reviews.
Authors can create as many Collections in a Library as they wish.
Authors can add as many components to a collection as they wish.
Components can live in multiple collections.
Collections can contain mixed media types (for example, a collection may contain video components, text blocks and problems all within the same collection).
Collections may be sorted by:
Title
Last modified datetime of their contents.
Search/sort/filter within a collection
Basic keyword search within a collection
Basic sort and filter
Sort alphabetical
Filter by tag
Jenna Makowski notes: “Really need to weigh the immediate user need against feasibility and eng effort, especially for MVP, esp since Collections will be assumed fairly small at the outset. Alternative barebones MVP approach is to auto-populate lists of components in collections alphabetically.”
[Key here is whether changes/updates to a collection in a Library need to auto-sync to item pools already being used in a course]
[FUTURE STATE] When Libraries support units, subsections and section, collections may also contain any combination of components, units, sections and subsections. Note that a single unit or a single section is not considered a Collection. Rather, a Collection is comprised of multiple sections, multiple units, etc.
...
A Collection can have up to 100,000 ( ? ) Items.
There can be at most 10,000 ( ? ) Collections in a Library
A single Item may belong to at most 100 Collections
This is largely to make sure that we can quickly do updates to Collections indexing that involve their contents, e.g. “sort Collections by their last modified Item”
Items have no manually selected ordering within a Collection.
Collections can overlap. An Item can belong to multiple Collections.
Collections do not nest. Collections are not Items. A Collection can be a superset of another Collection, but Collection cannot contain another Collection as one of its elements.
Collections are not publishable entities themselves.
They contain things that can be published (like Components), but there is no “draft” vs. “published” version of a Collection. Changes to Collection metadata like its name, description, or contents are saved immediately.
...