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

°ÄÃÅÁùºÏ²Ê¿ª½±¼Ç¼×ÊÁÏ

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); })(); Calvin Contact Person Responsibilities | °ÄÃÅÁùºÏ²Ê¿ª½±¼Ç¼×ÊÁÏ

°ÄÃÅÁùºÏ²Ê¿ª½±¼Ç¼×ÊÁÏ

Skip to main content

Calvin Contact Person Responsibilities

After Approval but before Arrival

Plan early:ÌýFor non-U.S. citizens, applications must be submitted at least six months before the visit begins.Ìý U.S. citizen applications must be submitted at least three months before their proposed arrival date.Ìý All materials need to be received by the dean for faculty development from the nominating office or department with sufficient lead time. Go to "application instructions" if you have not yet answered all of the initial questions.

°Õ³ó±ðÌýCalvin contactÌýis responsible for all visiting scholar arrangements, including those related to the following:

  • Hold initial conversation with the candidate. ReviewÌýapplication instructions. Complete and submit your request in workday. Remember to include the applicant's CV, letter of interest/project description, and letter of support from the sponsor.
  • If visitor is a non-US citizen, the contact person must coordinate the visa setup withÌýhuman resources and the Provost Office. This will include assigning a Calvin ID# and arranging for faculty privileges, which will include picture ID, library, and fieldhouse access.
  • If no visas or salaries are involved, the Calvin contact can submit theÌýapplication in workday.ÌýAfter approval is complete, the visitor will be contacted via email with information to receive a Calvin ID# for the visitor and/or their spouse (the spouse will need a separate ID if they would like to use Spoelhof Fieldhouse facilities).
  • Office space: Work with your department chair/academic deans to plan for visitor office space.
  • Keys andÌýbuilding accessÌýcan be coordinated throughÌý.
  • Proof of health insurance (document in English meeting DOS standards) is required upon entry into the United States for non-US citizens. Information on obtaining health insurance can be foundÌýhere.
  • Assist applicant in findingÌýhousingÌýand furnishings. If no furnished housing is available, the visiting scholar is responsible for supplying all of their own furnishings.
  • If visitor's children will be attending school, coordinateÌýschool enrollment information.
  • Coordinate flight and welcome at airport.
After Arrival
  • Arrange meeting withÌýhuman resourcesÌý²¹²Ô»åÌýpayroll: For non-US visitors, the department contact and visitor are required by the Department of State to meet withÌýhuman resourcesÌýwithin five days of arriving in the countryÌýfor an orientation and review of visitor's health insurance documents.ÌýPlease note that visiting scholars should plan to come directly to Calvin from their home country.
  • Provide visitor web link toÌýVisiting Scholar Resource page.
  • Assist visitor in obtaining aÌýsocial security numberÌýif they will be paid. They can apply for their card 10 days after arriving. If they apply too soon, it will be rejected.
  • Assist visitor in obtaining aÌýdriver's license, if needed.
  • If needed, assist visitor in obtaining Calvin parking permit through Campus Safety, provide initial orientation, including picture ID(s), tour of library and fieldhouse, introduction to colleagues, familiarization withÌýCalvin resources, campus tour, etc.
  • CoordinateÌýlocal bank account.
  • Set up regular meeting schedule.
  • If visitor would like to sit in on any classes, make sure to introduce them to professors (be sure visitor knows how much textbooks cost).
  • If the visitor would like to speak on a topic of general interest to the Calvin Community, please work with the dean for faculty development to arrange a public lecture and possible reception.
ONGOING
  • ProvideÌýhuman resourcesÌýprior notice of any travel by a non-U.S. visitor outside Grand Rapids.
At Conclusion of Visit

For all visitors:

  • Confirm that keys, ID cards, library books, office contents, borrowed items, and any other Calvin material have been returned. Give visitor notice of immediate shut-down of permissions and access in Calvin systems (especially computer systems).
  • The Calvin contact is responsible for conducting an informal interview with the visitor and providing theÌýdean for faculty developmentÌý(andÌýhuman resourcesÌýif non-U.S. visitor) with a brief program report (due within one month after the visitor's departure). The report should include the following:
    • Visitor's updated home, institutional, and email addresses.
    • Brief description of progress on visitor's intended research during their time at Calvin.
    • Brief assessment of Visiting Scholar program, including any successes and/or problems; include any recommendations for improvement.
    • Detailed summary of any participation in campus activities (classes, workshops, etc.) and any involvement in local community activities.

For all non-U.S. visitors (per Department of State requirements): ÌýProvide a complete list of all trips and other travel taken in the United States during their visit.

Questions? Please contact theÌýOffice of the Dean for faculty development and research initiatives.