Prism Blog

Archive for the 'Functionality' Category

Identifying the format in search results

The latest release of Prism, when supplied with data from the new MarcGrab, re-models title and statement of responsibility information from MARC field 245, analysing the different kinds of data that MARC often lumps together, to make better use of it. One benefit of this is that any number-and-name-of-part information embedded in subfield $c (statement of responsibility, etc) is now appended to the main title so that you can see all of the precise title information together. Another benefit is the display of the statement of responsibility.

Historically, a General Material Designator (GMD) has been added to title information to give some indication of the kind of material of the item. However, its general nature has always been unsatisfactory because users want more precise information, and this is why, in the new cataloguing rules, RDA, the GMD is dropped in favour of more specific alternatives. For these reasons we have omitted the GMD.

A better alternative to the GMD is accurate format information, presented so the user can see at a glance what it is. The format is already in a regular position at the beginning of a line, but to improve its display we’re proposing the following changes:

  • Move the summary snippet to the foot of the entry
  • Select the most specific format term, where more than one is currently given, according to a preference list. For example, select ‘eBook’ from ‘Electronic resource, eBook, Book’
  • Display the selected format in bold
  • Place the edition statement and the year of publication, in that order, after the language, to give more prominence to these important elements
  • Change the label ‘Published’ to ‘Publisher’ and unbold it by default, so that it does not distract attention from the earlier elements.

It is posible to hide the language and publisher elements with styling tools (a simple update to you site.css file). It is also possible to hide just the default language, that is, the language of your catalogue, usually ‘English’. For details of how to apply these changes, or to request us to do it for you, please raise a Support case.

This proposal is only about results entries, not the Item Detail page. There are other issues and ideas for the Item Detail page, which will be addressed later.

We’ve put together some examples. Please click on the image to get a full size view. Cover images have been omitted from the examples but they would be there, as now, in the implementation.

We’d love to hear your views on this proposal. Please comment on this blog post, or you can email me terry.willan@capita.co.uk. As soon as a favourable consensus is clear we’ll start work on this with a view to getting it into the next release of Prism.

Prism 3 Local Data Services Beta Test Progress

Following the recent release to preview of the latest version of Talis Prism 3, we’re now beginning the beta test with five customers for those features that require an upgrade to the Local Data services (LDS) software.

The LDS runs in your local environment and handles dynamic interactions between Prism 3 and your local database, such as fetching availability information and managing renewals and reservations.

The main new features that require the LDS upgrade are Loan History, which will display under an additional tab in the re-designed My Account arPrism 3 Loan historyea that you have in the Prism 3 release preview, and the display of an ‘In Transit’ status in the availability area on the Item Detail page. The LDS software has also undergone major revision ‘under the bonnet’, providing the foundation for more efficient further development.

The beta test is expected to take several weeks. After initial testing by library staff using the library’s sandbox Prism 3 tenancy, the new LDS will be applied to the live local environment making the new features live for the beta libraries’ users, for a period of close monitoring.

We’re developing the LDS so that it can be updated automatically, making it much easier to deliver improvements in future. We’re including appropriate tools to allow you to remain in control, but crucially it eliminates time-consuming manual intervention. The beta test will encompass this auto-update aspect, so that the general release roll-out will be the last time manual intervention will be needed.

The version of Prism 3 that is currently available for preview works with both the old and new versions of LDS, detecting them automatically. We’ll leave it on preview for a little longer for you to check, but we’ll put it live soon to give your users those benefits that don’t depend on the new LDS.

Prism 3 Release Preview – 11 February 2011

We’re pleased to announce that we’ve just released the latest version of Talis Prism 3 for everyone to preview. This is a big release with lots of great new features, the most notable are:

  • View loan history (beta)
  • “My Account” redesign
  • Choice of jacket image supplier
  • Linked data API
  • New breadcrumb trail
  • Display of “in transit” items
  • An alternative to “no image available”

We’ve also undertaken some “under the bonnet” work to support a lot of exciting developments we’ve got planned for the next year and beyond.

This release also contains some other changes and a small fix:

  • Additional fields included on the feedback page
  • Year facet is now sorted in descending order
  • Fix for a bug in the facet system where values with no corresponding results in a search were being displayed

My Account/View Loan History

