The following is a rough task outline of what is required in order to implement AP Recruit at a customer campus.
# | Campus Responsible | Task Description |
1 | UCOP/UCI | Initiate project for implementing AP Recruit for customer campus |
2 | UCI | Discuss system integration, branding, and other documents with customer |
3 | Customer | Provide completed system integration worksheet and branding packet to ucrecruit-support@uci.edu |
4 | Customer | Create DNS CNAME and SSL certificate, provide to UCI |
5 | UCI | Provide initial branded AP Recruit environment (with domain & SSL) to Customer for early feedback. |
6 | Customer | Review initial branded AP Recruit environment and provide feedback to UCI |
7 | Customer | Configure Shibboleth IdP to release EPPN and other optional attributes to AP Recruit |
8 | UCI | Configure Shibboleth SP |
9 | Customer | Provide initial spreadsheet of Academic Unit Hierarchy to UCI |
10 | UCI | Import Academic Unit Hierarchy into AP Recruit |
11 | Customer | Provide any necessary updates to campus specialties, title codes, or diversity benchmark/availability data used by AP Recruit |
12 | UCI | Implement requested changes to specialties, title codes or diversity benchmark/availability data |
13 | Customer | Provide SSH public key for data feed transfers |
14 | UCI | Authorize SSH public key and establish automated data feed imports |
15 | Customer | Automate delivery of data feeds to AP Recruit using SSH |
16 | UCI | Provide access control RESTful API credentials to customer (optional) |
17 | Customer | Automate update of access control data using RESTful API (optional) |
18 | UCI | Create remaining AP Recruit environments (test, training) |
19 | Customer | Automate delivery of data to additional AP Recruit environments |
20 | UCI | Provide AP Recruit training webinar (can happen at any time) |
21 | All | Final test |
22 | All | Revise/approve AP Recruit Service Level Agreement |
23 | Customer | Launch AP Recruit, announce, begin training, etc… |
24 | All | Close out project |