{"id":202,"date":"2007-11-07T12:31:37","date_gmt":"2007-11-07T19:31:37","guid":{"rendered":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/?p=202"},"modified":"2007-11-07T12:31:37","modified_gmt":"2007-11-07T19:31:37","slug":"towards-a-total-resource-management-solution","status":"publish","type":"post","link":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/2007\/11\/towards-a-total-resource-management-solution\/","title":{"rendered":"Towards a Total Resource Management Solution"},"content":{"rendered":"<p>This session is about Talis&#8217;s approach to managing electronic resources. I met with Sarah Bartlett from Talis yesterday and had a chat about what they are doing in this area &#8211; they have a project called Xedio which is working with customers, and representatives from the sector to develop a product &#8211; and she invited me to join the group, which I was very happy to do. From my point of view it is an opportunity to feed into a potential product, as well as get a feel for how other sites are dealing with the issues in this area. I know a couple of the other non-Talis customers on the group, and it sounds like they have put together a good and well informed group.<\/p>\n<p>Project Xedio is a development project. Interestingly I just had a chat with Ross MacIntyre from MIMAS over coffee, and he mentioned a UKSG project to look at the issue of Knowledge Bases which underpin products in the e-resource area (Link Resolvers, Federated search, and of course, ERM) &#8211; it will be interesting to see what the Talis take on this is. I&#8217;m not sure whether the project Ross was talking about was the &#8216;<a href=\"http:\/\/www.uksg.org\/projects\/linkfinal\">Link Resolvers and the Serials Supply Chain<\/a>&#8216; that has just published its final report, which might be worth a look.<\/p>\n<p>The Xedio project is being run using the &#8216;<a href=\"http:\/\/en.wikipedia.org\/wiki\/Scrum_(development)\">Scrum<\/a>&#8216; methodology, which Talis has been using in it&#8217;s development recently (for Talis Engage and Zephyr). The advisory group is currently prioritising requirements and feeding back to Talis, after this there will be a Webinar for feedback and discussion.<\/p>\n<p>Now Chris Armstrong&nbsp; from &#8216;<a href=\"http:\/\/www.i-a-l.co.uk\/\">Information Automation<\/a>&#8216; is talking about eContent. He doesn&#8217;t like the phrase eContent, and feels it is unhelpful. He suggests that there is a myth that users are format agnostic &#8211; but he doesn&#8217;t believe this to be the case. He believes this is being used by Aggregators<br \/> to talk up their databases. He feels it is more useful to talk about e-journals and e-books. Although I agree with him partially &#8211; it is important that a student understands the difference between a peer reviewed paper published in a journal, and a book chapter, I think that the point that the article is &#8216;peer reviewed&#8217; is the important bit &#8211; not the format of publication.<\/p>\n<p>The JUSTEIS project showed that although levels of provision were quite consistent across different types of content, but levels of use were quite different &#8211; essentially Search engines got used, everything else wasn&#8217;t very used. Chris argues that we don&#8217;t solve this by &#8216;dumbing down&#8217; and bundling everything into a google type interface, but to teach users about the resources as part of Information Literacy. I don&#8217;t really agree with this &#8211; I think that Information Literacy has to apply when a user has found a resource and is assessing it, not at some pre-qualification level, where they only search &#8216;approved&#8217; resources.<\/p>\n<p>Chris hopes that Information Literacy will start to be taught at younger ages &#8211; specifically in the 16-18 age group (6th form students).<\/p>\n<p>Chris believes that e-books are going to become a serious scholarly medium &#8211; and e-book readers will become more significant, digitisation will grow (<a href=\"http:\/\/books.google.com\/\">Google Book Search<\/a>, <a href=\"http:\/\/www.opencontentalliance.org\/\">Open Content Alliance<\/a> etc.) and new models will become accepted using Social Software &quot;Blooks&quot;. Also social software for reading &#8211; e.g. <a href=\"http:\/\/bookglutton.com\/portal\/beta\">Book Glutton<\/a> (<a href=\"http:\/\/blog.bookglutton.com\/?p=21\">here is an explanation of how this works<\/a>)<\/p>\n<p>Now Frances Hall is talking about the experience of dealing with e-journals at the University of Wolverhampton. There are many models to subscribe to a single title, with different rights attached. There are different levels of management required &#8211; e.g. for free titles, aggregated titles etc. However, users are only interested in finding the content they want at any particular time.<\/p>\n<p>Frances is describing the &#8216;e-journals&#8217; lifecycle, and highlighting some of the issues &#8211; the complexity of deals on offer etc. At Wolverhampton in their workflows they differentiate between journals and e-journals because of the different requirements &#8211; although for e-books they have a better integration between e-book and print book workflows.<\/p>\n<p>In terms of setting up access, it tends to be the smallest resources that take up the most time &#8211; ones from suppliers not used to supplying the HE sector.<\/p>\n<p>Finally in the lifecycle they have &#8216;cancellations&#8217; &#8211; the Schools have the final say in theory, but the nature of some e-journal subscriptions, especially the &#8216;big deals&#8217; means that they have had cancellations for print titles that they have had to reinstate, because they aren&#8217;t allowed to cancel the print under the electronic license. The usage stats informing cancellations tends to be reactive rather than proactive.<\/p>\n<p>Even after cancellation, there are &#8216;post-cancellation&#8217; access issues where you need to ensure you continue to have access to any backfiles you have the rights to.<\/p>\n<p>I&#8217;m sitting here feeling rather smug, as think Imperial is doing a pretty good job at a lot of this (that&#8217;s not to say we have solved all these problems, but relatively we are doing well) &#8211; what we need is systems that help us with these problems, and allow us to do this work more efficiently.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This session is about Talis&#8217;s approach to managing electronic resources. I met with Sarah Bartlett from Talis yesterday and had a chat about what they are doing in this area &#8211; they have a project called Xedio which is working with customers, and representatives from the sector to develop a product &#8211; and she invited [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[16],"class_list":["post-202","post","type-post","status-publish","format-standard","hentry","tag-insight07"],"_links":{"self":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/comments?post=202"}],"version-history":[{"count":0,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/202\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/media?parent=202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/categories?post=202"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/tags?post=202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}