Considering taxonomy assignments in export and import

1 Initial Problem

When exchanging content between ILIAS installations and the involved installations are using identical global taxonomies, the taxonomy assignments of exported and imported content should not get lost.

2 Conceptual Summary

Export and import of ILIAS objects with taxonomy support should consider taxonomy assignments. The export should add information about the used global taxonomy of this installation to the export file. The import should read out this information and try to re-assign the content to the related taxonomy if it also exists on the target installation. This requires NIC registration to identify the origin of the taxonomy.

The behavior shoul be similar to metadata: You can ex- and import globals taxonomies (administration > taxonomies). Taxonomy assignments of imported objects are also displayed accordingly in the new system if the global taxonomies are identical in both the new and the old system.

3 User Interface Modifications

3.1 List of Affected Views

no affected views

3.2 User Interface Details

none

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

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

• …

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