Learn - People Data

Data disclaimer

We strongly recommend reviewing the quality of your data before transferring into Learn.  Learn user data will only ever be as accurate as the data being sent to and processed overnight by Kallidus if you're using an overnight data file being sent to Kallidus to keep your user data up to date.

What data do I need?

In order to understand what data you need to transfer to the LMS you will need to ask two questions:

1. What do we need to report on:
   1. Department?
   2. Region?
   3. Role?
2. How will I assign learning?
   1. Job role?
   2. Department?

What data does Kallidus need?

The minimum data Kallidus requires is

• A unique identifier – this could be an employee number, or email address
• A unique username – this can be the same as your unique identifier – users will use this to log in
• First name
• Last name

Some Kallidus functionality requires further information:

• Line manager approvals – this requires a relationship to exist between a user and their manager
• Notifications – Kallidus has a built in message board; if you wish to notify users of course enrolments or deadlines you will need to supply an email address.

Data rules

• LMS Roles control what people can do in the system, ranging from Student – up to LMS Administrator. (Who needs what role, how can we identify?)
• Default password for first log in
• Line manager relationships – how can we identify?
• Group creations – what groups of users would you like to be created and maintained by the LMS?
• User field mapping – from your data, which information needs to go where in the LMS?
• Leavers – when people leave the organisation, how will the LMS know to un-enable?

Timescales

Est. Time	Stage	Description
1 day	1	Define data extract
1 day	2	Map to Kallidus fields
2 days	3	Send to Kallidus to load into LMS and test
2 days	4	Make changes and reload
1 day	5	Automate

NB: This will be an iterative piece of work spread out over an elapsed period, not full and consecutive days.