, 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); })(); Campus Event Parameters Event Services | app

app

Skip to main content

Campus Event Parameters

Guidelines and expectations for staff, faculty and students making plans for on-campus meetings.

Event Services assistance

Meeting ParametersService Level Provided
Full day or multi-day eventsSelf-service room reservations (may request training through Event Services). Confirmation of reservation requires final ES approval.
Events in roomsSelf-service room reservations (may request training through Event Services). Confirmation of reservation requires final ES approval.
Conference type events (multiple rooms/days)Should utilize an event planner.
Prince Conference Center eventsEvent Services authorization and event planner required.

Facilities set-up

Meeting ParametersService Level Provided
Table Setup in hallways, lobbies, Johnny’s, etc.Self-setup. Facilities can provide information on where items can be picked up.
Academic Meetings/ Events of less than 40, university staff

Self-setup.

  • Rooms should be returned to their original set-up, as you found it.
  • When setting up a room, do not create an obstruction to exits.
  • Upon reservation, staff should consider rooms that require minimal set-up for group size.
Academic Meetings of > 40 peopleSet-up may be requested but should be scheduled at least two weeks in advance.
Prince Conference CenterSet-up completed in-house by PCC staff per Event Services reservation.
Conferences on CampusSet-up will be coordinated between Event Services and Facilities.
Athletic EventsGame Day Staff when applicable; Upper bowl of bleachers remains closed unless bottom bowl is sold-out.

Technology assistance

Meeting ParametersService Level Provided
app staff or facultyContact Help Desk for assistance or for pre-event training. May utilize Audio Visual services for deliveries of items that might not normally be located in the space ONLY if pick-up is not available.
Athletic and Performance SpacesInternal performance events: Chapel, Recital Hall, CFAC Auditorium, Gezon, and VN Arena require technical assistance
app sponsored for external audiencesTechnology assistance, setup, configuration or staffing needs to be agreed upon with Event Services

Catering provisions

If app catering services are being utilized, please be sure to book your room prior to contacting catering.

Meeting ParametersService Level Provided
app meetings, university personnelNo food (internal or external) should be provided with app funds.
app staff events (i.e. HR/Provost sponsored events, department “parties”)No food (internal or external) should be provided with app funds.
Student EventsFood allowable as budgeted funds are available. Consider most affordable on/off campus option.
Recruitment Events, < 20 peoplePlated meals available through catering
Recruitment Events, > 20 peoplePlated meals or buffet available through catering (PLEASE NOTE: Health concerns should be carefully considered prior to scheduling a buffet)
Donor Events, < 20 peoplePlated meals available through catering
Donor Events, > 20 peoplePlated meals or buffet available through catering or an affordable off-campus option. (PLEASE NOTE: Health concerns should be carefully considered prior to scheduling a buffet)
Meeting with External Constituents

Consider carefully whether food is truly necessary.

If so, consider most affordable on/off campus option. Consultants will often consider providing food as a part of their contract costs with app. Should clarify whether consultants can/will pay for food.

Make a Reservation