Skip to content

Meeting Notes - 23-Feb-21 #49

@cliftonc

Description

@cliftonc

SEM Meeting

Notes

SIS Api

  • SIS API
    • PR to accept change in student and group reference approved.
    • Agree: Remove Display name, use first and last name
  • School Level Changes
    • Subject code is optional
    • Subject code link to gov website
    • Level - todo: we should define the list of values
    • Level - should we separate year?
    • Create 'course' entity; level + year
    • School Level - 1-N - government levels
    • Kees - make proposal
  • Enrolment?
    • Do we need the level?
    • Can we just add 'Course' to the subject Choices
      • TODO: Define course
    • Remove enrolment
  • Student object
    • SubjectChoices - remove start/end
    • Add school year to student object

Versioning

  • Entities should have version numbers

Startup / Bootstrap

  • Setup flow can trigger data load - driven by creator
  • For now - we can perhaps use 'getAll' - on the entity APIs or event APIs, though want to avoid clients polling for all data every night!

Setup Flow

  • OpenID Connect for everything
  • (Can we use .well-known type urls for discovery?)
  • Client credential flow for schools; via Openidconnect
  • Wouter to define flows for setup for us to review
  • LMS and SIS must have single endpoint for all schools
  • TenantId - express as a claim - tid
  • Partners share info on urls and client id/secret - this is per partner, not per school; and initial setup can be relatively manual (e.g. via dev portals) in short term

** Break for coffee **

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions