Skip to content

Jürgen Jakob

My feedback

1 result found

  1. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Leganto  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jürgen Jakob supported this idea  · 
    An error occurred while saving the comment
    Jürgen Jakob commented  · 

    ________________________________________
    Problem (short)
    Leganto shows two actions that read as “Remove from My Lists” but have different effects: one merely hides the list; the other can sever the course/list link, so the list vanishes until reopened via LMS (LTI). The generic wording is reused elsewhere (e.g., lists added from Find Lists), which amplifies confusion.
    We can tailor menu visibility by role and labels in Alma (new UI), but cannot switch the behavior to “hide only” today. [knowledge….sgroup.com] [knowledge….sgroup.com]
    ________________________________________
    Impact
    • Accidental loss of access: students think they’re just tidying My Lists but effectively remove course access until they reenter via LMS.
    • Support load and avoidable tickets; unclear recovery path.
    • Inconsistent UX wording due to one label serving multiple contexts. [knowledge….sgroup.com]
    ________________________________________
    Repro (condensed)
    1. Course with list published to Course Students.
    2. Student opens list; chooses “Remove from My Lists.”
    3. List disappears for the student; it reappears only after LMS (LTI) access restores the link. (Label and menu are configurable; behavior is not.) [knowledge….sgroup.com]
    ________________________________________
    Request
    1. Tenant level policy for course assigned lists:
    o HIDE_ONLY (remove from My Lists without changing course association),
    o DISABLED (don’t show to students), or
    o UNENROLL (current), with optional confirmation dialog.
    2. Separate label/tooltip keys for course assigned vs. self added lists to clarify consequences. [knowledge….sgroup.com]
    Examples
    leganto.removeFromMyList.behavior.forCourseAssigned = { HIDE_ONLY | UNENROLL | DISABLED }
    leganto.removeFromMyList.requireConfirm.forCourseAssigned = true|false
    ________________________________________
    What we can do now (and need confirmation for)
    • Hide risky action for Students via UI › List Menu in Alma (new UI). Please confirm the exact action key in the new UI config. [knowledge….sgroup.com]
    • Differentiate wording via General › Labels (two distinct labels + confirmations). Please provide the canonical keys used by the new UI. [knowledge….sgroup.com]
    • Add a student only banner (General message) explaining consequences/recovery (general_message + general_message_role=student). [knowledge….sgroup.com]
    • (Optional) Disable auto add to My Lists on first LTI access (as per Ideas Exchange—enable via support). [ideas.exli…sgroup.com]
    ________________________________________
    Acceptance criteria
    • Students don’t see the course leaving action (or, if shown, it’s clearly labeled + confirmed). [knowledge….sgroup.com]
    • Distinct labels/confirmations exist for hide vs. leave course, configurable in General › Labels. [knowledge….sgroup.com]
    • (Optional) Auto add via LTI is disabled on request for our tenant. [ideas.exli…sgroup.com]
    ________________________________________

    Jürgen Jakob shared this idea  ·