Brief Description
Most universities have multiple Systems of Record through which individuals are "registered" as part of the identity management system. Typical Systems of Record include a Student System, HR system for staff, Alumni system, Guest/Affiliate System, etc. The identity match or "join" process compares identity data across Systems of Record to ensure that a single identity is created, modified, and deleted for an individual, even if that individual exists in more than one System of Record simultaneously and/or moves back and forth between Systems of Record.
Generic Functional Requirements
- Multiple source data inputs including systems of record as well as identity registry
- Data normalization
- Match on multiple attributes
- Weighted attribute and source matching
- Use business rules
- Use business process management for work flow
- Pushes unmatched identities to external manual intervention
- Database, REST, ESB, LDAP for upstream / downstream connectors
Standards Support and Integration Considerations
Key Design Considerations
- Allows Push or Pull from Systems of Record
- Allows Realtime and Batch inputs
Technical Solutions
- Open Registry
- Mural
- BPMN2
Case Studies
Specific Products