IT Services Reference
Powered by

Oliver Standard Configuration (WONDE Sync)

In 

Look up the Edumate-to-Oliver field mappings recorded for WONDE synchronisation, including the user fields required by the shared SAML configuration.

Synchronisation of User data into Oliver v5 is achieved via a WONDE synchronisation from Edumate, with each Oliver instance authorised to ingest data from the corresponding WONDE endpoint.

For some clarity it is worth noting that WONDE ingests data from Edumate via the Edumate API. There is no specific schema (mapping of fields from Edumate to Oliver).

Oliver ingests WONDE data and the schema (field mappings) required is determined by the application consuming the import, in this case Oliver.

WONDE synchronises the following minimum Edumate fields to these Oliver fields.

To use the single CCM enterprise app across all schools, three Oliver fields MUST contain the data as indicated via the WONDE sync.

Edumate (WONDE) Field Oliver Field
Student/Staff Number + ALIAS* (Oliver Mandatory field)
Preferred Name FIRST NAME
Surname LAST NAME
Email + USERNAME
??? BRANCH
??? BORROWER TYPE
Student/Staff Number + STUDENT CODE
Salutation MAILING TITLE
Gender GENDER
Home Address ADDRESS
Mobile 1 MOBILE
Email EMAIL ADDRESS

* Oliver Mandatory Field

+ CCM Standard Configuration Requirements

WONDE creates its own unique synchronisation ID called the SMSID and this is used for each synchronisation cycle. As this ID is established on first sync of a user record, any future changes to Edumate data is automatically updated in Oliver, INCLUDING any changes to the users email as a result of name changes etc. This works well as the users Azure UPN is also updated in the same scenario, so SSO will continue to work.

Some Notes:

  • The ALIAS field is mandatory, and MUST be unique within each individual Oliver instance.
  • The ALIAS field is ALSO the field that is used for user barcodes within Oliver. Therefore IF you use ID cards with barcodes for your users do NOT change the ALIAS field without lots of thought and planning.
  • The USERNAME field is not mandatory but MUST be unique. And of course without a Username that corresponds to a user UPN there will be no logon.