Enrich administrative profiles from SGU

2026-09-03 12:21:43 -06:00
parent d50a4d9895
commit 403132f869
12 changed files with 609 additions and 22 deletions
@@ -24,9 +24,12 @@ Directory synchronization, deployment scripts, and tests.
 No derived password is created. Passwords are not written to a database, file,
 event log, application log, command line, or response.

-For administrative accounts, profile enrichment targets the read-only incident
-overview and reads only the employee number, name, account type/status, email,
-job title, and department from their stable element IDs. Incident, calendar,
+For administrative accounts, profile enrichment first verifies the employee
+number against the incident overview, then reads the structured given names and
+surnames from `datos/personales.aspx` and the postal address from
+`datos/ubicacion.aspx` in the same authenticated session. Account type/status,
+email, job title, and department remain sourced from the incident overview.
+Birth date, identifiers, telephone, emergency-contact, incident, calendar,
 photo, and manager fields are ignored. Student enrichment targets the read-only
 student information page and reads only the matching student number, structured
 name, email, career, and postal address. The career becomes an AD title in the