, but this code // executes before the first paint, when

ÃÛÌÒapp

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); VSP Application Instructions Faculty Development & Research | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

VSP Application Instructions

An application must be completed by the ÃÛÌÒapp contact person and submitted to the dean for faculty development and research initiatives via workday. To complete an application, go to workday and type "create request" in the search bar, then select the visiting scholar application. For a job aid to help you, go The dean will review the submitted information and determine what further steps must be taken.

Please gather the following information and review the ÃÛÌÒapp contact person's responsibilities,Ìýbefore filling out the application:

Visiting Scholar personal information required

  • Complete curriculum vitae. Be sure to include applicant's full name and title, complete mailing address, telephone #, email address, currently held position (graduate student, research associate, pastor, professor), field of specialization, educational degree, and most recent degree and from which institution.
  • Letter of interest with a brief description of the work the applicant will pursue at ÃÛÌÒapp.
  • Letter of reference from someone in the applicant's field of study.
  • Applicant’s nationality.
  • If non-U.S. citizen, date of last visit to the U.S.
  • Does the applicant have legal documents (current passport, Social Security number, visa, driver's license)?
  • Will the applicant have personal income or other financial resources sufficient to cover all expected living expenses and travel?
  • Does the applicant expect to be accompanied by family members during the visit?
  • Health coverage is required. What kind of health insurance policy will cover the applicant (and family) during their visit?
  • If non-U.S. applicant with school-aged children who will be attending local schools, has applicant checked with the schools to determine the school's student visa preferences?

Further information required regarding the proposed visit

  • Name of the sponsoring ÃÛÌÒapp department, center, or institute.
  • Name and title of the ÃÛÌÒapp contact (within the sponsoring department, center, or institute).
  • Letter of support from the sponsoring department, center, or institute.
  • Proposed time frame for the visit (start and end dates).
  • If applicant is a non-US citizen, what visa arrangements are planned?
  • Does the ÃÛÌÒapp sponsor expect the applicant to be paid through ÃÛÌÒapp (wages, stipends, honoraria, or salary)? If paying a non-U.S. applicant, J-visa or visa waiver must be in place.
  • Does the ÃÛÌÒapp sponsor expect to reimburse the applicant for any expenses?
  • Does the ÃÛÌÒapp sponsor expect to provide the applicant with an office on campus?
  • Does the ÃÛÌÒapp contact expect to assist the applicant with finding housing, transportation, schools for children, etc? (NOTE: school tuition credits are not available for non-employees.)
  • What level of ÃÛÌÒapp IT permissions will be requested for this visitor?
  • Has the ÃÛÌÒapp contact previewed the entire visiting scholar process and agreed to these responsibilities?

Questions? Please contact the Office of the Dean for Faculty Development and Research Initiatives.