Перейти к содержимому
Попробовать

Operations & Administration (Control)

Interfaces to other learning systems

ДляОператорАдминистрация

Other learning systems launch courses of this platform, third-party content runs here; plus keys for the platform's own programming interface and webhooks that notify other systems.

Зачем#

Customers bring their inventory and keep their existing learning system. The more open the platform, the easier the switch — and the less anyone has to retype a thousand questions.

Как это работает#

Маршрут кликовAdministrationThird-party content

  1. 1Open “Third-party content” in the administration's bar (address /admin/interop).
  2. 2Upload course packages (SCORM 1.2 and 2004 or Common Cartridge including question pools in QTI format). Under “Delivered packages” each is listed with format, number of files, size and remarks (Рис. 1).
    Рис. 1 “Delivered packages”: each with format, number of files, size and remarks.
    “Delivered packages”: each with format, number of files, size and remarks.

    Рис. 1 “Delivered packages”: each with format, number of files, size and remarks.

  3. 3“Connected learning systems”: register the platform as a tool in another learning system (LTI 1.3); the platform's own key addresses are listed with each connection.
  4. 4“Learning record store”: send learning events via xAPI to the university's learning record store; the list shows the last delivery or the last error.
  5. 5“API keys” (address /admin/api-schluessel): “Issue new key”, enter a purpose, tick rights, “Issue” — the key is shown exactly once.
  6. 6“Webhooks” (address /admin/webhooks): “Create new target” with purpose, address and events — the secret for checking the signature is shown exactly once.

Настройки и переключатели#

  • Включается для каждого клиентаПо умолчанию: вкл.Модуль: Schnittstellen

What an API key may do#

Every key sees only the data of its institution. The list “Issued keys” shows the beginning, the rights, the creation date and the last use; “Block” makes a key unusable immediately (afterwards it says “blocked” with a date).

  • Read courses
  • Read and write people
  • Read and write course enrolments
  • Read learning progress
  • Read credentials

Which events a webhook reports#

  • Enrolment created — a person was enrolled in a course, via the interface or in the platform.
  • Course completed.
  • Credential issued — with the public verification code, never with the signed credential itself.
  • Person changed — a name was changed via the interface.

A guard in the code ensures that every event offered is actually triggered somewhere — no promise that a customer builds against and that never arrives.

Who may do what#

  • Third-party content (packages, learning systems, learning record store): administration and operator.
  • API keys and webhooks: a customer's administration for its own institution (HR management or university administration with an organisation) and the operator. A customer must be able to set up their connection themselves and switch it off themselves in an incident.

Советы#

  • What cannot be transferred is not bent but reported: matching questions, cloze texts with tolerances and items with partial points are not adopted by the question import.
  • Adopted question pools can be practised and turned into an exam with one click (see “Imported questions as an exam”).
  • The complete guide for developers is available without signing in under /entwickler — a service provider can build the connection before receiving a key.
  • If a webhook target is not reached, delivery is retried for up to 26 hours at increasing intervals; every delivery is signed.

Связанные функции#

Справочные знания