Difference between revisions of "Developer Area/Import//Export/Interoperability"

From Mahara Wiki
Jump to navigation Jump to search
(Created page with "Mahara's [http://wiki.cetis.ac.uk/LEAP2A_specification Leap2A] support means that you can both export your data from a Mahara system, and import it again either into another Maha…")
 
 
(2 intermediate revisions by one other user not shown)
Line 5: Line 5:
 
<div class="wiki-tree">
 
<div class="wiki-tree">
  
* [[Developer Area/Import//Export/Interoperability/EPET|ePET]]
+
* [[Developer Area/Import%2f%2fExport/Interoperability/EPET|ePET]]
* [[Developer Area/Import//Export/Interoperability/EProgress File (KS4)|eProgress File (KS4)]]
+
* [[Developer Area/Import%2f%2fExport/Interoperability/EProgress File (KS4)|eProgress File (KS4)]]
* [[Developer Area/Import//Export/Interoperability/PebblePad|PebblePad]]
+
* [[Developer Area/Import%2f%2fExport/Interoperability/PebblePad|PebblePad]]
  
 
</div>
 
</div>
Line 16: Line 16:
 
* [[Developer_Area/Import//Export/Interoperability/EProgress_File_(KS4)|eProgress File (KS4)]]
 
* [[Developer_Area/Import//Export/Interoperability/EProgress_File_(KS4)|eProgress File (KS4)]]
 
* [[Developer_Area/Import//Export/Interoperability/PebblePad|PebblePad]]
 
* [[Developer_Area/Import//Export/Interoperability/PebblePad|PebblePad]]
 +
 +
[[Category:Developer Area]][[Category:Interoperability]]

Latest revision as of 12:29, 17 May 2011

Mahara's Leap2A support means that you can both export your data from a Mahara system, and import it again either into another Mahara or another ePortfolio system that has implemented the Leap2A standard.

Here we have documented how well information travels between Mahara and other systems (and vice versa).

Subpages