ECU Data Retreat 2019

Published May 05, 2022 by
Filed under:

ECU 2019 Data Retreat

  • Focus topic: Undergraduate Admissions data
  • Planning committee: Lee Cline, James Coker, Greg Harris, Beverly King, Heidi Puckett, Doug Stanley, Scotty Stroup, Ying Zhou
  • Date: February 18, 2019
  • Location: Main Campus Student Center, Room 125
  • Keynote speaker: Ron Mitchelson
  • Sample guiding questions:
    • How does your office identify new incoming undergraduate students (first-time or transfer)?
    • Do you ever encounter difficulty in determining which students have been admitted and/or enrolled (registered)? (For example, there is an “enrolled” indicator on three different ODS tables which do not always match.)
    • Does your office need/use any data on admitted and/or enrolled (registered) students to perform its functions? If so, what data errors/omissions do you encounter?
    • Does your office generate any data on admitted and/or enrolled (registered) students to perform its functions?
      • If so, how are these data stored and how timely are they updated?
      • Are the data imported into Banner and/or ECU’s data warehouse? If not, would you recommend additional data elements imported to Banner and/or ECU’s data warehouse, so they can be used by other functional offices?
    • Are there any special circumstances or variables other offices should consider when reporting your data? For example, the undergraduate admissions office looks at net admits and excludes withdrawals. This may alter how other offices report current and/or previous year data.
    • What recommendations do you have to improve data consistency, completeness, accuracy, or timeliness?
    • What recommendations do you have to improve communication between offices charged with data input, extraction, or analysis?
    • Is there anything about student admissions data processing that you would like to know more about?
  • Expected outcomes:
    • Come up with uniform measuring point or identify multiple measuring points used for tracking students
    • Determine how to get inquiry/prospect information into the data warehouse so can be accessed for reporting purposes
    • Begin to think about how to capture data on not only campus visit registration but also campus visit attendance (e.g., orientation), enrollment deposit data, housing (deposit) data, communication with students (What we are going to capture and how)
    • Think about data quality for data already being captured; across units, are we providing the right information in dashboards/reports?
    • Determine unit responsible for different reporting needs
    • Investigate frequency of data feeds/entry and when captured; also, alignment of time periods/captures
      • Pirate ID
      • Deposits
      • Pier holds
  • Determine if a data flow/management group (e.g., BSUG) get together monthly to review data
  • Determine which (how many) follow-up meetings are needed on related topics
  • General areas identified for further action:
    • Orientation attendance tracking efficiencies/automation
    • Orientation intended major collection/changes
    • Collection of campus visit data
    • Collecting/recording student gender
    • $0.00 enrollment deposit waivers/exemptions/$0.00 housing deposit waivers/exemptions
    • Recruiter data elements needed for reporting not currently pushed to Banner and/or streamed to ODS
    • Institution-wide reporting and selection criteria standards