MaestroMaestro Overview — contents
The Build
Integration — Moodle & LTI
How students reach Maestro: Moodle via LTI 1.3 with LTI Advantage. This topic covers sign-in and launch, adding courses to Moodle, roster sync, grade pass-back, and the boundary that keeps learning data inside Maestro.
Moodle connects to Maestro through LTI 1.3 with LTI Advantage. Single sign-on brings learners straight into Journey, where they land on Your day. Courses are added to Moodle whole, never item by item, and only once released. Each approved milestone becomes its own Moodle grade column, worth its weight. The roster is kept in sync automatically. Only milestone grades leave Maestro; check outcomes and the learner model stay inside.
LTI 1.3 at a glance
| Area | What it does |
|---|---|
| Sign-in & launch (LTI 1.3 Core) | Single sign-on from Moodle into Maestro, with no separate Maestro login. Learners land on Your day with the course they came from highlighted. |
| Adding courses (Deep Linking 2.0) | A whole released course is placed into a Moodle course as one LTI activity. |
| Grade pass-back (AGS) | One line item per approved milestone; final milestone grades flow to the Moodle gradebook. |
| Roster sync (NRPS) | Maestro reads the Moodle roster and keeps its own enrolments in step: joiners, leavers and suspensions. |
Sign-in & identity
A launch from Moodle signs the person in automatically. Identity is keyed on the institution's person identifier, never on email address or name, so two people are never merged because their details look alike.
- Learners. A first launch creates a Maestro identity as a student, unseen by the learner: no account to create, no password. Learners land on Your day, with the course they came from highlighted.
- Staff. Moodle instructor-type roles (Instructor, Administrator, Content Developer) are recognised as staff. A first-time instructor is created as an SME with no course access until assigned to a course. Moodle can never grant a higher Maestro role: IT links staff institutional identifiers to their Maestro staff accounts in advance, and a returning identity keeps its Maestro role. Staff who can preview Journey see it in preview mode.
The full role mapping is in Standard LMS & Roles.
Adding a course to Moodle
Deep linking is whole-course only. The picker lists released courses, each with its number of graded milestones; there is no way to link a single lesson or a single milestone. Opening the picker needs both a Moodle instructor-type role and the Maestro capability to add courses to Moodle, which only IT Admin holds, so in practice IT adds courses to Moodle from the "Ready for Moodle" queue. The course's status turns Live in Moodle on its first link or launch. See The Published Course Package for how a course is released.
Grade pass-back (AGS)
After a whole-course launch, Maestro makes sure Moodle holds one line item per approved milestone:
- labelled with the milestone's title;
- worth the milestone's weight in points: a weight of 0.5 gives 50 points, and a milestone with no weight gives 100;
- renamed or re-weighted when the milestone changes.
There is no course-level or activity aggregate column: Moodle's own course total follows the milestone weights. A grade is pushed only when a milestone attempt is finalised, through an outbox that removes duplicates and retries on failure.
Roster sync (NRPS)
Maestro reconciles each linked course's roster with Moodle every five minutes, and a "Sync roster" action runs it on demand. Only members with a learner role count. A learner marked inactive in Moodle has their enrolment suspended (shown as Deferred); a learner who leaves the roster loses access and their enrolment is marked Withdrawn. Completed enrolments are left untouched. Roster sync runs only for released courses.
Enrolment itself runs through the institution's existing systems into Moodle; there is no direct enrolment path into Maestro.
The export & privacy boundary
- Content authoring never flows through Moodle. Studio releases courses to Journey directly; Moodle only links to them.
- Maestro is the source of truth for grades. Moodle receives milestone grades via AGS; it does not compute them from Maestro data.
Only milestone grades leave Maestro. Lesson check outcomes, learner answers, mix-ups and the learner model stay inside Maestro. Build to this boundary from the start; it is a design constraint, not a later privacy retrofit.
Instructor detection matches the #Instructor, #Administrator and #ContentDeveloper role markers; every other role is a learner. Identity is keyed on lis_person_sourcedid. The Journey token is passed in the URL fragment, never the query string. A deep-link content item carries the course_code and no line item; milestone line items are created after launch, with scoreMaximum derived from grade_weight.