Tag: data and apis
We generate lots of content and manage lots of data in disconnected ways. The University of Arkansas started a project a few years ago called the Campus Data Project. A not seksi name for an incredible foundation with a REST API that lets users tie all kinds of data together that they never could before. From campus maps crossed with the campus directory to a news platform that updates experts lists and research blogs, the team has an ecosystem of useful reusable information getting more valuable with every piece of content added to it. Nixon will talk about the evolution of this system, how we use it currently, what our future plans are and how we have shared this platform with others in our state.
Fix All The Map Data! (DPA4)
Campus mapping: so many data sources, competing services, and oh so many pieces of data out there to correct. Knight will look at the various ways you can report data errors and work with data providers to help your visitors - and potential students - find their way around your campus.
If you use a Google Search Appliance (GSA) or the Google Custom Search Engine (GCSE) sometimes you can find it limiting to have it not well integrated with your web site. Both of these tools have an XML API that will allow you to build your own front-end and still leverage their power. Search can even be integrated into your 404 (Page Not Found) handling, so when an old URL doesn't work, it gets used as the basis of an automated search! Old URL is reported as bad to search engines, while user sees the most likely pages that replaced it. Everybody wins!
It's possible to make a structured, consistent, API that can handle changes to logic and the schema. Sure, it seems like a good plan to dump everything out of the database today, but what are you going to do when something changes down the road? Let's have a talk about some SOLID ways to structure our APIs and keep them from breaking down the road.
Less than two years ago, the largest department at Carnegie Mellon University ran a student database off defunct software, required students to complete forms by hand and collected qualifying exam documents from 25-35 students each semester via email. Since then, the university has updated its student database, built a department-wide data warehouse, introduced interactive forms and created a cloud-like solution for qualifying exam document collection. The key to these improvements has been the fruitful working relationships between academic advisors and technical staff. This presentation will provide an overview of how the presenters framed and prioritized IT requests, partnered with IT staff to make small and large-scale projects come to fruition and gained support in new IT initiatives. They will address the challenges of communicating across domains of expertise to successfully implement new technology solutions from both a higher education and IT perspective.
Data driven applications have been the norm for years, yet the availability of university data is often lacking. Many of our universities’ data is locked up within departmental silos and closed systems. Our requests to access this data usually result in blank stares, laughter, or confrontation. After all, it’s “my data”! And all the while our applications aren’t as robust as they could be, and users have suffered. At The Ohio State University their campus mobile app has been a cross-departmental collaboration, aggregating lots of campus data. Other departments have begun to see this as a model to follow. Building on this success, OSU launched its Enterprise Integration Platform initiative. The goal is for all campus data to be available via web services/APIs primarily RESTful accompanied by a user friendly searchable API where any person on campus can easily find data available and request access. It will give developers the ability to create robust applications that extend far beyond the silos that fall within their departments. This is a technical change as well as it is a cultural one. Developers can create the applications their departments are asking for. It also creates an awareness of the collective capital that resides in campus data. We’ll share our wins, losses, challenges, and long term plans. We’ll describe the technologies we’re using and things we’d do differently.
Taking the Web Offline (AIM10)
Let's face it. There more devices out there than you can support with dedicated native apps. And except for very specific cases, most of what you'll want to do with your app is available through web API's. And yes, this includes offline support. During this presentation we'll take a look at your options for storing data in the client browser and how you can leverage it to speed up your websites. We'll also spend some time looking at how it was implemented on 2014.highedweb.org.
Imagine a university website with content tailored specifically to the individual viewing it - a site where nobody has to hunt to find information relevant to them. Sound like a pipe dream? Maybe, maybe not. Social media has fundamentally changed the information gathering process. People want to be social anytime they consume media. According to social media mogul Gary Vaynerchuk, “This means that you need to fold a social element into all of your creative… and into every interaction with your customers…. From now on, every platform should be treated as a social networking platform.” Now, considering websites, if it's not social, it's not relevant. Fortunately, there are many ways to leverage the big data of social networks to an institution's advantage. A few key facts about users (such as age, location, and personal interests) can take content from “generic” to “extremely relevant.” Thankfully, social media APIs make this fairly simple to implement. Anglea will explore the possibilities that exist for integrating the secret sauce of social media into a website. He will also discuss everything from big ideas to small actionable steps to begin enhancing the social relevancy of content.