Prism Blog

Archive for 2010

Watch the latest Talis Prism Development webinar

If you were unable to attend one of our recent Prism 3 update webinars, then catch up on latest developments by watching the recording below or by downloading the video.

This was a wide-ranging webinar. It began with a brief tour of Prism 3, highlighting the main changes that have been released during 2010. In the rest of the webinar we looked at the developments that are in progress and planned for the New Year, including the benefits of the Linked Data API, Loan History, improvements in the design and functionality of the user account, progress with the Semantic Data Model, and more. This was a lively and positive session to round of the year, with many questions from a large audience.

[podcast format=”video”]http://talis-videos.s3.amazonaws.com/prism_webinar_131210.mp4[/podcast]

Prism 3 Release – December 2010

We’re pleased to announce that the recent hotfix release of Prism 3 has now been released to the live service. This resolves an issue in the caching system and enables reset tenant cache to function correctly. An issue that limited numbers of customers experienced with the availability display has also been addressed.

If you have questions on this, or any other issue, please feel free to email phil.john@talis.com, contact your account manager, or leave a comment on the blog.

Taking a New Look at the Account Pages

One of the things we’ve been keen to do for a while is re-assess presentation of the “My Account” pages in Prism 3. This has been dependent on another piece of work, improvements to the Local Data Services (LDS) that pass information back to Prism 3 from your local LMS. This does mean that some of these modifications are dependent on installation of the newer LDS at your site.

Reasons for the Changes

One of the most requested additions to Prism 3 was the Loan History, we’re going to add this, but we’re also taking the opportunity to look at how we deliver account information overall.

Similarly to how we approached the availability redesign earlier in the year, what we wanted to focus on was:

  • How can we make the complex data as people-centric as possible?
  • How can we make the common tasks easier?
  • How can we make the information easy to comprehend?

So in this post, we’ll take a look at some of the concepts we’re working with. Please do provide feedback and remember these are mockups rather than final designs so subject to change. Also, it’s worth remembering that these are defaults that can be over-ridden by custom css or interface labels. We’ll also be looking at further changes earlier next year as part of the “improvements to my account efficiency” roadmap item.

Breaking the Data into Manageable Chunks

Our first task with the account pages of Prism was to break the data into more manageable, compartmentalised chunks. Currently everything about an account appears on one page, and this will get pretty big, pretty fast, so we wanted to move each section of my account to its own sub-page.

This means each task has its own context to work in resulting in pages for:

  • Current Loans
  • Charges
  • Reservations
  • Bookings
  • Loan History
  • Inter Library Loans

There’s been some discussion on how this is to be split up, with the issue of whether Bookings and Reservations are different enough in the minds of library users. Currently we’re erring on the side of keeping them separate, but we’d be interested in your thoughts on this.

The Account Summary

At the top of the accounts pages we’ve realigned the summary details, in much the same way as we did with availability, to be simple statements making for a more “human” page. We’ve also made it persist through the various account pages, acting as a “notifications area” to summarise items that need action (reservation pickups, charges and so on). We’ll also use this area for confirmation of actions.

Accoutn Summary - showing loans, reservations, pickup and charges

A subtle change here is that the charges indicator contains the total including currently accruing fines, where previously these were only shown as part of the loans (something that confused users).

Beneath the summary, the navigation between the various sections of the account pages will be by mini-tabs. This is a nice simple metaphor for this type of content, allowing easy movement between the various sub-sections along with highlighting current location.

Current Loans

Here we’ve put the information that the majority of users need most of the time and made it the default page when you log in. We’ve taken a look at the Google analytics and the common paths involve going in and renewing, so we want to make this as easy as possible. So we’ve added a “renew all” button, to speed the most common use case, that of “I can’t get to the library, so need to renew all my current loans”.

Current Loans - showing extra item detail, highlighting of overdue and renew all button.

We’re improving this by adding in the jacket image and a link to the item in question. We’ve also removed some of the detail that really isn’t needed by most users: item ID and control number. This was a hard choice, but scenarios in which these would be useful are fairly limited in this context.

A useful piece of feedback we got from libraries was that showing the renew count out of a total would be really useful, so we’re hoping to add this too.

We’re also adding in several cues as to the state of individual items. We’re looking at several options for the exact nature of this display. The one shown above is a simple enhancement to the existing tables. Where an item is overdue it turns a shade of red and bolded.

