Look Before You UKLeaP An Overview of BS8788

1
Look Before You UKLeaPAn Overview of BS8788

• Carl Ebrey

2
Disclaimer

• Whilst the information contained within this
  presentation should be correct, no guarantees are
  made to this effect. Any errors/omissions should
  be reported to Carl Ebrey (please).

3
Disclaimer Part 2

• UKLeaP was like that when I got here. Its not
  my fault.

4
Background Info

• Currently no defined way to transfer PDP

• Schools dont talk to colleges

• Schwartz and Tomlinson reports in 2004

• A standard is required

5
Coming on in UKLeaPs and Bounds

• Began life as IMS LIP

• Was adopted and became UK LIP

• Through development became UKLeaP

• UKLeaP is now BS8788

6
Transferring Data The Different Approaches

• Whole record transfer

• Reference transfer

• Centralised system

7
Taming the Beast UKLeaP in More Detail
8
Schemas and Vocabularies

• XML standard is defined by schemas

• Values representing types are held in
  vocabularies

• Vocabularies are currently held as Excel files
  plans are to change to VDEX files

9
Application Profiles

• BS8788 is big!

• Nobody should (realistically) need to use all of
  it

• Application profiles define which parts of the
  standard are relevant to a particular application

10
Looking at a UKLeaP Document
11
Whats in a Name?

• ltformnamegt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tysour
  cegt
• lttyvaluegtPreferredlt/tyvaluegt
• lt/typenamegt
• lttextgtBob Carolgeeslt/textgt
• lt/formnamegt

12
Whats in a Name?

• ltnamegt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tysour
  cegt
• lttyvaluegtFulllt/tyvaluegt
• lt/typenamegt
• ltpartnamegt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tyso
  urcegt
• lttyvaluegtGivenlt/tyvaluegt
• lt/typenamegt
• lttextgtBob Davelt/textgt
• lt/partnamegt
• ltpartnamegt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tyso
  urcegt
• lttyvaluegtSurnamelt/tyvaluegt
• lt/typenamegt
• lttextgtCarolgeeslt/textgt
• lt/partnamegt

13
Addressing the Issue

• ltaddressgt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tysour
  cegt
• lttyvaluegtPrivatelt/tyvaluegt
• lt/typenamegt
• ltstreetgt
• ltstreetnumbergt50lt/streetnumbergt
• ltstreetnamegtSomewhere Stlt/streetnamegt
• lt/streetgt
• ltcitygtSomewherelt/citygt
• ltregiongtSomewhereshirelt/regiongt
• ltpostcodegtSO12 3MElt/postcodegt
• lt/addressgt

• This is an ideal example!

14
Telephone Numbers

• ltcontactinfogt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tysour
  cegt
• lttyvaluegtPrivatelt/tyvaluegt
• lt/typenamegt
• lttelephonegt
• ltareacodegt01234lt/areacodegt
• ltindnumbergt567890lt/indnumbergt
• lt/telephonegt
• lt/contactinfogt

15
Email Addresses

• ltcontactinfogt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tysour
  cegt
• lttyvaluegtPrivatelt/tyvaluegt
• lt/typenamegt
• ltemailgttest_at_test.comlt/emailgt
• lt/contactinfogt

16
Date of Birth

• ltdemographicsgt
• ltdategt
• lttypenamegt
• lttysource sourcetype"standard"gtUKLeaPlt/tyso
  urcegt
• lttyvaluegtBirthlt/tyvaluegt
• lt/typenamegt
• ltdatetimegt1977-10-03T000000lt/datetimegt
• lt/dategt
• lt/demographicsgt

17
Relational XML

• No surprises so far

• UKLeaP uses relationships to provide a logical
  structure to its elements

• These relationships, and their types, are key to
  making UKLeaP work

18
Relationships

• A graduate of Nottingham University-

• A QCL node representing her degree

• An affiliation node, representing her
  affiliation with the university

• An activity node, representing the activity of
  doing the degree itself

• A relationship node of type Supplements
  connecting the activity with the QCL

19
Exporting and Importing Data from UKLeaP
20
Developing Application Profiles

• Look at the data you hold to see what youre
  interested in

• Map the data against the UKLeaP schemas

• The result is your version of UKLeaP your
  application profile

• When importing and exporting data, youll be
  working with your application profile

21
Exporting Data

• Probably the easier part of UKLeaP

• Using a skeleton UKLeaP document, populate the
  fields with data from your DB

22
Mapping Between Profiles

• Before transferring data, a mapping needs to be
  done

• Both parties need to agree on what fields
  represent what data

• An accurate mapping makes importing the data
  easier

23
Mapping Between Profiles
24
Importing Data

• A bit trickier than exporting

• Transform input UKLeaP into a UKLeaP document
  matching your application profile

• Parse resulting document and insert data into
  your DB

25
Importing Data at UoN

• Input data is transformed into UoN UKLeaP

• UoN UKLeaP is transformed into DBXML

• DBXML is parsed and the data inserted into the
  DB

26
Importing Data at UoN

• Example DBXML document

lt?xml version"1.0" encoding"utf-8"?gt ltdbdatagt
lttable name"std_PGCE_CEP_details"gt ltlinegt
ltitem field"forename"gtBananalt/itemgt
ltitem field"surname"gtManlt/itemgt ltitem
field"birth_date"gt1977-03-30T000000lt/itemgt
lt/linegt lt/tablegt lt/dbdatagt
27
References

• http//www.imsglobal.org/profiles/index.html
• http//www.imsglobal.org/vdex/
• http//www.cetis.ac.uk/profiles/uklip/