The most visible change in this release is the “My Account” redesign that Matt blogged about in December. The new design splits different pieces of data into their own sections and simplifies some of the most common workflows we’ve identified analysing log files. A very common operation is renewing all loans, which is now possible in a single click with the “Renew all” button.

We’ve also looked at the data displayed to users and made a few tweaks, including humanised dates and displaying ILL statuses as text descriptions rather than code numbers.

A new section has been added to allow users to view a history of their past loans; these can be paged through and sorted by title, author or date borrowed. We’ve also added book jackets to serve as a visual “aide memoire” when browsing the list.

Developing Loan History has required a new release of “Local Data Services” (LDS) so we’re going to BETA test it with a handful of customers to ensure everything is working before performing a full rollout. Once the new version of LDS goes to general release and your system is upgraded, Prism 3 will start showing the “Loan History” tab.

Choice of jacket image supplier/Alternative to “no image available”

To increase the coverage for jacket images, we’ve been talking with several providers to augment the current offering. We’re in the final stages of these conversations at the moment and as soon as they are concluded we can enable them with the work we’ve undertaken.

In tandem with this effort, we devoted effort to an idea posted by City of London libraries on Talis Library Ideas: An alternative to the default “No Image Available”. It’s now possible to upload your own images that will be displayed if no cover image can be found. These need to be a particular size and named in a certain way so that we can detect that you’ve uploaded them:

The files should be named

no-image-small.[ext]

and

no-image-medium.[ext]

where [ext] is one of gif, png or jpg, e.g. no-image-small.jpg. We suggest keeping the size of the small image at 75×100 pixels, and the medium at 150×200 pixels.

These files can then be uploaded using the Talis Admin Console.

Linked data API

Allowing greater access to the curated data in your catalogues was a central reason for developing the Linked Data API and with this release you can now surface search results and item pages in a variety of machine-readable formats. The API will also allow richer extensions that are able to tap into more of the underlying data that drives Prism 3.

To view search results as RSS 1.0, you need to add .rss to the end of “/items”, e.g.:

http://prism.talis.com/demo/leicestershire/items.rss?query=Lost+Symbol

Any search can be surfaced in this way, so you could provide RSS feeds of new releases in particular genres; your users can then subscribe to these, allowing them to be informed when something they may be interested in borrowing becomes available.

The RSS icon now also appears in the browser address bar on every search results page; users can click this to capture their search as an RSS feed, allowing them to monitor updates to those results.

The RSS icon in Firefox

The RSS icon in Firefox

The RSS icon in Internet Explorer

The RSS icon in Internet Explorer (lower right hand side of image)

To fetch the details of a particular item in a variety of formats you just append the output type after the local control number, e.g.:

http://prism.talis.com/demo/southwark/items/638126.rdf

The supported output formats are: RDF/XML (.rdf), JSON (.json), N-Triples (.nt) and Turtle (.ttl).

Display of “in transit” items

Another Talis Library Ideas suggestion that we’ve completed for this release is flagging up when an item is in transit/between locations. This feature is also reliant on the new version of LDS, so will also be tested by a small group of libraries before going to general release.

New breadcrumb trail

At a Prism 3 user day last year, the University of Derby mentioned that it would be useful if individual facets could be removed from a search in progress, without having to go back several steps. We set about looking at different ways to present this option to users and settled on a brand new breadcrumb trail for Prism 3.

The new trail has small remove buttons after each element, clicking it will rerun the search without that particular constraint included – allowing users to “open up” their search if they haven’t found exactly what they were looking for.

This is a substantial release so we’d appreciate it if you could take some time to cast an eye over your tenancy and familiarise yourself with the changes we’ve made.

You can access the preview by placing “/demo/” after the prism.talis.com part of your URL, e.g. http://prism.talis.com/demo/leicestershire/.

If you have questions on this or any other issue, please feel free to email me phil.john@talis.com or your Account Manager (or comment here, of course).

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.

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 Preview – 2 September 2010

We’ve just released the latest version of Talis Prism 3 for everyone to preview; this release contains some essential precursors for introducing the Semantic Data Model, as well as several other under-the-bonnet tweaks.

The biggest change in this release is a new session tracking system. By tweaking how we handle “my account” sessions, we’ve been able make some changes which will allow us to further improve performance in Prism 3 going forward.

