The person lifecycle defines how person objects are provisioned and managed through the UCSB Identity Service.
Person objects for "employee", "student", and "applicant" demographics are provisioned from nightly data extracts from the payroll, registration, and admissions systems, respectively. Other demographics such as extension students, visiting scholars, and emeriti are managed using our Demographic Import application (forthcoming).
All new person objects go through a reconciliation process against our existing store of person data to prevent duplicates. Those objects that don't exist or have been previously terminated are added to our person database.
Upon creation, each person object is assigned one or more affiliations as described in affiliation handling.
Once a person object has been created, their identity can be activated using our Identity Manager service. Upon activation the principal creates a UCSBnetID and password for their electronic identity, along with validating their personal information, email address, etc. Once the account has been activated, the person object is provisioned into one or more identity repositories.
All person data collected in our nightly data extracts are compared against existing records; updates to core identity attributes are merged into records appropriately. Fields that are self-editable via the Identity Editor are left unchanged.
As described in affiliation handling documentation, the affiliation values associated with each person object are deprovisioned based on criteria specific to each demographic. When a person object no longer has any active affiliations, their entry is terminated and deprovisioned from the identity repositories.