Show Advanced KnowledgeHide Advanced Knowledge

Solve Dilemma of SOAP vs Course-Export

1 Initial Problem

There is a interaction of course- and group-export and SOAP-course-and-group-export:

• On the one handside the SOAP-course-export must be downwardcompatible,
• one the other handside the Course-XML should not comprise any settings of course-foreign settings like container, news, sorting,..)

This problem must be solved.

• Kurs und Gruppen können über SOAP Webservice angelegt werden, dann wird ein standardxml verwendet, das wird krampfhaft stabil gehalten. Das wird einmal gebrochen werden müssen

2 Conceptual Summary

The methods of the SOAP-based Webservice for administering with courses needs to be reworked:

• Though the SOAP-methods for administrating with coruses (CRUD) are described in the course-DTD, there is no gernaeral concept for including settings from other services.
• The „Standard“ XML-Im/Export allows for including head- and tail-dependencies, which can integrate settings and data from other services in other components. These dependencies are structured in subdirectories component-zip-archive. For technical reasons (WHICH) this structure  can not be reused for the SOAP-based administration of courses. 

Because of this with ILIAS 7 some not -downward-compatible changes need to be made. The respective SOAP-mathods are marked deprecated with Release 6.

3 User Interface Modifications

3.1 List of Affected Views

None.

3.2 User Interface Details

GUI not affected.

3.3 New User Interface Concepts

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 Information

{ 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 Implications

{ 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: Tödt, Alexandra [atoedt]
• Maintainer: Meyer, Stefan [smeyer]
• 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}.