About Ledger Data

The Learning Ledger is a holistic view of every student in your school. You can import almost any data that is important to your school community. Examples of data sources commonly imported include NAPLAN, PAT, Allwell, AGAT, CogAT, semester grades, effort, teacher comments, GPA, attendance summaries, student goals, summative and formative activities, learning engagement and wellness.

Adding a data source to Ledger is as simple as sending us a sample of the data you wish to have imported. We will write an import recipe based on the data which you will be able to use to import data via a simple drag-and-drop interface whenever needed. We can also import your data for you.

Ledger also supports direct posting via xAPI. Please get in touch if your data source supports this eLearning standard.

About Recipes

Ledger is completely dynamic which allows us to take almost any data your school wants to see. In order for a data source to be added to the Ledger, all that needs to happen is that we need to create an import recipe. The recipe simply tells the Ledger importer:

• Which columns to import from your spreadsheet and which to ignore

• How to choose the data to import based on repeatable criteria (e.g. only import rows where the data in the 'Final Results' column = 'Yes')

• What name to give the fields we import on screen

• How to group the data in the timeline

• How to group the data in the Profiler and Mixer

Once the recipe is written the data can be imported as needed, either by you or by us.

In order to add a new recipe to the ledger:

• Send an export of the data to us containing real values which adheres to the data guidelines below.

• Let us know which fields you would like imported, and what you would like them to be called. We will contact you if we have questions.

• We will create a new recipe for that data source and import the spreadsheet you have sent us.

• Once the data is imported, we will contact you so that you can take a look and let us know if any changes are needed.

• Once the recipe is agreed, it is available in the Ledger Import for your school. You can import data as required. We can also import data for you.

Providing Data for Recipe Creation

When adding a new data source to Ledger, the first data set you send us acts as a blueprint which sets the format for all future imports. The first step to adding a data source is sending us an export of the data. Before sending, please make sure it adheres to the following:

• The data is repeatedly exportable in a CSV, XLS or XLSX format.

• The data is going to be consistent. We create an import recipe based on the field names in the first export. These field names should not change.

• The data needs to be complete. Data should only be imported once it has been finalised. For example, please don't send semester grades that are still being finalised.

• The data needs to be consolidated. Any necessary data consolidations or calculations need to have been done before data is imported. We can do selective imports where we only import data where a field contains a certain value (e.g. only import rows where the data in the 'Final Results' column = 'Yes'). However, we don't do calculations or at import time.

When you are ready to send your data, please send to your Literatu representative.

We will work as quickly as possible to get your recipes created and your data imported, but please be aware that we do work on a queue basis.

To minimise delays:

• For recipe creation please make sure you send us correct and complete data which adheres to the criteria above. and let us know which fields to import, what to call them, and information about any other criteria (e.g. only import rows where the data in the 'Final Results' column = 'Yes').

• For ongoing data import where we import data for you The first thing that happens when an import is done is a check to see whether your data matches the format the recipe is expecting. If your data fails the check, your import will be moved to an investigations queue. This queue is slower. There, a support rep will investigate to find out why the data no longer matches the recipe format. We run these 2 queues to enable us to keep moving quickly through importing data which is correct. To avoid waiting, please check to make sure your data matches the format you initially sent when the recipe was created.