Developer Area/Import//Export/Interoperability: Difference between revisions
From Mahara Wiki
< Developer Area | Import//Export
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
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 Mahara or another ePortfolio system that has implemented the Leap2A standard. | 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 Mahara or another ePortfolio system that has implemented the Leap2A standard. | ||
| Line 20: | 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 13:29, 17 Mayıs 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).