For standardizing UCPath attributes for IDM/UCTrust use
As part of UCPath project, Campus IDM systems will get real time Person Job information from UCPath Central. Person Job information contains multiple data elements and attributes and campuses store this information in their IDM Data Store for asserting Single-Sign On applications. Some of these attributes can be directly mapped to already defined UCTrust identity attributes and some are not. For the attributes which are not mapped need come up with common definition, standardize and assign URN OID’s for IDM/UCTrust use.
1. Map UCPath/IDM data elements to standard inetOrgPerson or eduPerson or ucTrust objectclass schema and attribute
Example:
2. How to assert multi valued data elements
Example:
3. Determine which UCPath/IDM data elements are to be supported UC-wide.
4. Derivation/calculation logic for data. This is relevant for the attributes which are effective dated, and/or has effective status.
5. What to do with future effective dated rows? If a Person Job is effective in future date then should we include / exclude the attribute?
UCPath Attribute definition - UCTrust recommendations
UCPath Attribute definition - UCPath-IDM workgroup recommendations
UCPath PersonJob (I-280 interface) Data Element Analysis (summarized meeting notes)
Supervisor Determination in PS/HCM