Technology Partners

What should application developers (who will extend Navigator and make contributions to core solution — more of engineering team extension) should be prepared for?

Partners should have a good understanding of microservices architecture
Partners should have a good understanding of RESTful API design
Partners should have a good understanding of Java-based implementations
Partners should have a good understanding of front-end implementations based on EmberJS

What should Technology Partners (who will use Navigator in closed environment while extending workflows) should be prepared for?

Partners need to have an understanding of SSO models and should be using an identity provisioning system that can be configured at Navigator for SSO flows.
Partners should be able to share their roster data in OneRoster standards format, or via ClassLink Roster API.
Partners should be able to understand competency-based learning models, bring in the frameworks of interest, and be able to map the frameworks to other similar frameworks.
Partners should be able to identify, create, and curate content relevant to the competency model of interest; and be able to setup content working together with other NLC Partners.
Partners should be able to use shared API that requires an understanding of RESTful services and sync/async mechanisms to extend any workflows in their products to bring Navigator into play.
Partners should be able to push data (either as xAPI or Navigator specific data-in format) via shared API.
Partners should be able to sync data (either LTI outcomes or xAPI or Navigator specific data-out format) to their system via a shared API model.
Partners should be able to design deploy architecture based on guidance from other NLC Partners and should have expertise on AWS services, hosting & infra-manage.

What should Technology Partners (who will use our API layer to extend workflows) be prepared for?

Partners need to have an understanding of SSO models and should be using an identity provisioning system that can be configured at Navigator for SSO flows.
Partners should be able to share their roster data in OneRoster standards format, or via ClassLink Roster API.
Partners should be able to understand competency-based learning models, bring in the frameworks of interest, and be able to map the frameworks to other similar frameworks.
Partners should be able to identify, create, and curate content relevant to the competency model of interest; and be able to setup content working together with NLC.
Partners should be able to use shared API that requires an understanding of RESTful services and sync/async mechanisms to extend any workflows in their products to bring Navigator into play.
Partners should be able to push data (either as xAPI or Navigator specific data-in format) via shared API.
Partners should be able to sync data (either LTI outcomes or xAPI or Navigator specific data-out format) to their system via a shared API model.

What does it mean to have tenancy on Navigator? What is sub-tenancy?

Tenancy setup at Navigator provides for isolation of content, identity, and data. Partners can choose to bring their content for their private use; and restrict access to data for users within the partner group. Tenancy setup ensures this isolation. In addition, tenancy will support customization of Navigator to the extent of usage of specific competency model, framework, etc; and access to additional tenant-level aggregate reports.
Sub-tenancy can be imagined as a controlled group within the tenant set up like a department requiring its own data isolation within the organization but access allowed to parent tenant users but not to peer departments. Sub-tenant, from a structure and setup perspective, is no different from a tenant.

How can Implementers be onboarded onto NLC?

Support Competency Framework development- includes Competency definition, Crosswalks, GUT, content development based on competencies
Rostering of their student/teacher users into Navigator classes
Course building to enable implementation
Product interface customisations, if any
Gather data on implementation

What happens when content resides in 2 different systems and there are constant metadata updates in Partner’s systems. Does metadata updates in partner’s systems need to be periodically updated in the Navigator?

Yes, this would be a necessity.

Is Navigator an authoring tool?

Learning Navigator is not an authoring tool, it only indexes content
Also, Navigator doesn’t store content; actual content resides in repositories like Google Drive and other parts of the cloud

Who collaborates with NLC?

Any entity interested in adopting and implementing Navigated Learning. This includes use of the Navigator tools and platform, adopting a competency-based approach to learning, and an interest in measuring learning Impact.

What should Implementation Partners (who will use services) be technically prepared for?

Partners need to have an understanding of SSO models and should be using an identity provisioning system that can be configured at Navigator for SSO flows.
Partners should be able to share their roster data in OneRoster standards format, or via ClassLink Roster API.
Partners should be able to understand competency-based learning models, bring in the frameworks of interest, and be able to map the frameworks to other similar frameworks.
Partners should be able to identify, create, and curate content relevant to the competency model of interest; and be able to setup content working together with NLC.

Do we need to put up relevant assessment questions for every file uploaded in a course so that it can help decide which content in the course the learner needs to go through?

The approach in Navigator course building is to ensure there is an assessment (with a set of min 5 questions if possible) for each competency/lesson to be studied. The individual questions can cover the sub-lessons/ micro-competencies covered in the particular competency/lesson.