Feature Wiki
Tabs
Copy Content from Media Pool via Page Editor
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 2.1 RFC 2119
- 2.2 Requirements
- 3 User Interface Modifications
- 4 Technical Information
- 5 Privacy
- 6 Security
- 7 Contact
- 8 Funding
- 9 Discussion
- 10 Implementation
This is a draft. Parts or all of it is subject to change. In case the author had sufficient caffeine levels he has marked parts he is not sure of yet with "(?)" where needed. Discussion is welcome.
1 Initial Problem
Media pools offer a convenient way of storing content/media for use in multiple locations. However, users can only link content to different target locations. This is not always wanted. The option to copy a content element should be offered to allow users to decide if they want to link an element and be able to quickly update the element via the mediapool or to copy the element in case this is not needed and the element has to be adjusted for the target object specifically.
2 Conceptual Summary
2.1 RFC 2119
In order to provide a clear understanding of the importance/relevance of a requirement we use the following keywords as described in RFC 2119:
- MUST, MUST NOT
- REQUIRED
- SHALL, SHALL NOT
- SHOULD, SHOULD NOT
- RECOMMENDED
- MAY
- OPTIONAL
2.2 Requirements
Users must be able to decide if they want to link or copy a content element from a media pool.
3 User Interface Modifications
3.1 List of Affected Views
- ilpccontentincludegui
3.2 User Interface Details
An option to copy selected content from a media pool is added to the current GUI.
3.3 New User Interface Concepts
None.
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
No privacy implications.
6 Security
No security implications.
7 Contact
- Author of the Request: Sesterhenn, Fabian [sesterhenn]
- 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.}
8 Funding
If you are interest in funding this feature, please add your name and institution to this list.
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}.
Last edited: 2. May 2022, 13:28, Sesterhenn, Fabian [sesterhenn]