Feature Wiki

Information about planned and released features

Tabs

Media Pools and Media Objects

1 General

Maintainer and Tester

  • Media Pool

    • Authority to Sign off on Conceptual Changes: akill
    • Authority to Sign off on Code Changes: akill
    • Authority to Curate Test Cases: atoedt
    • Authority to (De-)Assign Authorities: akill
    • Tester: kiegel
    • Assignee for Security Reports: akill
    • Assignee for Security Issues: akill
    • Unit-specific Guidelines, Rules, and Regulations: LINK MISSING
  • Media Objects

    • Authority to Sign off on Conceptual Changes: akill
    • Authority to Sign off on Code Changes: akill
    • Authority to Curate Test Cases: kunkel
    • Authority to (De-)Assign Authorities: akill
    • Tester: kiegel
    • Assignee for Security Reports: akill
    • Assignee for Security Issues: akill
    • Unit-specific Guidelines, Rules, and Regulations: LINK MISSING

 

Additional

Media Pool

Roadmap

Short Term

Mid Term

Improve Architecture

  • Introduce repository pattern
  • Improve DI handling
  • Factor business logic out of UI classes

Long Term

 

Media Objects

MediaObjects

Short Term

Link Areas

  • Link area editing should work client side, similar to editing of interactive images in the page editor.
  • Link areas should be responsive/scalable.

Prio "On Request"

Access Handling

The fact that re-using media elements creates references that all allow write access to a media object if write access to the container is given sometimes confuses users and leads to undesired behaviour. However re-using (not simply copying all the time) media objects is a central use case in most larger content creation processes.

It would be possible to think of a more sophisticated access handling and for giving options (copy/reference) during copy processes. However this all would require some conceptual work.

Anchor Support for Link Areas

Internal links added to link areas currently do not support the anchor attribute.

 

2 Projects

The following projects are planned or have been realised for this component:

3 Suggested Features

In the following list you can add a request for a new feature or pick-up an already suggested feature about that should be decided again. The lists after show existing suggestions and scheduled features of this component.

  1. ...

SUGGESTED FOR 11

Already suggested

4 Scheduled Features

The following features have been scheduled / published in ILIAS Release 11:

The following features have been scheduled / published in ILIAS Release 10:

The following features have been scheduled / published in ILIAS Release 9:

The following features have been scheduled / published in ILIAS Release 8:

The following features have been scheduled / published in ILIAS Release 7:

The following features have been scheduled / published in ILIAS Release 6:

The following features have been scheduled / published in ILIAS Release 5.4:

The following features have been scheduled / published in ILIAS Release 5.3:

The following features have been scheduled / published in ILIAS Release 5.2:

The following features have been scheduled / published in ILIAS Release 5.1:

The following features have already been developed and published in ILIAS Release 5.0:

The following features have already been developed and published in ILIAS Release 4.4:

 
The following features have already been developed and published in ILIAS Release 4.3: 
The following features have already been developed and published in ILIAS Release 4.2: 
The following features have already been developed and published in ILIAS Release 4.1: 
The following features have already been developed and published in ILIAS Release 4.0:

5 Redundant, Outdated and Rejected Feature Requests

Requests that are outdated or redundant (already implemented in other requests)

Rejected Feature Requests

Last edited: 23. Oct 2024, 14:24, Gruber, Ann-Christin [acgruber]