CAMPUS VP Sample Clauses

CAMPUS VP. As the import is just possible for CAMPUS VP eViP exports and reacts just like the normal CAMPUS VP import no additional development took place.
View Source
CAMPUS VP. The export is arranged like a normal CAMPUS VP in the Classic- or Card-Player (DTL = diagnostic therapy loop).
View Source
CAMPUS VP. For the export a CAMPUS XML export file is generated and a XSLT transformation is started. It consists of a file called start.xslt which includes the files • virtualpatientdata.xslt, which includes vpd-fragen.xslt for knowledge questions • dataavailabilitymodel.xslt • activitymodel.xslt • lom_metadata.xslt • imsmanifest.xslt Those files generate the different files for the MVP package. For those HTML fragments that are not XML conform, the library HTML Cleaner (▇▇▇▇://▇▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇) is used. The already exported media files and the newly generated XML files are stored together with static files (e.g. the schema files) in one ZIP file.
View Source
CAMPUS VP. To import a CAMPUS VP eViP export file click on System ! Import case:
View Source
CAMPUS VP. For the import the already existing import module could be used for CAMPUS VPs only. The original XML file is base 64 decoded and unzipped. After that it is imported together with the media files.
View Source
CAMPUS VP. The CAMPUS fall.xml has had to be transformed via XSLT files to the VP XML files. This was made possible with ▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/xalan-j/ Xalan-J. For direct importing in CAMPUS the original CAMPUS XML file is GZIPed (for smaller space requirements) and base64 encoded put inside the XtensibleInfo.
View Source
CAMPUS VP. For inner CAMPUS VP import the virtualpatient.xml file is used because it contains the whole CAMPUS VP import format in the XtensibleInfo section. This section is interpreted and can be easily imported.
View Source
CAMPUS VP. To export a CAMPUS VP you have to open the case and select Learning Object ! eViP- Export:
View Source