Prism Blog

Prism Release Preview – 15 February 2013

I’m pleased to announce that the latest release of Prism is available for you to preview. This is an infrastructure release with changes to the Prism infrastructure in order to support the delivery of the roadmap items “Migration to the Capita Infrastructure” and “Migration to a new domain name”, which are due during 2013.

 Making the most of your preview

We’ve made technical changes to the way Prism searches and retrieves data. This means it’s important that you make the most of the preview period to ensure your tenancy continues to behave the same as it does with the live version of Prism. As with every release, please also ensure that your local styling and extensions continue to work correctly.

As usual, you can preview this release by inserting ‘/demo/’ after the prism.talis.com part of your URL and before the name of your tenancy, e.g. prism.talis.com/demo/mytenancy/. If you have your own host name, you’ll need to use prism.talis.com instead.

Release to the live service

The date for release to the live service is dependent upon your feedback from preview. This is currently planned for Monday 4th March 2013.

4 Responses

  1. Michael Stead Says:

    Styling seems to have remained intact, but there’s a problem with loan history – https://prism.talis.com/demo/wigan/account/history – on the demo tenancy. The live tenancy displays a list of books with cover images as you’d expect, but the demo tenancy just has a fragment of HTML – <a href=" – instead.

    I've got a demo user account which shows this error, so feel free to get in touch if you want to replicate it.

  2. Terry Willan Says:

    Thanks for this, Michael. We’re fixing this and a few other issues, and will update the release on preview soon.

  3. Claire Eskriett Says:

    Hi Terry

    We can’t see ‘More like this’ on our demo tenancy, e.g. bib id 1083087 (it definitely has a More Like This display on the live tenancy)

  4. Terry Willan Says:

    Hi Claire, It looks OK here in various browsers. Perhaps it was due to caching in the browser, which can be cleared by Ctrl+F5. Are you still having the problem?

Leave a Reply