Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Consultations with libary staff who have expertise in various areas to better inform the redesign projects [(blog post | full notes summary(docx)]

...

  • As the proof of concept is iteratively developed, advancing from prototype to pilot to live production, the platform will be continually tested. It will be initially shared with a few targeted focus groups, then released to more wider audiences througout the year.

...

A big benefit of the hybrid approach is that on the back end, APIs can be tweaked or even swapped out with minimal interruption for the user. Changes can be made without extensive downtime or change in staff workflow.  Further, this methos offers more control to develop a user experience customized to meet OSU's unique community needs.

Can I see some examples of what our new discovery platform will be like?

Absolutely. But keep in mind that we are developing a Buckeye-centric experience based on evaluating evaluations of user feedback and web analytics gathered from the OSU community. ThereforeFor that reason, these examples can only hint at how our discovery platform will function. 

...

When will the project be completed?

...

The most effective way to measure success is through user-centered design. We will track improvement by making ongoing comparisons of usability data that we began analyzing in Spring 2016 for the Discovery Inquiry Proposal. As User Experience Leads for both the website and discovery redesign projects, Leads Robyn Ness and Meris Mandernach began  began performing usability testing in April 2017 that provides , providing even more data to guide us during this process. These presentations summarizing their findings:

...