Improvement of import and export

1 Requirements

1.1 Motivation

Here’s an issue that was raised by Anne Frey during the T&A export tests, but it’s relevant for other objects, too.

Currently, ILIAS is missing a validation of XML import files. As Anne doesn’t know the implementation in ILIAS, she could only give a generic recommendation to improve this. For a (syntactic) verification, she would recommend to use a PHP function (e.g.: http://php.net/manual/en/domdocument.validate.php [^]).

I don’t have the technical knowledge to suggest a solution, but I would ask our programmers to look into this.

1.2 Specification

• full xml format validation for all xml files an import package contain (dtd or schema)
  • in most cases no validation is done in the current state
  • it is to be checked if all required dtd/schema files are available
• validation of the package's object type and helpful failure message, when type mismatched
  • at the time beeing i can submit a course packege to the test module import,the test tells me, that the package contains no questions, sure - it isn't a test module package
• extend/change the common package format, so package's filename gets independent from content
  • the package's generated with the current state are named as follows: <UnixTS>__<NicID>__<ObjType>_<ObjID>.zipthe content's first level folder is equally named and these path-/filenames are used during extraction of the package.
  • when the filename differs from the content's first level folder name, an import is not possible anymore
  • an exported ilias object package should be renameable for the individual needs of the creator (e.g. for archiving)
• support formatted xml files containing line breaks and indentations
  • this requires at least a discussion about the handling of strings from tag contents
  • will a simple trim make any problems? possible <![CDATA[ ... ]]> occurences also need to be considered

2 Additional Information

• Idea / concept: Kruse, Fabian [Fabian]
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

JourFixe, ILIAS [jourfixe], Oct 10, 2016: We highly appreciate this suggestion and the idea of an improved import procedure. Please present a concept for a future processing of the XML import (and also about how to handle 'very old export files') and present it in one of the next Jour Fixes.

Zenzen, Enrico [ezenzen], 24 AUG 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

4 Implementation

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