What
is the student profile table?
The Student Profile table
was conceived as a one time
snapshot of students who
enrolled for a particular
semester. On the 21st day,
data for each student is
frozen and except for ENROLLED_HOURS
the data values will not
change . The Student Profile
is the table that the WAREHOUSE
census database looks at
to provide the ASU_Student_Census
table. The WAREHOUSE database
is a "view" of
the Student Profile. It
therefore has approximately
the same data elements in
it that you learned in the
WAREHOUSE database class.
There is one record in this
table per student per semester.
What
is the timing of the table?
The Student Profile table
is generated weekly starting
after pre registration for
the semester. Most of its
data elements are frozen
on the 21st day. After it
is frozen, Institutional
Analysis adjusts it so it
matches the Registrars official
reports. Only ENROLLED_HOURS
and the RECORD_ON_SIS flag
will be updated weekly after
the 21st day. If a student
registers after the 21st
day a new record is added
for that student. If a student
ID changes, the RECORD_ON_SIS
flag for the original ID
is set to N and a new record
is added under the new ID.
All records that are added
after the 21st day have
their FLAG_21ST_DAY set
to N. ENROLLED_HOURS are
updated weekly for two years
after the semester is completed.
So if someone withdraws
after the fact the enrolled
hours would be updated.
Why
would you use it?
The most popular reason
to use the Student Profile
table is to obtain a student's
minority status code. This
code which looks at a students
visa, citizenship, and ethnicity
has only been provided for
the census data. It exists
no where else in the STUDENT
database. Note if the student
changes their ethnicity,
visa, or citizenship in
mid semester, it will not
show the change here. But
at least you can get what
they were on the 21st day.
If you don't limit any of
the flags at the bottom
of the table you will get
a record for every student
who enrolled at anytime
during the semester.
The
other thing this table is
good for is finding students
who were here last semester.
The Registered Student table
is good for students who
are here this semester but
what if you want to send
something to students who
were here last Spring. Because
students continue to be
added to this table even
after the 21st day, the
Student Profile table is
a good place to get affiliate
ID's that you can match
to Student Mailing Labels
tables.
Yet
another useful feature of
the Student Profile table
is to give you a quickie
look over time at an individual
student. Say a student has
been here six semesters.
You can limit AFFILIATE_ID
to this student's ID and
put COLLEGE_OR_DIVISION_CODE,
DEGREE, MAJOR, CUMULATIVE_GPA,
CUMULATIVE_TRANSFER_HOURS
and more on the request
line. You can quickly see
if they are changing majors,
if they are picking up transfer
hours and they go, if their
GPA is going up or down.
Why
would you NOT want to use
it?
If you want data more current
than the 21st day on your
students, don't get it from
Student Profile. For instance,
although a students degree
major may be 04 0000 (non
degree seeking undergrad)
on the 21st day, by the
next week it may change
to Psychology. You could
get the most recent degree
major code in the Registered
Student table.
What
should you watch out for?
There are a number of flags
at the bottom of the table
that are tricky. If you
want to duplicate the enrollments
in the WAREHOUSE census
database, limit the CENSUS_ENROLLMENT_FLAG
to Y. If you want to see
how many students showed
up after the 21st day limit
the FLAG_21ST_DAY to N.