Show Advanced KnowledgeHide Advanced Knowledge

Improved Landing Pages

1 Description

ILIAS resources are often linked to from the outside. However if a user finds himself on an information page, it is quite hard for him, how to find out, how to get access.

I a user land on a landing page, there are two primary interests for him:

• Getting information about the resource
• getting access to it.

The latter is not well supported.

We wrote an interaction pattern, on how to deal with this situation: Make the next possible action clear are visible.

Full pattern:
Landing Pages for LMS interaction pattern. (PDF, 500kb)

1.1 These are the situations a landing page has to deal with:

1.2 Ideas

1.3 Context

2 Status

• Scheduled for: not scheduled yet (has been scheduled for v. 4.3 but postponed due to missing funding)
• Funding: Required
• Development: Feature is to be developed by leifos

3 Additional Information

• If you want to work on this feature, I'm happy to help you design it: roland.studer@psy.unibe.ch

4 Discussion

HL: We suggest the following behavior:

• If it`s possible to "join" a course, then users does see in the info-tab in "Access" a new information with a corresponding button: "To become a course member, click on the button below".
• This new button "Join course" should be a bigger button - similar as the new "Start survey"-button, designed in survey and test-tool (ELBA-branch).
• Clicking this "Join course" button opens the "Join"-tab.
• If users are not logged in, then they can also click this "Join course"-button, but they then first are redirected to the login mask, before they see the the "Join"-tab.

JF 28 Mar 2011: We highly appreciate the improvements for this process and would like to try to get it funded and implemented for ILIAS 4.3. There are some technical implications that need still to be discussed, but we like the general idea.

Florian Suittenpointner, 13 Apr 2011:
Just one addition regarding your case distinction:
There might be cases when a link points to a course in ILIAS that is not accessible due to lacking roles/permissions.
Example scenarios:

• User is a course member but has not been assigned to another (superordinated) local role that's necessary to access the place where the course is located. e.g., the local role "Employee in department X". This role might lack because the employee has been forgotten or because he's new in the company.
• User is "Anonymous" but the course isn't accessible because a superordinated category isn't accessible for this role.

In these cases, the user is by now only redirected to the login page without ANY further information. Maybe there could simply be a message telling him that there are permissions lacking. A better alternative was a message telling what permission for which object is lacking and maybe even who's the owner of this object.

5 Follow-up