PEIMS Data Standards app_pet_field

A PET event is an individual student’s enrollment to or withdrawal from a CAMPUS-ID-OF- ENROLLMENT tightly coupled with the date the enrollment or withdrawal took place. Although the districts are provided with a manual capability to create a PET event, most districts submit their enrollment and withdrawal events to TEA in an XML-based extract file. The file is referred to as an ‘extract’ file because it is created through a vendor-supported process that extracts event information from a district’s student information system. The extracted data are stored in an XML-based file consistent with the PET XML Schema Definition (XSD). Prior to transferring the PET Extract File to TEA, the system verifies the structure of the file against the PET XSD. In addition, the system verifies the contents of the file against the declared data types and restrictions defined for each element in the PET XSD for each simple type element. The data types and restrictions defined with the PET XSD constitute the PET Field Edits.

Restrictions control acceptable values for XML elements. Restrictions on XML elements are called facets. The following table provides a listing of restrictions used in the PET XSD. In combination with an element’s declared data type, restrictions enable the XSD validation process not only to validate the structure of the XML file but also to validate the data values contained within the file against its XML schema definition. Every simple type element within the PET XSD has a restriction that limits the domain of acceptable values. PET Extract Files improperly structured or containing unacceptable values will not transfer to the TEA for further processing.

Available XSD Restrictions
Restriction	Description
minInclusive	Specifies the lower bounds for numeric values (the value must be greater than or equal to this value)
maxInclusive	Specifies the upper bounds for numeric values (the value must be less than or equal to this value)
minLength	Specifies the minimum number of characters or list items allowed (the value must be equal to or greater than zero)
maxLength	Specifies the maximum number of characters or list items allowed (the value must be equal to or greater than zero)
pattern	Defines the exact sequence of characters that are acceptable
whiteSpace	Specifies how white space (line feeds, tabs, spaces, and carriage returns) is handled

After a PET Extract File is successfully validated against the PET XSD and transferred to TEA, the system places the file in a queue for further processing. As resources are available, the file is opened and the PET Records in the file are validated and loaded. As illustrated below, the PET validation and load process is divided into two logical stages:

PET Context Edits are used in both stages. If the system does not find an exact match for the student ID and major demographics in the TSDS Unique ID System, an error will result. If the system does find an exact match in the TSDS Unique ID System, the PET events are validated against appropriate PET Context Edits before being loaded into the PET Event table. Each of the PET Context Edits is presented in the next section.

Each PET Context Edit is traced to its associated PEIMS Edit Number, if applicable. A PET Context Edit is not required for any of the following data elements because data quality is assured through the XSD validation process:

PET Context Edits have been defined for BirthDate, SexCode, GenerationCode, AmericanIndianAlaskanNativeCd, AsianCd, BlackAfricanAmericanCd, NativeHawaiianPacificIslandCd, WhiteCd, and HispanicLatinoCd in support of the PET Student Add process. See “PET Edits” section.

PET Context Edits
PET EDIT #	Data Element(s)	Edit Rule Text	PEIMS Edit #
P001	StudentID	The first character of StudentID must be “S” or “0”-“8”.	10001
P002	StudentID	Each character of StudentID must not be the same number.	10002
P003	StudentID	The first three characters of StudentID must not be “000”.	10003
P004	StudentID	If first character of StudentID is not an “S”, the fourth and fifth characters must not be “00”.	10005
P005	StudentID	If first character of StudentID is not an “S”, the last four characters must not be “0000”.	10006
P006	FirstName, MiddleName, LastName	Former edit deleted.
P007	FirstName, MiddleName, LastName	The FirstName, MiddleName, and/or LastName must only contain the following characters: A-Z 0-9 Apostrophe Hyphen Space character	10015
P008	FirstName, MiddleName, LastName	Name must not contain only apostrophes.	10015
P009	FirstName, MiddleName, LastName	Name must not contain only hyphens.	10015
P010	FirstName, LastName	Name must not contain only spaces.	10015
P011	MiddleName	Former edit deleted
P012	FirstName, MiddleName, LastName	The FirstName, MiddleName, and/or LastName must not contain only “0” – “9”.	10017
P013	DistrictID	The DistrictID contained within the CampusIDofEnrollment must match an entry registered with the TEA.	01001
P014	CampusIDof Enrollment	The first six characters of the CampusIDofEnrollment must be the same as the ID of the district transferring the PET Extract File.	11011 40028 40707 40807
P015	CampusIDof Enrollment	CampusIDofEnrollment must match an entry registered with the TEA as an active instructional campus and is not a budgeted campus.	11012 40002 40704 40808
P018	CampusIDof Enrollment	When creating or maintaining a PET Event, the first six characters of the CampusIDof Enrollment must match the district-level user’s Agent ID.	NA
P019	CampusIDof Enrollment	When creating or maintaining a PET Event, the CampusIDofEnrollment must match the campus-level user’s Agent ID.	NA
P020	EnrollDate	When creating or maintaining a PET Event, the EnrollDate must fall within the date range defined for the PET School Year in context. In general, the school year begins on June 1 and extends through August 31 of the following year.	NA
P021	EnrollDate	The EnrollDate must not be greater than the PET file submission date.	NA
P022	WithdrawDate	When creating or maintaining a PET Event, if a prior enrollment record for the CampusIDofEnrollment doesn’t exist, the withdrawal event is invalid.	NA
P023	WithdrawDate	When creating or maintaining a PET Event, the WithdrawDate must fall within the date range defined for the PET School Year in context. In general, the school year begins on June 1 and extends through August 31 of the following year.	NA
P024	WithdrawDate	The WithdrawDate must not be greater than the PET file submission date.	NA
P025	LocalID	When creating or maintaining a PET Event, the Local ID must be consistent with the PEIMS Data Standards’ Name Field pattern. In addition to the space character, this pattern allows any of the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 ~ ! @ # $ % ^ & * ( ) - _ + = : ; " ' , . / < > ?	NA
P026	CampusData	Two or more CampusData elements for the same CampusIDofEnrollment for one Student are invalid. Note: All the PET Events for one Student at a given CampusIDofEnrollment should be clustered together in one or more PETEventSet elements.	NA
P027	PETEventSet	Two or more incomplete PETEventSets for the same CampusIDofEnrollment for one Student are invalid.	NA
P028	EnrollDate / WithdrawDate	Two or more equal PET Event dates for the same CampusIDofEnrollment for one Student in two different PET Event Sets are invalid.	NA
P029	BirthDate	BirthDate must be a valid date.	10141
P030	BirthDate	BirthDate must be less than the enrollment date.	NA
P031	AmericanIndianAlaskanNativeCd, AsianCd, BlackAfricanAmericanCd, NativeHawaiianPacificIslandCd, or WhiteCd	AmericanIndianAlaskanNativeCd, AsianCd, BlackAfricanAmericanCd, NativeHawaiianPacificIslandCd, or WhiteCd must be ‘1’.	1011M

For assistance with the PEIMS Data Standards contact the PEIMS Office at PeimsCustomerSupport@tea.state.tx.us

This version of the PEIMS Data Standards is a programmatically converted HTML version of the PEIMS Data Standards. It is intended as a job aid to facilitate navigation of the PEIMS Data Standards documentation and should not be used to submit PEIMS data or to reach final conclusions about individual public schools. All of the information provided is reviewed for accuracy and reliability; however, TEA assumes no responsibility for any errors appearing in the HTML version of the PEIMS Data Standards.