Faculty Search Release Notes: 2018.08.01
We made a few small phrasing updates in our built-in form for applicant self-reporting of Equal Employment Opportunity (EEO) information. These updates keep the form consistent with recent changes to the language prescribed in the federal EEO Commission’s Voluntary Self-Identification of Disability Form (form CC-305, OMB Control Number 1250-0005, expires 1/31/2020).
- Updated expiration date to: “Expires 1/31/2020"
- Added “i” to the Reasonable accommodation notice to connect as additive to the previous statement
- New order for the disability options are as follows:
- Cerebral palsy
- Muscular dystrophy
- Bipolar disorder
- Major depression
- Multiple sclerosis (MS)
- Missing limbs or partially missing limbs
- Post-traumatic stress disorder (PTSD)
- Obsessive compulsive disorder
- Impairments requiring the use of a wheelchair
- Intellectual disability (previously called mental retardation)
Administrators can now create, record, and report on disposition codes from a new “Disposition Codes” tab on the Administration page of the program.
Disposition codes are short explanations of why an applicant did not make it to the next step of the hiring process. Disposition codes provide users with a responsible, liability-preventing form of documentation of the hiring process in order to keep a record of the stated reasons why an individual job candidate was removed from consideration.
Up till now, Faculty Search clients have used application statuses to record disposition codes. This new feature will make recording and reporting on disposition codes easier, more accurate, and intentional.
Why don’t I see Disposition codes? If disposition codes are turned off or not created by an institution, the user will NOT see related content such as disposition code labels, buttons, and columns etc.
- Disposition codes are meant to work in conjunction with application statuses, rather than replace them outright.
- Application statuses are meant to cover where a given applicant is in the committee’s process (e.g. Long List, Short List). Disposition codes, on the other hand, are intended to document why a given applicant did not move any further in the process. In many situations, these fields will be reported on together to support end of search reporting.
- Using disposition codes for each applicant will help compliance reporting at the completion of a search. In many cases, it will help meet requirements for each applicant to have a valid code assigned to them.
- Disposition codes are created on the “Disposition Codes” tab of the Administration page
- When user edits the name of a code, the change will propagate to all instances where that code is used
- When user deletes a code, the code will not be available for future use, but will remain applied to any applicants who had it applied in an open or closed position, and it will remain applied to those applicants in reporting
- The codes Admins create will be displayed in alphabetical order
- If codes have been turned on for an institution, all units will have access to these disposition codes.
- User can assign one or more applicants with one disposition code
- Faculty Search CM or Admin at an institution that uses disposition codes, can assign disposition codes to an applicant from the applicant profile page. User will see a field labeled "Disposition Code" on the page, and an option to add.
- CM or Admin can also assign codes to multiple applications at once on the applications page.
CM or Admin in Search can create an Applications Report by selecting to add a Disposition Code column for reports on the applications list.
Interfolio Faculty Search now keeps an automatic log of the user actions and events that take place around each position in the program in order to provide users with a clear record of when certain changes were made and by whom.
The position activity log for any given position is visible only to users with Administrator rights over that position (admins and committee menagers). The position activity log plays a similar function to the case activity log in RPT. It is separate from the existing system logs under Reports.
The user will see a log with entries indicating changes or activity. This list of events can be searched and sorted by date or event. A link to “View Message” concerning the event will appear where applicable.
Availability and limitations:
- You can access the position activity log from within the individual position.
- Currently, position activity log data is just for the individual positionnot available in aggregate (such as through Reports).
The events logged will initially include:
- Position Status Changes: Text: [First Name] [Last Name] [(E-mail address)] updated the position status from [Old Status Value] to [New Status Value].
- Committee additions: (only ad-hoc additions here) Text: user_name (user_email) added user_name (user_email) as a committee member for this position.
- Committee Removals: Text: user_name (user_email) removed user_name (user_email) as a committee member for this position.
- Position Workflow step change when the position is sent forward (approved) or backward (rejected): Text: approver_name (approver_email) moved the position from Step X of Y: step-name to Step Z of Y: step-name.
- Position published: Text: If a user published: user_name (user_email) published the position. If interfolio auto-published, we should say: Interfolio automatically published the position.
- Position Open Date: Text: This position is open and accepting new applications.
- Position Close Date: Text: The close date for this position has passed, and the position is no longer accepting new applications.
Interested applicants for a position who are viewing a landing page on Interfolio will again see the full unit hierarchy displayed on the page in a clear and legible font.