Difference between revisions of "Developer Area/Import//Export/LEAP Export/Internal Artefact Plugin"
From Mahara Wiki
< Developer Area | Import//Export | LEAP Export
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
The internal artefact plugin hooks into the [[Developer Area/Import%2f%2fExport/LEAP Export|LEAP export system]] to export all profile related artefacts. Due to profile artefacts not mapping nicely to entries - in fact, most profile artefacts become persondata elements within an entry - this plugin generates its own XML for most of them. | The internal artefact plugin hooks into the [[Developer Area/Import%2f%2fExport/LEAP Export|LEAP export system]] to export all profile related artefacts. Due to profile artefacts not mapping nicely to entries - in fact, most profile artefacts become persondata elements within an entry - this plugin generates its own XML for most of them. | ||
Revision as of 17:16, 12 May 2011
The internal artefact plugin hooks into the LEAP export system to export all profile related artefacts. Due to profile artefacts not mapping nicely to entries - in fact, most profile artefacts become persondata elements within an entry - this plugin generates its own XML for most of them.
Export Strategy
Apart from the Occupation and Industry profile fields, all artefacts are exported in a LEAP2A person entry. This entry always has the id portfolio:artefactinternal, and is referenced by the tag for the feed. Inside this entry are leap:persondata elements for most of Mahara's profile fields. The address fields are exported in a leap:spatial element.
Profile icons are linked to this element using a related link type. These are the only links created for the person entry.