UO Libraries Supervisors use this service to request or update permissions and access to technology used by Libraries employees & student workers.
Note: Please submit your requests 2 weeks prior to start date. If submitted later than this, be aware that we may not be able to fulfill your requests by their start/end date
How to Submit Technology Onboarding Request
Hiring Supervisor
To onboard a new employee, please gather the information listed below, and then click Onboard Employee (top right of the page).
- Employee Information
- New employee's name (required)
- DuckID (required)
- 95 Number (required)
- Employee supervisor name & email (required)
- Title of employee position
- Position number
- Work unit/Division
- Employment status (Full Time, Part Time, Limited Duration, Temporary, Post Retirement)
- Employee role (faculty, OA, classified staff, GE, intern, student)
- Start Date (and end date if Limited Duration/contract)
- Office building, room, and jack number (if required)
- Does the employee need computer equipment: To purchase new equipment, consult USS Device and Hardware standards and use that information to fill out your request for equipment here as soon as possible to ensure equipment is on site prior to the new employees start date.
- Does the employee require access to the following applications or services, and if so, what roles will they need (if applicable):
- Alma (which roles? Like whom?)
- Alma Analytics
- ArcGIS
- ArchiveIt
- ArchiveSpace
- Aviary
- Banner/AppWorx
- Concur approvals chain
- Connexion (OCLC)
- Email lists (Please list)
- FileZilla
- Key(s) (Specify which)
- LibApps: LibAnswers
- LibApps: LibCal
|
- LibApps: LibGuides
- LibApps: LibInsight
- LibApps: LibWizard
- LibFiles file share folders (Please list)
- LibWeb Admin
- MarcEdit
- Melior Fonts
- MS Project
- MS Visio
- OCLC role/app
- Oregon Digital admin
- Outlook calendars (Specify)
|
- PaperCut public printer admin
- Phone (Teams) number
- Preservica
- Primo Admin/roles
- ScholarsBank Admin
- Teams
- TDX access to submit tickets to Libraries queues
- TDNext tech access (respond to tickets - Facilities/Core Systems/SCUA/Incident Forms)
- Zebraprinter/SpineOmatic
- Other
|
There will be an open text box for special notes.
Note: Supervisors must add the staff member to Libraries Teams, Sharepoint sites, and Email lists.
Note: some access may take longer or is dependent on other permissions being granted
The Workflow
Once the ticket has been submitted, a set of tasks is created based on the selections provided by the hiring manager. If the selections are "no" or "none," then tasks are NOT created for the responsible group. Tasks and responsible people/groups will only be notified if the hiring manager selects the relevant options.
The tasks to provision the new employee into a system are NOT generated until PAST Human Resources provides and/or verifies the employee's position number, 95 number, and DuckID.
If a group/person is assigned a task they will be notified of the task, and it is expected that each task is completed within five business days. Once all the tasks are complete, the responsible group, the hiring manager, and PAST Human Resources are notified. Alma/Primo VE access depend on Banner being updated with all needed details. If access is needed sooner, please discuss with Core Systems Librarian.
ADI is responsible for the ticket and will ensure the onboarding information is provided and accurate and that people/groups responsible for tasks complete them on time.
Availability and Access
UO Library Supervisors, including Student employee supervisors, as well as ADI staff and USSAS staff
Note: Your request will be forwarded to relevant library and USSAS technology staff, and you will be contacted if there are questions. Thank you.
Questions
If you have any additional questions, please contact Margaret Alexander.
[back to top]