Catalogue

1 Initial Problem

…

2 Conceptual Summary

With the catalog object it should be possible to display a list of objects. In a first version, only courses will be offered in the catalogue.

...automatically collect courses for course catalogues

...automatically collect courses for a course management system

Catalogue can be used for:

• Enrolment Object

• Study Programme: Automatically add users by role, membership or organizational unit
• Course: Automatically add users by role, membership or organizational unit
• Competence profiles can be assigned to OrgUnits

3 User Interface Modifications

3.1 List of Affected Views

Add

Create

Define Rules

Courses

Rules

Rules are AND-linked . It is possible to create an OR rule by grouping the rules.

Rule

A Rule-"line" for the course can be configured as follows

Define Views

Table

For the table it is possible to make the following column configurations. Hopefully with the Api Alignment we could provide later all properties of a course.

Detailed View

The Detail View is identically to the detail view of a Data Collection.

Specific Filter for Viewer

This is an additional filter criterion which additionally filters the list based on the properties of the viewer.

Manage Content

Studer, Martin [mstuder] Workshop: 16.05.2019 Multiactions for E-Mail, Assign to Coure, Assign to Group

Use Cases

See -> 1 Initial Problem

Archiv

...automatically collect users for a phone book table

...automatically collect users for a user gallery

Do we need a declaration of consent here? Privacy by Personal Profil Data Settings.

...automatically collect users for enrol them in a study program

Enroll to Study Program

Studer, Martin [mstuder] Workshop: 16.05.2019 We should not do this because of circular references.

See Study Programme: Automatically add users by role, membership or organizational unit

...automatically collect courses for course catalogues

...automatically collect courses for a course management system

Studer, Martin [mstuder] Workshop: 16.05.2019 Mixed object types should be possible.

3.2 User Interface Details

Catalogue should be used for

• Study Programme: Automatically add users by role, membership or organizational unit
• Course: Automatically add users by role, membership or organizational unit
• Competence profiles can be assigned to OrgUnits

3.3 New User Interface Concepts

None

4 Technical Information

I propose to introduce a centralized service for the collection process: https://github.com/ILIAS-eLearning/ILIAS/blob/c0ffbbed2293143facd6279511e28b5b5549175a/src/RuleEngine/README.md

5 Contact

• Author of the Request: Studer, Martin [mstuder]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

05 May 2019, Studer, Martin [mstuder] see also Course Catalogue

Killing, Alexander [alex], 14 May 2019: Thanks for the FR. This could be very valuable imo. I am not sure if I will be able to participte in the workshop, but I would like to ask you to address two points that need clarification.

• Query stragegy: Could you please elaborate on how and when the objects will be collected? It seems that the object sets will always be stored redundant in the catalogue and it should be configurable on what events the catalogue should be updated (create, update, cron). This might be challenging for a user and I would fear this kind of redundancy, since it may result in subtle inconsistencies. The alternative would be to always dynamically query the result set from the DB using a class like ilUserQuery. This might cost performance on complex queries, but if you add a simple caching mechanism, this could be countervailed imo.
• Policy strategy: The way how permissions on the catalogue object itself and on its subitems work together should be explained somewhere. This might be straightforward, if the catalogue will not permit access to anything that is not accessible by other means.

Studer, Martin [mstuder], 16 May 2019 - Workshop

1. We should not enrol users of catalog automaticaly to other ILIAS Modules.
2. A Catalog List should have actions like "E-Mail to" or "Enrol in Courses"
3. Mixed Object Types should be possible.
4. Should it be possible for an ILIAS Object to prevent of beeing collected?
5. Query Strategy: The Object will be stored redundant in the catalogue
6. Policy Strategy:
   ILIAS Objects: The catalog only shows a user the objects for which he has the "Visible" permission in the ILIAS repository.

Studer, Martin [mstuder], 20 May 2019

Policy Strategy: 

• ILIAS Objects: The catalogue only shows a user the objects for which the user has the "Visible" permission in the ILIAS repository.
• ILIAS Members: The catalogue only shows members of objects for which user has the permssions to see them.
• ILIAS Users: The catalogue only shows the user and attribute for which the Search-Setting in the ILIAS Administration is activated.

JourFixe, ILIAS [jourfixe], 17 JUN 2019 : We discussed Martin's suggestion and strongly recommend to break the request down to a simpler approach and to realise only a 'course catalogue' in the first round. Martin will adapt the request accordingly.

To get a common understanding of the feature we need more textual descriptions of the feature and its behaviour. Screenshot alone offer to much space for interpretation. As the API Alignment won't be available for 6.0, this feature could also realised without using the API alignment (if feature is accepted). We highly appreciate Martin's commitment to adapt the feature to the API alignement once this will be available in ILIAS.

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.