Recommended steps to rollout the new list view at your University

Overview

This article is designed to talk you through the recommended steps to roll out the new list view at your University. There will be a number of factors you wish to consider, including:

Step 1 - Timing of a change within the academic year

The new list view interface has been designed to be intuitive and in line with web design and browser capability that should be familiar. It is important not to underestimate change - however small or straightforward, for a student under-pressure for an assignment or exam, a change can impact. 

When Talis contact you to advise the interface is available, the students and academics will not be aware that anything has changed until you decide to enable it more widely. You may wish to return to this decision following a staff side review phase - see Step 2.

Step 2 - Library staff familiarisation - staff side review

When something changes on an interface that is used for study this may raise questions from Students and Academics, so it is important that the Library staff first have the chance to familiarise themselves with the changes so they are prepared to support others.

Talis have created two roles that help with this stage of the rollout:

  • List View Beta - Enables the user to see a List Beta button in order to view any list in the new list view

World_War_History_-_Short___Broadminster.png

  • List View Admin - Enables the user to default any list to 'List View Status' so any other users visiting that list see the list in the desired status

World_War_History_-_Short___Broadminster.png

You can control who to give the individual roles to using invites.

List View Statuses:

  • Beta off -  means the 'List beta' button will not be presented to all users.  It will be visible only to users with the 'View list beta’ permission, supporting an invitation-only beta of the new list view.
  • 1.0 by default - will enable an opt-in beta for all users of the list.  The 'List beta' button will be visible in the original list view, allowing users to switch to the new list view (and get back again).
  • 2.0 by default - will enable an opt-out beta for all users of the list.  When attempting to visit the original list view, the user will be automatically redirected to the new list view.  Once it is loaded, a button will be present on this view allowing the user to revert to the original list view if they choose.

Once Library staff have the permissions it may be a good idea to arrange a feedback session or focus group so you can decide and plan the next steps in the rollout.

Step 3 - Academic awareness

Before introducing it more widely you may have Academics who are willing to review the changes in the interface and help advise on how they feel the change will be received more widely and how much support they think will be needed. Often universities have their own user guides or video tutorials, these may need updating so that if an academic is unsure how the new features work they will have a resource to turn to. You may find that you can reduce the level of guidance needed with it's improved ease of use.

Step 4  - Student awareness

Having gained feedback from Library and Academic staff, you may feel the changes are too beneficial to hold back from the students for too long. Is the start of next academic year too long?

You may have access to a student focus group or even conduct an ad-hoc survey within the library to canvas student's thoughts by presenting the new view to them. What may seem like a big change to us could be minimal to the average tech-savvy student.

Often universities have their own user guides or video tutorials. These may need updating so if a student is unsure how the new features work they will have a resource to turn to.

You could even link Talis' overview of the new list view - New list UX - features

Step 5 - Methods of rollout

If you are considering the rollout of the new list view to academics there are 3 ways in which you can switch lists to the new list view:

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk