Forum topic

3 posts / 0 new
Last post
Robert Rae
Last seen: 3 weeks 1 day ago
Joined: 08/20/2019 - 16:32
New Report! HESA Aggregate Offshore Report

Folks,

Ah, the sweet summer air, the warm breeze, and the gentle tug of regulatory changes on the horizon. Yes, it's the time of year when we take stock of our regulatory reporting requirements and try to figure out how the system can help us.

You guys have very deftly managed our current HESA AP Report mechanism, and that's been incredibly useful. Now, it seems we have a secondary, thankfully small, report to submit in the same vein - the Aggregate Offshore Report.

The coverage for this report is: all students on a programme of study who will not spend 8 consecutive weeks in the UK during their programme.

The structure for this report is:

--
Provider:

RECID - Record type indicator (static field)
UKPRN - UK Provider Reference Number (static field)

Provider > Provision:

COUNTRY - Country of activity (where are the students based)
LEVEL - Level of provision (bachelor, masters, doctorate, etc)
HEADCOUNT - Number of students (how many students)
HEADCOUNTDS - Number of students dormant (how many students still registered but undertaking no study in the reporting year)
HEADCOUNTSCS - Number of students continuing study (how many students will go on to study in the next year)
HEADCOUNTSSC - Number of students successfully completed (how many students succesfully completed a programme this year)
HEADCOUNTSW - Number of students withdrawn (how many students fully withdrew from a programme this year)
INSTCAMP - Providers own campus identifier (an identifier for the area - we will likely use the country codes for this)
TYPE - Type of activity (static field)

--

The report is XML, and I will post the scheme below. Further information and tool can be found on the HESA website.

Thankfully, all this information is already held in GNECsis, but we will need a way of indicating on a Student's profile that they should be included in the AOR report. My initial thought would be a tick box on their Student Degree Track entity, because I don't think there is an easy and reliable way to discern this automatically from existing data. 

After they are identified, it would be a case of assessing the fields based on existing data. Essentially, it appears we will need one of these Provider>Provision entities for every country in which we have students resident on our MA programme. So, the report might read:

19052
10004538

US
M
15
1
5
8
1
US
03

CN
M
9
1
5
2
1
CN
03

And continue on with as many blocks as we have students in different countries. Students from the same country would need to be aggregated into one block - the top block here, for example, would contain the collated information for all students based on the US.

The rest of the information should be easily drawn from the student profile

HEADCOUNTDS - from the NOTACT field
HEADCOUNTSCS - those without an instance end date
HEADCOUNTSSC - those with an instance end date and Reason for Ending instance of succesful completion
HEADCOUNTSW - those with an instance end date and a Reason for Ending indicating withdrawal.

--

I'm sure we'll want to chat through this a bit, but I hope it won't be too hard to accomplish! Thanks for your help.

--

Scheme:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:include schemaLocation="C19052DataTypes.xsd" />
  <xs:element name="COUNTRY" type="COUNTRYCodeType" />
  <xs:element name="HEADCOUNT">
    <xs:simpleType>
      <xs:restriction base="xs:positiveInteger">
        <xs:totalDigits value="6" />
      </xs:restriction>
    </xs:simpleType>
  </xs:element>
  <xs:element name="HEADCOUNTDS">
    <xs:simpleType>
      <xs:restriction base="xs:integer">
        <xs:totalDigits value="6" />
      </xs:restriction>
    </xs:simpleType>
  </xs:element>
  <xs:element name="HEADCOUNTSCS">
    <xs:simpleType>
      <xs:restriction base="xs:integer">
        <xs:totalDigits value="6" />
      </xs:restriction>
    </xs:simpleType>
  </xs:element>
  <xs:element name="HEADCOUNTSSC">
    <xs:simpleType>
      <xs:restriction base="xs:integer">
        <xs:totalDigits value="6" />
      </xs:restriction>
    </xs:simpleType>
  </xs:element>
  <xs:element name="HEADCOUNTSW">
    <xs:simpleType>
      <xs:restriction base="xs:integer">
        <xs:totalDigits value="6" />
      </xs:restriction>
    </xs:simpleType>
  </xs:element>
  <xs:element name="INSTCAMP" type="INSTCAMPType" />
  <xs:element name="LEVEL" type="LEVELCodeType" />
  <xs:element name="RECID" type="RECIDCodeType" />
  <xs:element name="TYPE" type="TYPECodeType" />
  <xs:element name="UKPRN" type="UKPRNType" />
  <xs:element name="StudentRecord">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="Provider" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
    </xs:complexType>
  </xs:element>
  <xs:element name="Provider">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="UKPRN" minOccurs="1" maxOccurs="1" />
        <xs:element ref="RECID" minOccurs="1" maxOccurs="1" />
        <xs:element ref="Provision" minOccurs="1" maxOccurs="unbounded" />
      </xs:sequence>
    </xs:complexType>
  </xs:element>
  <xs:element name="Provision">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="COUNTRY" minOccurs="1" maxOccurs="1" />
        <xs:element ref="HEADCOUNT" minOccurs="0" maxOccurs="1" />
        <xs:element ref="HEADCOUNTDS" minOccurs="0" maxOccurs="1" />
        <xs:element ref="HEADCOUNTSCS" minOccurs="0" maxOccurs="1" />
        <xs:element ref="HEADCOUNTSSC" minOccurs="0" maxOccurs="1" />
        <xs:element ref="HEADCOUNTSW" minOccurs="0" maxOccurs="1" />
        <xs:element ref="INSTCAMP" minOccurs="0" maxOccurs="1" />
        <xs:element ref="LEVEL" minOccurs="1" maxOccurs="1" />
        <xs:element ref="TYPE" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

 

Status: 
Resolved
No votes yet
kbible
Last seen: 19 min 50 sec ago
Joined: 01/22/2019 - 10:07
Thanks for letting us know. 

Thanks for letting us know.  I have added a task for Alan to take a look

No votes yet

Senior Software Developer
Global Ministry Center - Church of the Nazarene

kbible
Last seen: 19 min 50 sec ago
Joined: 01/22/2019 - 10:07
Version 2.57

This was included in version 2.57.

No votes yet

Senior Software Developer
Global Ministry Center - Church of the Nazarene