We’ve also enabled Talis Aspire integration, allowing those of you with our next-generation resource list management system to flag what lists an item appears on. If your institution uses Talis Aspire and you would like us to enable this integration, please raise a support request and we will make the necessary configuration changes.

For those of you undertaking your own styling, we’ve introduced a new theme fragment for placing all JavaScript includes; this allows us to control when they are sent to the browser, optimising the performance of your Prism 3 tenancy.

Finally, this version contains the first release of the Semantic Data Model. This will be trialled with several beta customers before being made more widely available. The work released today includes the new “Format” and “Content” facets, as well as display of Alternate Graphic Representation (MARC21 field 880) on item pages. Here’s a sneak preview of this new feature:

Main record representation

Alternate graphic representation shown after clicking on the "Chinese" tab.

As you can see, this release contains quite a lot of “under-the-bonnet” work so we’d really appreciate it if you can all cast an eye over your tenancies. To view the release preview, simply place /demo/ after the prism.talis.com part of your url, e.g. http://prism.talis.com/demo/leicestershire/.

If you have any questions on this, or other issues, please feel free to email me (Phil.John@talis.com) or your account manager (or comment here, of course).

New Stock/Prepared Searches

One of the features in the latest Prism 3 preview is new stock searches. I’m going to explain how to perform these searches once we roll out the MarcGrabber update to your system, as well as cover some other additions to the advanced search syntax.

Back in February, Alison explained how any query in Prism 3 can be saved as a prepared search, either by bookmarking or by copying and pasting the URL in your browser address bar. This also holds for new stock searches: you’ll be able to bookmark them, have them on your library website, link to them in emails or even from Facebook.

To prepare a new stock search, all you need to do is perform a search and then add a small snippet of text to the end of the address/URL. To allow you to have very broad sets of items included, we’ve added some new modifiers to the advanced search syntax:

  • collection
  • genre
  • languagecode
  • loantype
  • location
  • language
  • subject
  • dewey

These can be used just like the current modifiers: append a colon followed by a single word or, if searching for several words, surround them in quotation marks (e.g. subject:"Historical Drama").

If we look at one library who are beta testing the new stock search capability, I can enter a query for all items in their main catalogue by entering collection:"Main Catalogue" in the search box.

Search for collection:"Main Catalogue"

When you click on the “Search” button, the URL in the web browser address bar changes to:

http://prism.talis.com/demo/southwark/items?query=collection%3A"Main+Catalogue"

To turn this search into a new stock search just put the following snippet at the end of that URL:

&sort=shelveddate%3Ad&limit=10

This sets the sort order to recent shelved dates first and limits the number of records returned to a single page. The finished URL that you can bookmark/link to etc. now looks like:

http://prism.talis.com/demo/southwark/items?query=collection%3A"Main+Catalogue"&sort=shelveddate%3Ad&limit=10

Finally, you may have noticed in the list of new advanced search modifiers that you will be able to search by Dewey Decimal Classification. Some people have been asking if they can run searches on a sequence of classes; presently we only support searching on a single class, but we are investigating adding this capability in a future release.

If you have any questions on this, or any other issues, please feel free to email me phil.john@talis.com or your account manager (or comment here, of course).

Indicating copy status and the reserve function in the new release of Talis Prism 3

It can be helpful if the catalogue displays information about copies that are not yet ready for use. In the release that’s now on preview, Talis Prism 3 gives specific information about copies where the item status name in Talis Alto is one of: Order pending, Order sent, and Received. Copies at these statuses (and others) can be set to display or not by configuration in Talis Alto. In the latest release of Talis Prism 3 the default display text for these statuses is as follows:

  • Order pending – On order
  • Order sent – On order
  • Received – Awaiting shelving

For copies where the item status in Talis Alto is some other value, apart from In Stock/Loanable, the default display text in Talis Prism 3 is Please Ask.

Another improvement in the latest release of Talis Prism 3 is that the facility to place a reservation is now prominently situated in the availability area. In the preview, the default texts on the buttons before and after logging in are unchanged as ‘Login to request this book’ and ‘Request’, because changes to text take effect immediately in the live service. When this release goes live, those default texts will be changed to ‘Reserve this item’ and ‘Reserve’, to be more concise, more specific about the action and more general about the resource.