The second option is adds an additional collation of items so that common dates act as headings (much like an email client might). So you can see “overdue”, “due back this week”, “due back this month” and “due later” to help as a cue for what needs attention now.

Current Loans - with extra headings breaking up overdue, due next week and so on.

Loan History

The Loan History pages have the potential to contain a huge amount of data, especially if a library user has had an account for several decades and borrowed books every few weeks in that time. Thus the Loan History page needs to be broken down into manageable chunks.

Loan history - showing navigation and sorting options

The history can be re-ordered by the title, main author and loan dates; each version of the navigation provides its own paging mechanism.

Reservations, Bookings and Inter-library Loans

Although the concepts may be different, the mechanics of checking these three elements online are very similar, so the interfaces here differ only in the labels.

Reservations - showing pickup point, and highlights to ready for pickup status.

Again, the basic changes are to add in the book covers, links to the books and highlighting of common actions. A simple statement of entitlement is an element we hope to add to allow people to manage their account more efficiently and again we’ve added a cancel all button.

Charges

The charges page has only a few minor improvements. We’ve included the summary and with the improved LDS service we can fix the missing accrual date problem. As mentioned earlier, the totals now represent the current total owed, including currently accruing items.

Charges - showing history of charges and date accrued.

Next Steps

The key aim of this work is to add in the loan history work, break the account pages into manageable chunks and integrate it more completely into the rest of the product. Although it mainly addresses the “Loan History” roadmap item it also paves the way for future work including the “improvements to my account efficiency” item.

Please do let us know if there are issues we haven’t considered either here or via email.

Prism 3 Hotfix Release Preview – December 2010

We’ve released a preview version of a hotfix for two issues some customers are experiencing. The issues addressed are:

  • Reset Tenant Cache failing under certain conditions
  • Availability not displaying summary message under certain conditions

We are planning to release these to live early next week.

As with all previous releases, these changes can be tested by using the demo version of your site. For customers using the “prism.talis.com” domain, this is accessed by putting “demo/” just before your tenancy name, e.g.:

http://prism.talis.com/demo/leicestershire/

For customers with own hostname enabled, the “demo/” is placed at the end of your URL, e.g.:

http://catalogue.sunderland.ac.uk/demo/

If you have questions on this, or any other issue, please feel free to email phil.john@talis.com, contact your account manager, or leave a comment on the blog.

Talis Prism 3 Development Update Webinar

For the last development update webinar of 2010 we are going to review the current functionality of Talis Prism 3 and look forward enthusiastically to the new features planned for the first half of 2011.

This free webinar will be of interest to all customers including those who have not yet started to implement Talis Prism 3.

It will be one webinar, rather than the usual academic/public split, and we will be making time for a lively question and answer session.

The webinar will be on Monday 13th December at 14:00 for one hour. Click here to register.

In the meantime keep up with the latest Talis Prism 3 news and developments on the Talis Prism 3 website and blog.

Prism 3 Release – 19 November 2010

We’re pleased to announce that the recent preview release of Talis Prism 3 has now been deployed to the live service.  For full details on what has changed in this release please visit the preview release notice here: //blogs.librarymanagementcloud.co.uk/prism/2010/10/29/prism-3-release-preview-october-2010/.

If you have questions on this, or any other issue, please feel free to email phil.john@talis.com, contact your account manager, or leave a comment on the blog.

Watch the latest Talis Prism Development webinar

If you were unable to attend one of our recent Prism 3 update webinars, then catch up on latest developments by watching the recording below or by downloading the video.

The main topics covered were:

  • Introductions
  • Roadmap
  • General Update
    • Release
    • Semantic Data Model
  • Roadmap next steps
    • View Loan History
    • Choice of Jacket image supplier
    • Linked Data API
  • Reservations survey
  • Google Analytics stats
  • Questions

[podcast format=”video”]http://talis-videos.s3.amazonaws.com/prism_webinar_081110.mp4[/podcast]

Prism 3 Release Preview – October 2010

We’re pleased to announce that we’ve just released the latest version of Talis Prism 3 for everyone to preview.

This release comprises the following changes:

  • The culmination of a large unit of work focussing on performance
  • A bug fix for customers with own hostnames, allowing them to view items in their sandbox tenancy.

As with all previous releases, these changes can be tested by using the demo version of your site. For customers using the “prism.talis.com” domain, this is accessed by putting “demo/” just before your tenancy name, e.g.:

