Element E713 - Preference ordinal position
Description
The ordinal position of a preference in the set of preferences of an applicant as at the Reference date
Input Packets
Packets/Groups it appears in:
Showing 0 of 2.
Validations
Showing 0 of 5.
Scheduled Validations
Format
| Code category | Element (E) |
|---|---|
| Element # | 713 |
| Element Type: | String |
| Width: | 2 |
| Version Revision Date: | |
| Version: | 7.10 |
| Years version active: | 2025 |
Allowable Values
| VALUE | MEANING |
|---|---|
| 00 | Provider does not require applicants to express a preference order |
| 01 to 98 | Actual or notional ordinal position assigned to a preference |
| 99 | May be reported for course offers if the offered course is not a current preference and such data is captured |
Higher Education Providers
B2G API users
- Providers report ‘00’ or a notional Preference ordinal position if applicants are not required to express a preference order
- The Preference ordinal position (E713) must be different in each Course Preference linked to a single Application identification code (E700) for the Reporting year (E415) (unless 00 is reported)
- If only one preference is submitted against a unique value for Application identification code (E700) then the Preference ordinal position of ‘01’ should be assigned
TCSI Data Entry Users
- Only one instance of a ‘00’ notional Preference ordinal position can be reported for a unique combination of Application identification code (E700) for the Reporting year (E415)
- The Preference ordinal position (E713) must be different in each Course Preference linked to a single Application identification code (E700) for the Reporting year (E415)
- If only one preference is submitted against a unique value for Application identification code (E700) then the Preference ordinal position of ‘01’ should be assigned
If the submitter is a TAC
Provision of full details of the Preference ordinal position is required for all Preference Details and Offer Details data records.
- The Preference ordinal position (E713) must be different in each Course Preference linked to a single Application identification code (E700) for the Reporting year (E415).
- The Preference ordinal position (E713) must be different in each Course Offer linked to a single Application identification code (E700) which has the same Date offered (E705) for the Reporting year (E415). This rule does not apply to the reporting of ‘99’.
Summary
Element 713 was included as part of the University Applications and Offers data collection from 2010. There have been some modifications and updates to coding notes to this element since to help streamline documentation.
Table 1. Change control information with links to relevant versions 1
| First year version applied | Last year version applied | Version | Change | Reason for change | Notice date | Issue date |
|---|---|---|---|---|---|---|
| 2025 | Current | 7.10 | Additional Information has been updated to provide clarity about reporting '00' through the different data submission organisation types and channels (B2G API or TCSI Data entry) | To provide clarity | 25 Nov 2024 | 25 Nov 2024 |
| 2021 | 2024 | 7.00 | Incremental version number applied. | A new version number is applied to mark the transition from the Higher Education Information Management System (HEIMS) to the Tertiary Collection of Information (TCSI). | 3 Jul 2020 | 3 Jul 2020 |
| 2015 | 2020 | 6.00 | Re‑format document to conform with the department's application upgrade | Ministerial Notice document system upgrade | 22 May 2014 | 22 May 2014 |
| 2014 | 2014 | 5.00 | Applications and Offers Data Collection - Updated coding notes to include reference to TAC's Data Elements Map in the HEIMS Web Services Specification. | To clarify information | 27 Mar 2013 | 27 Mar 2013 |
| 2013 | 2013 | 4.00 | Moved coding notes from structure documents | To streamline documentation | 14 Feb 2012 | 14 Feb 2012 |
| 2012 | 2012 | 3.00 | New versioning applied to data elements | No change in requirements - Implementation of new document management system. | 11 Mar 2011 | 11 Mar 2011 |
| 2010 | 2011 | 1.00 | New element for purpose of University Applications and Offers Data collection | New Collection | 30 Nov 2009 | 05 Dec 2008 |
| Pre‑HESA: There is no earlier version of this element. | ||||||
Note 1: A version of an element can be associated with one or more reporting years. Where there are multiple versions applicable to a reporting year, only a link to the latest version is provided.