Some libraries charge for reservations. This can be indicated in the button text, for example ‘Reserve this item (£0.50 charge)’. To request any text changes, please raise a service request.

Prepared Searches, Links and New Stock

One of the great features in Talis Prism 2 is the ability to specify searches that you know will appeal to your users and let them get into exploring the catalogue. These prepared searches are one of the most asked about features for Talis Prism 3 so I wanted to take a little time to explain how Talis Prism 3 works, starting from the point of view of Talis Prism 2…

Setting up prepared searches in Talis Prism 2 was not a straightforward task, you had to work out the SQL query that would bring back the results you wanted then put that into webmin as a prepared search. SQL is not a friendly language and you then had to know how to construct a link for the search and add it into your prepared search list.

Only administrators could set up these searches and they had to be linked in Talis Prism 2 to make them useful.

We wanted to make things easier in Talis Prism 3 and we think we have.

Any search can be used as a prepared search in Talis Prism 3. All you have to do is perform the search you want to do, refine the search using facets, order the search results as you want them and grab the URL out of the address bar in your browser. No SQL, no webmin.

You can do a number of things straight away with that search URL, you can bookmark it in the browser (something you can’t do with Talis Prism 2 searches) or you can use it as a link in a document, or send it to a friend in an email. Any search in Talis Prism 3 is linkable. You can even submit them to Google for indexing, as a number of our customers have.

In Talis Prism 2 you had all your prepared searches listed on a prepared search page. With Talis Prism 3 you can put those links in any web page you like, anywhere on the web. In Facebook, perhaps or on your library blog. Of course, you can also add them to your homepage using Talis Prism 3’s homepage fragment.

What this approach means is that prepared searches can be easily put together by anyone, and used in far more flexible ways than Talis Prism 2 prepared searches. In Talis Prism 3 the feature is so simple we don’t even call them prepared searches… we just call them searches.

Of course, Talis Prism 3 is still evolving and we have work yet to do. We know that one of the very common cases for prepared searches is to highlight new additions to your stock (using the date received from the order history table). Right now the data model inside Talis Prism 3 does not track that date, in fact it’s not in the marc records that get sent over to us. We’re working on fixing that, and as it’s such an important feature to so many of you we’ve worked out how we can bring that development forward to this quarter and we’re aiming for a beta with a few customers by the end of March. 🙂

The next Talis Prism 3 Development Update Webinar  on 8th March will look to explore this functionality further, if in the meantime you would like further information please email Imraz.Mohammed@Talis.com.

Display of Notes

We have a question about the way we handle notes that we would like your help with – how notes display in Prism 3.

We’ve been looking at this because a few customers have asked for more of their notes to display on the item detail pages in Prism 3. At the moment only one note from the marc record is shown and it’s not predictable which one will be shown.

The reason notes don’t work well today is that the underlying data model for notes was designed for indexing and didn’t consider the needs of displaying notes properly. All notes from 500, 501, 502, 504, 505, 508, 511, 518, 520, 521, 533, 534, 536, 538, 545 and 550 are kept and indexed for search, unfortunately they are not kept in distinct properties and the order in which they were present in the marc record is not preserved.

In the Semantic Data Model work we have already designed new data structures for notes that will keep them distinct and maintain the ordering from the catalogue record – so longer term we will be addressing this issue much more cleanly.

What some of you have asked us to do in the meantime is to display all of the notes we have stored for indexing. This would display more of your valuable information to the user, helping them understand more about the item they’re looking at. On the downside, because of the limits of the data model, the order in which the notes are displayed would not be predictable and some notes such as the Summary, Contents and Performers notes may be repeated in the display.

We’ll be discussing this at the development webinar today and would very much like to hear your views on what is most preferable – more data, but with some repetition, or showing only one note as we do today. You can add a comment to this post, email terry.willan@talis.com, or bring your views to the development webinar.

To help you see what we mean we’ve put together some example screens showing how the notes would display. Click on each screenshot for a larger view of it.

  • Catch-22 (with publication history, summary and indexes notes)
  • Songs of Scotland (with contents and performers notes
  • Language proof and logic (with contents, accompanying material, indexes and system requirements notes)