Catalogue View for Repository Items

Must-haves:
Step 1: KS-improvement: add new interface concepts (3.3)
Step 3: implement catalogue view (3.2)

Nice-to-have:
Step 2: Improved Creative Commons Support : add CC0-licence
Step 4: Show availability and preconditions in modal
Step 5: Presentation of Items with preconditions

1 Initial Problem

Up to now, ILIAS provides two kinds of item presentations – list and tiles. While the list item presentation is focused on a simple presentation of the item and a lot of its properties, the tile view offers a visual attractive presentation of each items with a reduced amount of properties presented. But ILIAS lacks a presentation that is visual attractive _and_ presents a lot of the item's properties. Such a view on the items of a repository object would be fine to create a kind of catalogue of learning contents.

2 Conceptual Summary

A third type of "item presentation" called "catalogue view" should be introduced to the repository objects.

• A catalogue card consists of an image and a list of textual presented properties, supplemented by the known actions dropdown, new implemented glyph for the action "Make Favourite" and a presentation of the learning progress status
• The catalogue card re-uses the tile image - if available.
• Textual informations are
  • Title
  • Description
  • Availability
  • Preconditions
  • Online-Status
  • Type (e.g. file type or LM type)
  • size (if its a file)
  • Metadata: Author
  • Metadata: Keywords
  • Metadata: Licence (incl. CC-img)
  • learning progress (if active)

3 User Interface Modifications

3.1 List of Affected Views

• repository item > settings
• repository item > "catalogue view"

3.2 User Interface Details

The description shouldnt smash the panel, when its longer than 2 lines - in this case "..." shows, that there is more description. Maximum length of description is set in administration as before.

Catalogue view: 

Settings of repository object: (here: category)

3.3 New User Interface Concepts

New or modified user interface elements (for Kitchen Sink) are:

1. presentation of images in panel items
2. presentation of links in panel items
3. presentation of favourite glyph in panel

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Kunkel, Matthias [mkunkel], Seibt, Alina [alina.seibt]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• ILIAS-Verein within the projects DigikoS and VerDatAs

9 Discussion

10 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}.