February 2010 – Talis Prism 3 Roadmap
Following a review of Talis Prism 3 development, we have published the February Talis Prism 3 Roadmap and Talis Prism 3 Feature List.
The next Talis Prism 3 Development Webinar has been scheduled for 8th March 2010 and will look to focus on the Talis Prism 3 roadmap. If you were unable to attend a webinar and would like a more detailed explanation around the roadmap, or have any questions, then please contact Alison.Kershaw@Talis.com.
February 23rd, 2010 at 9:44 am
Hi – Within the Improvements in Display of Availability Information, I’m interested in what you mean by “We will be looking at summary-level information for most users and making
copy-level information available for expert users” in terms of most users and expert users. I don’t think I’ve seen this distinction with regards to Prism 3 before, and wondered what it meant? Is the information going to be available for all to see on Prism?
Thanks
Jo
February 25th, 2010 at 12:40 pm
Jo,
Thanks for pointing that out, I didn’t realise we haven’t talked about that distinction before so I’ll expand a little here, but we’re also about to blog the intended design for availability so that will hopefully make things clearer as well.
We get a lot of great suggestions for Prism 3 from all of you (and we want to improve our handling of those, watch this space) and we incorporate those ideas into our design thinking. Some of those ideas are centered on particular situations or particular uses of Prism 3 – ideas that optimise for when someone is in the library building or being assisted by a librarian, for example.
Every feature added to a piece of software makes it more complex to use, so we are always treading the line between making Prism 3 more useful in a specific situation and making it more difficult for everyone the rest of the time. While just one small feature may not seem a big deal, and often it’s not for regular users, the build up of features over time can easily lead to an overwhelming experience for first-time and infrequent users. Prism 3 obviously has to cater for both.
That is the distinction we’re making above and hopefully a distinction you will feel we’ve handled well in the availability design when we blog that.
rob