We’re aiming to give you details of the timestamp (for those who receive it through odbc-link or xml-link) and how to access the data w/c 16 November.
You will also be able to access StarJ through the export data function in web-link. We’ll provide further information of how to do this once it’s available.
As a reminder, the data forms part of the Student Record required by the Higher Education Statistics Agency (HESA). Some providers in England also use the data to support Office for Student (OfS) returns.
HESA has confirmed there are no changes for UCAS to apply to StarJ for 2020. They have previously confirmed they do not require the HECoS codes added to the data we make available to you for their verification purposes.
For courses rolled over in 2019 in our collection tool, we brought over the JACS codes as read-only and HECoS codes became mandatory for these. New courses added for 2019 and subsequent years will only have HECoS codes, so it’s possible for reduced coverage of JACS for applicants associated with these courses.
HESA has paused their development of Data Futures, At this time, while we understand the possible value of adding HECoS codes to this data, it felt more prudent to wait until the following cycle, when HECoS can be incorporated into a fuller set of changes to the specification.
If you’ve requested a StarJ flat file, this will be available through MOVEit, the secure file transfer service. You can find more details about this in the MOVEit user guide.
You can read about the ‘Specification of the UCAS data for HESA (*J) 2020’ on our HESA return page.
If you had some placed 2020 applicants in the HEP1 and HEP2 test environments, StarJ test data is set up for you. You can access this by visiting our test and training environments page.