## approach for collection versions and expansions:
- Components:
  - Collection version dropdown in the breadcrumb
    - User goal #1: Find a collection version
  - Focus of the version/expansions dropdown
    - User Goal #2: management
    - User Goal #3: looking for an expansion
- Two types of users:
  - Most common user: someone who doesn't care about expansions
    - as a consumer: they typically only use the default expansion for a collection version
    - as a manager: typically always auto-expand collection versions and need to rebuild expansions to bring the underlying source versions up to the latest
  - Less common user: power users people who care about expansions, are thinking about FHIR, etc.
    - as a consumer: they pay close attention to expansion parameters and resolved source versions in an expansion
    - as a manager: author expansions in addition to reference

## feedabck received on TBv2 collection versions and expansions page:
- too much whitespace
- primary action/flow on the page not clear
- how to work with expansions not intuitive

-------

## Review of all screenshots in the ocl-zeplin repo:
> Note: Covers OCL 3.0 folder and OCL Design System folder. If a screenshot is not mentioned, then it is still useful and we'll bring it into the design system.
> All content in Design system, OCL Term Browser, and TermBrowser are stale. Exclude everything from those folders.

assiocations -- this is current but not hierarchical
card view - partially accurate, but we've evolved past it
chip and tooltip (for repo) - this is mostly accurate
    - and we do not yet have a tooltip for concept, mapping, reference, expansion

Color Guidance - this is 100% implemented (and referenced by name, e.g. "primary.80")

Concept - card designs are there, tooltips and chips are not

Empty State -- the middle "no updates to show" is accurate, but not the left drawer

Signed out & Feed -- display of cards in What's new has evolved some, but otherwise good

Dashboard view not implemented: 
- Signed In - not implemented
- Signed Out - not implemented

Edit Concept/mapping - not applicable -- 

Elevations - the first one is used, that's it

Grouped by Source - we did not implement

Grouped by Type - Dense: still accurate, but we didn't do the expand/collapse yet

Hierarchy Grouped by Code Dense -- not implemented yet, but still a good design direction; not intuitive with the expand/collapse button next to name instead of code

My Repositories Copy Code System - as implemented!

My Repositories Create Version -- not implemented like this; we followed v2

Org Overview Browser members

These are not implemented and layout/component decisions needed, but useful designs:
- Reference details - not implemented
- Reference expansion mappings - not implemented
- Reference expansion - not implemented

Repository Card View: Dialog - We're not going this direction -- the workflow is good, designs are useful, but we are definitely not implementing this for MVP

Repository Collection References -- not implemented; current reference listing is v2 style; need some functional and design decisions; consider this as an input

Repository Source Mappings -- not implemented and not clear if this hierarchical display of mappings is the direction that we will go

-- we have not implemented this 2-column key-value pair display, but probably should (e.g. view repo attributes modal)
- Repo Source Overview 
- Repo valueset

Repository ValueSet: Composition, Conceptes - not implemetned

Search Concepts Bulk - partially implemented
- Action button designs - we haven't used these anywhere
- Card View -- this design is generally used across TBv3, but we modified the concept card view as part of the OCL Mapper card view work (e.g. to support multiple properties, etc.)

Search Concepts -- same as above with Concept Card view

Search Concepts Detail view Edit Concept -- do not implement

Card View in Search Results - only impelmented for concepts (which doesn't follow this design system)

Design System / Component Tables Search Concept AND Component Tables -- partial -- the first one is done, the others not; this is useful but not there yet

-------

Implementation gap:
- Design system shows a Key-value-pair component view -- need to implement this in TBv3

Major Design System GAPs:
- browsing hierarchical source -- we're happy to go with v2 model for now
- collections & their references -- this is the biggest gap
- concept selector component -- in the meantime, use the v2 quick add mapping approach (which combines multiple components to select a concept)
- editing concepts, mappings, references -- expect other gaps, need to assess
- (optional) mappings grouped by source, type, etc.