You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
-
# ILR_File_Creator
1
+
# ILR_File_Creator
2
+
3
+
## Overview
2
4
3
-
## Overview:
4
5
The DFE tool for creating XML files that can be uploaded to their website is slow and limited in its function. My organization an Airtable that contains all the information it asks for but its hard to move all that information into the DFE tool. To fix this we built a new ILR tool that takes the CSV values generated from our Airtable and processes them to a XML file automatically. If you want to create a similar Airtable or Excell document that can be fed into this tool a CSV for creating one is at the bottom of the readme. This project is an electron application and following the set up instruction will create an app for whatever operating system you build it on. If you want to make aplications for other operating systems more information about distributing electron apps with electron forge can be found [here]([url](https://www.electronforge.io/)).
5
6
6
7
## User Stories
@@ -9,19 +10,15 @@ The DFE tool for creating XML files that can be uploaded to their website is slo
9
10
* App will tell user if there are any empty or missing fields in the CSV list
10
11
* App will return a XML file to the user thats structure matches that required by the DFE
11
12
12
-
*## Libraires Used
13
+
## Libraries Used
13
14
14
15
* electron
15
-
16
16
* electron forge
17
-
18
17
* xmllint
19
-
20
18
* papaparse
21
19
22
-
23
-
24
20
## Usage
21
+
25
22
This repo can be used to update and create copies of the ILR tool app. Bellow I will give general instructions for making creating copies of the app and how to update the tool when the ILR produces new versions. (note I can not account for everything they might change in a version and future users may need to update the code to account for changes made in a new academic year) Finally I will provide instructions for how to use the app and organize your table.
26
23
27
24
### Set Up
@@ -52,20 +49,23 @@ npm run package
52
49
# Builds app
53
50
npm run make
54
51
```
55
-
After running these commands you should see something like in your code editor
56
-

52
+
53
+
After running these commands you should see something like in your code editor
54
+

57
55
58
56
The app will appear within the make folder which is inside the out folder. In this photo I am making a mac os version so we have a Darwin zip file and a .dmg file but the exact outputs will vary depending on your computer. You can left click to open these in your finder and then copy them to wherever you want to use them from.
59
57
60
58
### Updating With ILR Tool
61
-
When the academic year changes and the official ILR application is updated along with the schema you will need to make at lease two adjustments to this project.
59
+
60
+
When the academic year changes and the official ILR application is updated along with the schema you will need to make at lease two adjustments to this project.
62
61
63
62
First go on the DFE website and find the schema for the current academic years XMLS. They can usually be found somewhere within [this part](https://guidance.submit-learner-data.service.gov.uk/) of the DFE website. Once you find the schema copy its content and use it to replace the content of schemafile.xsd, which is the 2024-25 version of the schema.
64
63
65
64
2nd, download the official version of the ILR application on a windows computer. Left click on it and look at the application information to find the version it should be something like 2425.1.49.0 (note there is a shorter version of this version code displayed in application when you open it you want the long version) Keep this version code on hand since the ILR tool will require it to be input along with the CVS.
66
65
67
-
### Application Usage
66
+
### Application Usage
67
+
68
68
When you open the application it asks for the version code discussed above and a CSV (more details bellow). Once these are supplied the tool will display error messages and warnings. Warnings are fine and one or two are usually produced but if there are errors you wont be able to upload to the DFE's website until they are resolved. (you will get the line in the XML where there error is to help find it) You can click a button to download this XML file to your computer and then upload it to the DFE website. I want to end this by saying how to organize your table so it produces the correct CSV files. The columns should be as follows in the exact order. If you dont have information for a row leave it blank do not put in place holder values.
69
69
70
70
Use this CVS file to organize your data
71
-
[ ILR data export(template).csv](https://github.com/user-attachments/files/19339597/ILR.data.export.template.csv)
71
+
[ ILR data export(template).csv](https://github.com/user-attachments/files/19339597/ILR.data.export.template.csv)
Copy file name to clipboardExpand all lines: docs/ErrorDecoder.md
+62-70Lines changed: 62 additions & 70 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
-
# Intro
2
-
When data is stored in the XML or errors are output by the tool they use different names than the aritable. To help clarify bellow are two lists. One of all the rows in the aritable and their numbers. The other has all the data as it is entered into the system or output as errors as well as the row number from which it is fed. By looking at these two lists you should be able to interpret errors. You can figure out what row is being referred to by looking for the airtable row name with the same number (for example PHours has number 42 the same as Planned hours (aim 1) so you can tell that is what it means). It will also help if in the future there seems to be some sort of mix up to double check things are going to the right place.
3
-
4
-
# Data as it goes into XML
1
+
# Error Decoder
5
2
3
+
When data is stored in the XML or errors are output by the tool they use different names than the aritable. To help clarify bellow are two lists. One of all the rows in the aritable and their numbers. The other has all the data as it is entered into the system or output as errors as well as the row number from which it is fed. By looking at these two lists you should be able to interpret errors. You can figure out what row is being referred to by looking for the airtable row name with the same number (for example PHours has number 42 the same as Planned hours (aim 1) so you can tell that is what it means). It will also help if in the future there seems to be some sort of mix up to double check things are going to the right place.
6
4
5
+
## Data as it goes into XML
7
6
8
7
2. ULN: index 2
9
8
3. FamilyName: index 4
@@ -19,78 +18,72 @@ When data is stored in the XML or errors are output by the tool they use differe
19
18
13. TelNo: index 12 (optional)
20
19
14. LLDDHealthProb: index 13 (converted to 1 or 9)
0 commit comments