Use Internet2 SiteID

Already have an Internet2 SiteID?
Sign in here.

Internet2 SiteID


OneCampus Best Practices: Driving Adoption with Student Involvement

Mar 24, 2015, by Eric Westfall
Tags: Higher Education, Internet2 Member, Internet2 NET+, OneCampus by rSmart

A Q&A with Katelin Corbin, UTIS Student IT Ambassador, Indiana University

In 2013, Indiana University (IU) developed as a way for students, staff, and faculty to quickly find and access university services in a marketplace format. Since its deployment, access to more than 400 apps has been streamlined for 130,000 users across eight campuses.

In 2014, IU partnered with rSmart to make this innovative, cloud-based solution available to all higher education institutions and participated in the NET+ service validation process to integrate Internet2's InCommon federated authentication and ensure OneCampus was architected for performance across the advanced Internet2 Network to maximize deployment efficiencies. The institutions who helped rSmart and IU shape the new NET+ OneCampus solution included BYU-Idaho, Clemson University, University of Maryland, University of Nebraska at Omaha, University of Pittsburgh and University of Utah.

As new institutions prepare to deploy OneCampus, many have asked IU for tips and best practices on how to drive a successful adoption. In the Q&A below, Katelin Corbin, a junior at Indiana University, describes how students are helping increase adoption and educate their peers on the benefits of OneCampus.

Q: How did you get involved with OneCampus? What role do students play in the promotion of IT resources and technology on campus?

I first got involved with our University Information Technology Services (UITS) department as a Student IT Ambassador. We are a volunteer student leadership club that helps promote campus IT resources, technology, and tools and provides feedback to UITS on outreach efforts.

In August 2013, I joined a team focused specifically on that was made up of three students from each of the major campuses and one student from each satellite campus. Our role is to test the application, share feedback, and help get the word out. The committee meets regularly and we use a listserv to bounce ideas off each other.

Q: How do you help get the word out about OneCampus to students?

As a Student IT Ambassador, I attend tabling events inside academic buildings and in high traffic areas such as the library to talk with students about its ease of use and search functionality. I also show how it's mobile-friendly and allows them to find what they need with just one-click. We use a branded tablecloth, computers, mobile devices, and free 'swag' such as t-shirts or smartphone wallets to draw students to the table.

IU also promotes OneCampus using social media, online bulletin boards, and visual advertising such as campus buses wrapped with the logo and website, bus stop signs, and digital billboards inside the libraries.

Q: What do students like most about OneCampus?

Students like because it is mobile friendly, easy to use, and the search works similar to Google so it makes finding information much easier and faster than our old legacy portal. The 'My Favorites' section is also very popular and students like being able to submit feedback and suggestions.

Q: What would you share with administrators at another college or university preparing the deploy OneCampus?

It is essential to get students on board and involved in the promotion from the start. Students would rather hear from students than faculty/staff. It is also important to find a way to pitch OneCampus as the 'better way' and include testimonials about the benefits. Students also love free stuff so items that are branded with the website are very effective.

Eric Westfall is an Enterprise Software Architect at Indiana University and manages the university's Enterprise Systems Integration team. His portfolio includes One.IU, an events calendar, IU’s mobile application, notifications infrastructure, IU classifieds, application deployment automation, and Kuali Rice middleware.