When you have imported guardians and students, you need to build a relationship between the two. Without this relationship, the guardians will not be attached to the student profile and have no context. Have a look at this article to further understand how to give a guardian context.
Understanding legacy IDs
This is useful to understand as it is a quick and easy way to import the relationship file successfully. If you are importing from another software, then your users may have a unique legacy ID already. If not then try to create fake ones. These legacy IDs must be unique, but we suggest starting with your students at 1000, 1001, and 1002, and then doing the same for the parents with guardians 1 starting at 10000, 10001 and 10002, the guardians 2 at 20000, 20001, and 20002. So the relationship file would start by using the legacy ID of the student and then add both guardians accordingly. In the below example, the student 1000 will be attached to 2 guardians (10000 and 20000).
| Student Legacy ID | Guardian Legacy ID |
| 1000 | 10000 |
| 1000 | 20000 |
| 1001 | 10001 |
| 1001 | 10002 |
Options for relationship import
In this import, you will match the student profile to the user profile. If you do choose names, then be wary if you have a common family name in your community it may be hard to match the records as the system will not be able to proceed.
| Student (Family name, First name) | Student (Legacy ID) | Guardian (Family name, First name) | Guardian (Legacy ID) |
| Relationship type (Name or idea) | Is the main guardian (Y/N) | Is emergency contact (Y/N) | Has access (Y/N) |
| Is the invoice payer (Y/N) | Has pickup rights (Y/N) |
Comments
0 comments
Please sign in to leave a comment.