http://prism.talis.com/demo/leicestershire/

For customers with own hostname enabled, the “demo/” is placed at the end of your URL, e.g.:

http://catalogue.sunderland.ac.uk/demo/

If you have questions on this, or any other issue, please feel free to email phil.john@talis.com, contact your account manager, or leave a comment on the blog.

Talis Prism 3 Default Design Released

One of the most common areas that customers tell me they struggle with during the implementation of Talis Prism 3 is the design aspect. We have always provided a very basic design template so that each individual organisation can customise Prism 3 to their own design requirements. However this has proved challenging for some organisations who do not have the relevant in house CSS and Web Design skills to complete their design.

We have taken this feedback on board and are pleased to announce that a new default design skin is now available for those who would like this to then further build their design on. To view the default skin please visit http://prism.talis.com/trial .

If you would like this applied to your Prism 3 tenancy please contact Imraz.Mohammed@talis.com.

If you have any queries about this or any other aspect of Talis Prism 3, please contact your Account Manager or email Imraz.Mohammed@talis.com.

Keep up with the latest Talis Prism 3 news and developments on the Talis Prism 3 website and blog.

Back in the academic groove with Google Analytics

We started using Google Analytics with Talis Prism 3 back in March, when usage across tenancies was relatively low – in the hundreds. Of course, in the intervening period a significant number of customers have adopted Talis Prism 3. As Imraz Mohammed pointed out on his recent Talis Prism 3 Update on this blog, 30 libraries have now moved to Talis Prism 3, of which 13 are university libraries. The combination of these increased volumes of usage and the approach of the new academic year means that Google Analytics is proving invaluable to Talis development staff and customers alike. Not only does it provide an updated picture of usage every few hours, but it’s so flexible that in different contexts, in this case, different times of year, it can provide powerful metrics for diagnostics and decision-making.

Of course the start of the academic year is particularly interesting (or murderous, depending on your viewpoint) for university libraries, where the user base and its multifarious motivations are shifting almost by the day. Around the middle of September, we were running at around 9,500 unique visitors per day across all the Talis Prism 3 tenancies. At this point it can be useful to start using the map facility on Google Analytics to get a picture (literally) of the shifting balance between use on campus and access from students at home.

And then suddenly, from Monday 27th September, universities welcome the year’s new students and the usage statistics started to climb. University of Northampton provides a great example of this. Already by Monday 27th, Talis Prism 3 is handling twice the previous traffic. On Tuesday there were 39,000 and by Friday they had reached 59,000.

By week beginning  4th October, students are returning, but freshers continue to make their presence felt on Google Analytics. The important metric Average pages per visit decreases as freshers log on to take a look at the system and play around with a few cursory searches before lectures start. On a similar vein, Average time spent on page has dipped and the bounce rate is up.

We start to see patterns at many levels. We notice that usage peaks on Wednesday and Thursday and then calms down for the weekend, before a growing again from Monday. And the longer we use it the more useful those patterns will be. I look forward to next year when we’ll be able to refer back to the September / October metrics in order to anticipate usage.

Our interest in Google Analytics extends well beyond the value for academic libraries in understanding end-user behaviour, important though that is. When providing Software as a Service such as Talis Prism 3, we need to be able to anticipate load with a high degree of accuracy. If not, unexpected spikes in usage may compromise the service. And this of course is the most critical time of the year, when expectations among students of campus services such as library systems are most likely to be set. On 27th September, when we experienced 1.5 hours of outage on Talis Prism 3, it was crucial to diagnose, resolve, and also make sure the problem did not recur. Two weeks later, Google Analytics enables us to state with confidence that we are successfully handling a five-fold increase in traffic compared to 27th September.

In order to resolve the underlying problems behind the outage, we advanced some of the performance enhancements we’d been working on into production. The majority of these changes will be released shortly, following a series of phased roll-outs, in which we install change on half the servers, monitor, and then roll out to the rest of the pool. This ensures that changes are tested in isolation, and is part of a broader testing strategy around Talis Prism 3, centred around:

a.       Automated tests which, for every change introduced, run through every Talis Prism 3 transaction – e.g. renewal, search, login – checking for an unchanged output in every instance. 20-30 minutes is all it takes to run through this comprehensive suite of functions.

b.      Performance tests in which we mimic live traffic on the two staging servers here at Talis before release onto customer tenancies.