Feature Wiki

Information about planned and released features

Tabs

Adopt Content: Allow Folders as Source

1 Initial Problem

The process to adopt contend for courses or groups (Course / Manage / Adopt Content) does not allow the user to select a folder as source. Only course objects and group objects are allowed. This limits how content can be structured elsewhere in the repository, i.e. if you have a course or group container that functions as a "content-pool" for tutors, tutors have to seperate content (i.e. tests, files etc). that belongs to different courses/modules with more sub-groups.

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 select a folder from within a course / group as source container for the copying process when adopting content. The selected folder object itself will not be copied, the same way a group object selected as source when adopting content is omited.

3 User Interface Modifications

3.1 List of Affected Views

  • ilobjectcopygui / adoptContent

3.2 User Interface Details

The tree must allow for folders to be selected as source for copying content.

Mockup 1: Tree view for adopting content with option to select subfolder as a source

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

None.

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: 11. Apr 2022, 11:00, Sesterhenn, Fabian [sesterhenn]