Example Graduate Education Manager user sync file

In order to allow for the most effective User sync files processing, files have to be provided in a structure similar to the example below.

User sync files should be structured as JSON or XML with a top level list element containing one record per user.

[
    {
        "username": "js991",
        "nameFirst": "Jane",
        "nameLast": "Smith",
        "email": "jsmith@example.org",
        "orgUnit": "W38222",
        "category": "student",
        "startDate": "2018-04-02",
        "mode": "FT",
        "status": "active",
        "visa": "T4",
        "programme": "phd",
        "thesisTitle": "Customs in medieval ...",
        "supervisors": [
            {
                "username": "jb124",
                "role": "MAIN"
            },
            {
                "username": "mw281",
                "role": "COSUP1"
            },
            {
                "username": "is829",
                "role": "COSUP2"
            }
        ]
    },
    {
        "username": "jb124",
        "nameFirst": "Joe",
        "nameMiddle": "X",
        "nameLast": "Bloggs",
        "email": "jb@example.org",
        "orgUnit": "E8217",
        "category": "researcher"
    }
]

Organisational unit and category should use the codes in your systems, and we’ll map them using the mappings and organisational structure you provide.

You can name the fields to match the names in your systems, which may assist you in working with the sync.