Following the HigherEdWeb 2019 Conference, OpenScholar surveyed 55 IT and marketing leaders about their experience supporting faculty websites. 61% of respondents work at R1 or R2 research universities.
This is what they said.
Faculty sites are built in fragmented ways
75% of respondents work at universities where faculty sites are built on a CMS that the school supports. But most schools also have faculty directory and profiles that IT controls, as well as sites built on technology that the academic chooses.
Opportunity: Have an integrated approach to important faculty, department and other sites.
IT supports 20 different website publishing platforms
Wordpress and Drupal are some of the most popular technologies used. Many schools also built proprietary plugins or publishing platforms. Opportunity: Consolidate systems to save time and control branding.
To support faculty sites, IT spends the most time answering help desk tickets
Most requests are to add/edit content, fix bugs and lead faculty trainings. IT is also asked to update designs and templates.
Opportunity: Take back your time by outsourcing faculty site tickets to a full-service team that builds sites and maintains content.
At R1 schools, 65% of faculty tickets are resolved within the day
30% are resolved within the week, and 5% over 8+ days.
Opportunity: Boost faculty and department satisfaction with faster responses to all tickets.
The site requests backlog is typically less than 2 weeks
But 31% of respondents couldn’t quantify the backlog.
Opportunity: Streamline the process by which faculty request sites and updates, and tighten reporting so that IT can easily track requests.
If you’re interested in saving time and consolidating faculty website systems, let’s chat.
OpenScholar is the leading research asset management platform, built for fast-moving IT and marketing departments to help faculty publish research and connect with the world. With one-stop publishing and activity reporting tools, OpenScholar is trusted by over 25,000 users at Harvard University, University of Virginia, Beth Israel Hospital, Broad Institute and more.
The typical OpenScholar customer is research university or hospital IT department that wants to scale and support hundreds of flexible, secure and branded websites. See how OpenScholar powers 11k Harvard sites: https://openscholar.harvard.edu