Sourced open data and public reuse context
Source records, publishing, and corrections: Workday Student
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Translate the institutional setting into academic units, periods, programs of study, course sections, student cohorts, eligibility rules, and business processes. Ask how the design affects records and student service. A public-data service needs named owners for source records, publication rules, refresh timing, metadata, legal review, corrections, and downstream applications that the publishing team does not control.
Evidence to request: Use an applicant-to-enrollment exercise and require academic, process, eligibility, security, billing, and reporting decisions. Identify each source system, dataset owner, publication test, refresh schedule, restricted field, correction route, consumer, and support handoff connected to the role.
Sourced enterprise applications and infrastructure context
Shared services across departments: Workday Student
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Set boundaries among Workday Student, HCM, Financials, identity, learning systems, federal or provincial aid services, payment tools, and campus applications. Require a comparable integration example. A shared service may support departments with separate case records, approvals, retention rules, operating hours, budgets, and legacy systems while one central team owns infrastructure and support.
Evidence to request: Review a campus interface or student-record defect with the affected population, diagnosis, correction, replay, and validation. Name the departments, user groups, service owner, application and hosting boundary, approval path, maintenance window, legacy connections, and acceptance evidence.
Sourced cybersecurity and geographic data context
Identity, location, and disclosure boundaries: Workday Student
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Define conversion, testing, cutover, and term-support ownership. Candidates should cover applicants, students, curricula, enrollments, balances, aid records, security, reports, exceptions, and reconciliation. Constituent and location records can cross identity, field access, map layers, integrations, operational use, audit logs, and public-disclosure rules that require separate review owners.
Evidence to request: Ask for a term conversion or registration cycle the consultant owned, including record validation, role testing, exceptions, communication, and acceptance. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.