Main Menu
LEAP2A
Newcastle University was involved in the production of the Leap2A Specification. This section of the site contains our local resources for use with this specification.
For more details about the specification, please see the leapspecs.org WIKI at http://wiki.leapspecs.org/2A/specification
Our local category scheme is available here.
An example export from the ePET portfolio is available in XML Format and as a ZIP file.
These exports have been updated to conform to the latest version of the Leap2A specification (2010-07).
These have been checked at
http://validator.w3.org/feed/ and the
Leap2A validator,
and have been found to be valid Atom and Leap2A records.
The full import and export procedure has been included in the online demonstrator. This will allow you to test your downloads in ePet and test ePet downloads in your system.
Notes on implementation
The following notes are to aid anyone wanting to import an ePet LEAP2A export into their own system. If you have any further queries, please contact Paul Horner.
- On import, we only recognise two types of link records - parent and child. The LEAP2A Links are stripped down to this
bi-directional format on import and the implied differences between the types are ignored. On export, we have used what we feel
is the most applicable format.
- UPDATE - we do now look at the type, but still work on a parent/child relationship basis because the specific type of relationship can make it a lot easier to work out where something should go.
- We have chosen (where possible) to include links in both directions. If there is a conflict between these on import, only the parent link will be recognised.
- Where no author is included in an entry, the author included in the feed record should be used.
There are still some things that haven't been implemented yet.
- Limited CV data is still missing. We've implemented persondata (address, phone, etc), but we still need to cover the
following core parts of the CV - qualifications (which may be outside the current leap2a scope?), languages and publications.
On import, only the personal statement and limited content details are updated - we simply ran out of time!
- Language implementation needs some thought. We currently support the europass language passport, which contains self-assessments against foreign languages, with evidence based on experience and qualifications. This should map very nicely to the LEAP2a standard, because the self assessments are generic skills, the diplomas are qualifications and the other evidence is an activity. However, we haven't yet completed this as part of the export because of time constraints.
- The exported file system does not actually follow the same structure of the ePET file store. This isn't actually going to be that major a problem, but might cause some issues for users.
The script we use to formulate the first part of the import is available for download here. This is a Python script that takes and Atom Feed (or LEAP2A version 2009-03) and returns a Python dictionary that you can manipulate as part of your import procedure. It's not complicated, but what comes out of the end is a little bit neater to work with than the plain XML feed (in my opinion).