CAMPUS Key Feature Sample Clauses
CAMPUS Key Feature. For the import each activity node is sequentially used: • Get the ActivityNode • Get all the referenced DAMNodeItems • Get all the referenced media files and VP elements • Serialise all VP elements to XHTML, probably with special templates • Import the serialised XHTML and media data in one slide (key feature section)
CAMPUS Key Feature. To import an eViP file as a key feature case click on System ! Import case:
CAMPUS Key Feature. The eViP KF import translates the eViP XML files to CAMPUS KF XML import file using a XSLT style sheet. It takes every ActivityNode and looks for referencing VP elements. Those elements are put together in one big XHTML per Node while some VP elements are rendered into XHTML structures (e.g. InterviewItems are rendered with one one div for the question and one div for the answer).
CAMPUS Key Feature. For the export the CAMPUS KF export module is used. The generated XML file is transformed into the different files using the export.xslt (which includes the vpd-fragen.xslt sheet). After adding the media files and static files, everything is packed into a ZIP file.
CAMPUS Key Feature. To export a CAMPUS key feature case you have to open the case and select Learning Object
CAMPUS Key Feature. For the import the XSLT file evip_to_keyfeature.xslt is used. The style sheets loads the different MVP files and generates a keyfeature.xml file for the normal CAMPUS KF import module.
CAMPUS Key Feature. Every section (= slide) is transformed to one VPDText, one DAMNode and one ActivityNode. The ActivityNodes are just sequentially arranged then.
CAMPUS Key Feature. The CAMPUS keyfeature.xml has had to be transformed via XSLT files to the VP XML files. This was made possible with ▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/xalan-j/ ▇▇▇▇▇-▇.