Update Jan. 25, 2017: We’ve been asked to accelerate our timeline for launch. We’re now aiming to launch the site in August, in time for the fall term. Launch has been changed below.
Scope & Schedule Defined
The web team has now defined the scope of the new redesign web site. Search will be high on the list of things to improve for our users. With Emerging Technologies Librarian Mark Mounts’ detailed research in this area, we will be implementing several of his recommendations, as well as improving the look and feel of the search results page itself. Google Analytics data shows that the Catalog and the Research Guides receive quite a large amount of traffic. We decided a redesign that didn’t consider the user’s experience going from our main web pages to other heavily trafficked areas would result in user confusion and/or dissatisfaction. So, now our plan includes a new Drupal web site, along with a light redesign on some non-Drupal systems in order to ease user navigation between all digital services.
We also have created a detailed content site flow, to help us organize and to inform our future wireframing and global navigation. Again, we used Google Analytics data, combined with our research of other academic library web sites to help decide which areas were the most important. We’re also going to leverage some of the offerings from our SpringShare systems, especially embeddable widgets which will allow users quick access to resources in places we think they will be looking for them. (For example, the “Chat with a Librarian” widget.)
The Content Flow map (PDF) shows how we are thinking of organizing content on the web site and how to make it easier for users to find what they are looking for.
With all this information, the team was able to create a draft schedule that has a launch in August 2017. We are using Asana, a project management tool that was suggested by the College web team to track our tasks.
As we now begin to build out the new Content Management System, we wanted to make sure to keep all Library staff that may be impacted informed as the project moves along, and get feedback at crucial points in our project. We will be using the User Engagement & Technologies group as our new stakeholders on the project, in order to ensure that all library branches are represented.
Other meetings we’ve scheduled:
Monthly Meeting of OmniUpdate and Research Guide content creators
- 40 staffers
Bi-Weekly Meeting with core team on SpringShare products
- Dennis G., Bill F., Amy B. Mark M., Allie A.
Bi-Weekly meeting with core team on Technology, Drupal solutions
- Paul M., Josh S., Allie A, Amy B., Eric B., Anthony H.
Search team meetings 2x a week
- Josh S., Allie A., Mark M., Amy B.
Drupal Content Entry Experience meetings weekly
- Dennis G., Amy B., Allie A.
Wireframing/design meetings weekly
- Dennis G., Amy B., Allie A.
Usability bi-weekly meeting
- Don F., Amy B., Allie A.
Editorial Meeting bi-weekly
- Jane Q., Karen S., Dennis G., Amy B.
Please let us know thoughts and comments. We are looking forward to a great 2017!