/
Collection Player Design

Collection Player Design

 

Problem statement

 

For the adaptors to experience the collections which are part of knowLG building block there is a need to build a player which will render them, So there is a need to build a collection player which supports all types of collections.

 

Since the knowLG portal is built using the angular framework we will design the player as a component and each is responsible for taking the input data and rendering and also providing the output event for the same.

Design

 

Below provides the interfaces for each component that needs to be implemented

 

<sb-collection-player [collection]=”<collectionObject>”>

 

<sb-collection-header

[name]=”<collection-name>”

[metadata]=”<['string': ‘<any>’]>” />

 

<sb-collection-renderer

[hierarchy]=”collection-hierarchy”

(selectedContent)=”renderContent($event)” />

 

<sb-toc-item ….> - This should be used from the common consumption components which renders the hierarchy.

 

<sb-content-info [content]=”content”>

<sb-collection-info [collection]=”<collection-metadata>”>

 

Related content

Sunbird Knowlg
Sunbird Knowlg
Read with this
[Implementation design] To show the list of contents for consumptions experiences
[Implementation design] To show the list of contents for consumptions experiences
More like this
Knowlg Mobile app and website players features interoperability
Knowlg Mobile app and website players features interoperability
Read with this
Content Player 2.0
Content Player 2.0
More like this
Knowlg mirco-services: Open questions
Knowlg mirco-services: Open questions
Read with this
Implementation - Knowlg player app integrate with player V1
Implementation - Knowlg player app integrate with player V1
More like this