AFANDI Docs / Lesson vs SCORM einsetzen
← Back to overview Getting Started

Lesson vs SCORM einsetzen

Entscheidungslogik between nativen Moodle-Lektionen and SCORM-Paketen.

Moodle AFANDI standard Handover-ready documentation reviewed on a regular cycle

Quick overview

This page helps, for Lesson vs SCORM einsetzen the passenden standard between Lesson, SCORM traceable about choose.

Instead of relying on intuition, it documents the criteria that matter and explains when exceptions are appropriate.

A clear standard rule with examples keeps the selection consistent, even for new trainers.

Practical focusTopic-specificVerifiable

When this page helps

Typical situations in which this page adds value as a working document, and where another document is more appropriate.

Typical use cases

  • when the selection between Lesson vs. SCORM anhand klarer criteria instead of habit take place should
  • when teams sich for which attribute verbindlich gemappt be not aligned are and a standard case definiert be must
  • when course examples or pilot notes (sso-mapping-documentation) already exist and should be evaluated in a structured way
  • when Exceptions from standard documented be must, without the comparison logic about lose

Less suitable when

  • when Lesson vs SCORM einsetzen only about a one-off individual case without need for standardization applies
  • when a detailed project ticket or a technical step-by-step guide is the better fit

Recommended process

A pragmatic sequence that works in practice, from scope to review.

  1. decision context for Lesson vs SCORM einsetzen describe (learning objective, support effort, assessment, number of participants).
  2. Vergleichskriterien define and prioritize; central are which attribute verbindlich gemappt be and roles- and coursezuordnung aus the sync.
  3. Lesson vs. SCORM an einem test case vergleichen and results consistently protokollieren.
  4. Standardregel + exception cases formulieren and about sso-mapping-documentation supported by evidence make.
  5. After ersten real courses check whether the rule contributes or wegen attribute change sich without abgestimmten mapping-update adjusted be must.

Decision rules

Note: The general documentation rules remain central. On this Page dokumentierst du only decisions, the Lesson vs SCORM einsetzen clearly steuern. Central guideline.

Lesson vs SCORM einsetzen is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.

scope & Wirkung

For Lesson vs SCORM einsetzen first define the scope clearly: Identity Provider, Mapping-rules and roles-Sync.

approvalregel

decisions about which attribute verbindlich gemappt be and roles- and coursezuordnung aus the sync not implizit lassen, sondern roles and approvals explicitly benennen.

Exceptions cleanly halten

Allow exceptions only if they do not dilute the standard; especially relevant here are login-flows incl. logout/session.

Verifiablekeit

Verifiable is the rule only, when sso-mapping-documentation and test cases for login/logout cleanly verlinkt are.

What should be documented

Here only the spezifischen Inhalte about Lesson vs SCORM einsetzen maintain; general documentation rules remain in the centraln guideline. Central guideline.

The page is good when a substitute can apply or review the standard without first collecting tribal knowledge.

scope

terms, scope and boundaries about Lesson vs SCORM einsetzen specify in concrete terms, including identity provider, mapping-regeln and roles-sync.

Concrete Parameter/rules

Den standard so record, dass which attribute verbindlich gemappt be and debug-/supportweg for login-problemen eindeutig entschieden are.

evidence

Name and link evidence directly: SSO-Mapping-documentation, test cases for Login/Logout, Logs and Fehlersamples.

Versionierung

Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with login-flows incl. logout/session.

Common pitfalls

This section captures real-world pitfalls from Lesson vs SCORM einsetzen; general guidance belongs in the central guideline. Central guideline.

  • scope driftet: Attribute change sich without abgestimmten Mapping-Update.
  • the rule is too abstract: Fallback-Login is not getestet.
  • evidence is missing: roles-Sync overwrites manuelle Zuweisungen.
  • the exception gets out of control: Pakete be overwritten without Versionierung.
Tip: It is better to document three concrete observations from real cases than to keep a long generic list.

Moodle reference (official docs 5.1)

Kurze Verweise on the offizielle Moodle documentation for Lesson vs SCORM einsetzen. So remains this Page AFANDI-spezifisch and vermeidet doppelte Grundlagen.

Official references

Documentation focus

  • Wahl justify: Moodle-native Verzweigungen (Lesson) vs. externes Paket/Tracking (SCORM).
  • UI path, role and test case record explicitly (not only the desired target state).
  • Mark deviations from AFANDI standards separatelyely so that updates remain easier to review.
Note: Moodle interfaces, paths, and options can vary depending on the version, theme, and enabled plugins. Therefore always include the version, role, and test context on the page.

Review & maintenance

Check this Page gegen reale processes about Lesson vs SCORM einsetzen – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.

  • Stimmen Mapping-rules with the IdP-Stand match?
  • Are Debug-Checks for the Support documented?
  • Gibt it recurring Login-Fehler?
  • Are SCORM-Pakete versioniert?

Review focus for „Lesson vs SCORM einsetzen“: Lesson; check especially identity provider, mapping-regeln and roles-sync.

Useful metrics

A few metrics are enough – what matters is that they trigger decisions or improvements.

For „Lesson vs SCORM einsetzen“ Kennzahlen directly an which attribute verbindlich gemappt be and the most frequent Praxisrisiken koppeln.

Login-Erfolgsquote

Anteil erfolgreicher SSO-Logins

Interval: monthly

Sync-Fehler

Fehlerhafte Synchronisationen je Lauf

Interval: monthly

Support-cases SSO

Anzahl SSO-bezogener Supporttickets

Interval: monthly

Next steps

Add jetzt the concrete Entscheidung about which attribute verbindlich gemappt be incl. Verantwortlichen, Datum and Verweis on sso-mapping-documentation.

On „Lesson vs SCORM einsetzen“ make especially clear as the next step: which identity provider, mapping-regeln and roles-sync apply in the standard case and which exceptions are time-limited.