COMPASS - University of Florida

MDM Person Hub Data FAQ

What is Registry and MDM Person HUB data?

UFIT Enterprise Systems applications and technologies allow data to be integrated throughout the university and its diverse information systems. The UF Identity-Registry on the mainframe serves as a system of record for the identity attributes of UF faculty, staff, students, and many others in the UF community, and a one-stop service for updated identity and contact information for multiple applications across campus. Most of this data is self-asserted, and can include biographical/demographic data, such as name and address types, contact methods, identifiers (typically government issued), descriptors (gender, DOB, ethnicity, vet status, disability status, other), relationships, emergency contact(s), privacy choices, and affiliations.

Who is impacted by current and pending changes?

Moving from mainframe data access is an “invisible” process for students, and most staff and faculty already are using alternate means to access and manipulate data, such as through Enterprise Analytics, web services, the ESODBC warehouse, or the UF Data Lake. Staff impacted by changes in where this information is stored and how will be accessed are primarily Person Hub data authors, consumers, and data stewards who handle daily operational activities.

  • Person data authors and respective modifier systems include:
    • Student
      • Admissions (Gator360)
      • Student Records (SIS)
      • Office of Student Financial Affairs (ParentPLUS loan process)
    • Human Resources (EPAF)
    • Distance and Continuing Education (Custom - "Quick Reg")
    • UF Health
    • Business Services (Direct)
    • Housing
    • Self Service
    • IAM Functionality
      • Coordinators
      • Administrators
  • Person data consumers and subscribers include:
    • All Authors
    • University Athletic Association
    • UFAD
    • AT
    • Traffic and Parking
    • College of Liberal Arts and Sciences
    • Career Resource Center
    • Dentistry, College of Education, Forestry, Pharmacy
    • Warrington College of Business, Vet Med, Emerging Pathogens
    • Research
    • OIPR
    • PPD
    • University of Florida Foundation
    • Facilities
    • Libraries
    • Internal Audit
    • VIVO
    • PHHP
    • International Center

If I believe I am a Registry author and/or consumer, what do I need to do?

Since 2017, UFIT has been in contact with nearly all authors and consumers collectively and individually to describe upcoming changes, timelines, development, and testing efforts. We are currently reaching out to departments/colleges/divisions who utilize Registry API’s, the ODBC data warehouse, or direct mainframe access according to an audit of security roles to ensure all customers are accounted for and ready for this transition with minimal business disruption.

If you have not been contacted, and/or cannot identify the source and/or nature of your data interactions, first reach out to any related core office (i.e., Office of the University Registrar, Academic Advising, Financial Aid, Graduate School, Student Financials), or your unit’s IT staff. If they feel your interactions are related to the mainframe and have not been addressed, or suspect they are related to third party or homegrown applications that import “Person” information, such as name, GatorLink ID, and email address, contact Troy Haynes (thaynes@ufl.edu) in the UFIT Project Management Office for routing to the appropriate area.

What method(s) will you be using for future Person Hub data consumption? 

  • If you are using the ODBC:
  • Anyone who currently has access to the ODBC may continue to access it in the same way.
  • New structures will have the suffix ‘_MDM’ appearing in the new object names in ODBC QAT.
    • WH_UFDIR_PERSON (Historical view)
    • WH_UFDIR_PERSON_MDM (New MDM view)
  • ‘ _MDM’ structures are temporary and are there for testing and to familiarize you with the new structures and data changes. Once your testing is completed and the mainframe is decommissioned, you will return to using your historical view. For example:
    • Query 1
      • select * from SYSADM.WH_UFDIR_NAME --registry
      • WHERE UF_UFID = :1
      •   AND UF_ACTIVE_FLG = 'Y'
      • order by UF_TYPE_CD;
    • --Query 2
      • select * from SYSADM.WH_UFDIR_NAME_MDM  --mdm testing only
      • WHERE UF_UFID = :1
      •   AND UF_ACTIVE_FLG = 'Y'
      • order by UF_TYPE_CD;
  • It is expected that SYSADM.WH_UFDIR_NAME will update with the data from SYSADM.WH_UFDIR_NAME_MDM when we go-live. So ESODBC queries (like query 1) will reference MDM data instead of Registry.
  • Make sure you have noted the data changes, started to modify your consuming systems to accommodate these data changes, and are reviewing and testing the ‘_MDM’ structures

If you are using Person Hub REST-ful services (for customers who need real-time data regarding a Person):

  • Contact Louis Cressia, review the QuickStart guide, establish a connection, and call the services.
  • Make sure you have noted the data changes, started to modify your consuming systems to accommodate for the new web service traffic and data changes, and are reviewing and testing your changes.

If you are using Person Hub Notification Queues… This customer base for this method of consumption is small and localized (primarily authors), and UFIT is interacting with this group personally.

  • You should be familiar with the following data changes:
  • Consolidated data types, renamed fields (UF Business Name to Legal Name; Physical Address to Street Address). These changes are described in documentation at https://data.ufl.edu/data-management/
  • Many Legacy Registry type codes are changing
    • Affiliations will retain legacy type codes
    • All other have new type codes.

Many of you have moved through the discovery and development process and are either in testing or prepared to move forward smoothly after the mainframe is decommissioned.  While we believe we have a comprehensive list of authors and consumers, and are conducting personal outreach to each, we want to make sure no one has been missed. Data accessed directly from the mainframe will go stale after June 30, 2019.

Where can I read more about data and find additional resources, such as documentation and how to sign up for targeted data listservs?

 


If you have not been contacted, and/or cannot identify the source and/or nature of your data interactions, first reach out to any related core office (i.e., Office of the University Registrar, Academic Advising, Financial Aid, Graduate School, Student Financials), or your unit’s IT staff. If they feel your interactions are related to the mainframe and have not been addressed, or suspect they are related to third party or homegrown applications that import “Person” information, such as name, GatorLink ID, and email address, contact Troy Haynes (thaynes@ufl.edu) in the UFIT Project Management Office for routing to the appropriate area.