{"id":590,"date":"2018-05-30T19:05:26","date_gmt":"2018-05-30T07:05:26","guid":{"rendered":"http:\/\/deborahfitchett.com\/blog\/?p=590"},"modified":"2018-05-30T19:05:26","modified_gmt":"2018-05-30T07:05:26","slug":"ex-libris-company-product-updates-anzreg2018","status":"publish","type":"post","link":"https:\/\/deborahfitchett.com\/blog\/2018\/05\/ex-libris-company-product-updates-anzreg2018\/","title":{"rendered":"Ex Libris company \/ product updates #anzreg2018"},"content":{"rendered":"<p><strong>Ex Libris company update<\/strong><br \/>\nBar Veinstein, President Ex Libris<\/p>\n<ul>\n<li>in 85 of top 100 unis; 65million api calls\/month; percentage of new sales that are in cloud up from 16% in 2009 to 96% in 2017; 92% customer satisfaction<\/li>\n<li>Pivot for exploration of funding\/collaboration https:\/\/www.proquest.com\/products-services\/Pivot.html<\/li>\n<li>aim to develop solutions sustainably so not a proliferation of systems for developing needs<\/li>\n<li>looking at more AI to develop recommendation eg &#8220;high patron demand for 8 titles. review and purchase?&#8221;, &#8220;based on usage patterns, you should move 46 titles from closed stacks to open shelves?&#8221;, &#8220;your interloans rota needs load balancing, configure now?&#8221;, &#8220;you&#8217;ve got usage from vendors who provide SUSHI accounts you haven&#8217;t set up yet, do that now?&#8221;, algorithms around SUSHI vs usage.<\/li>\n<li>serious about retaining Primo\/Summon; shared content and metadata<\/li>\n<li>Primo VE &#8211; realtime updates. Trying to reduce complexity of Primo Back Office (pipes etc &#8211; but unclear what replaces this when pipes are &#8220;all gone&#8221;)<\/li>\n<li>RefWorks not just for end user but also aggregated analytics on cloud platform. Should this be connected\/equal to eshelf on Primo?<\/li>\n<li>Leganto &#8211; &#8216;wanting to get libraries closer to teaching and learning&#8217; &#8211; tracking whether instructors are actually using it and big jumps between semesters.<\/li>\n<li>developing app services (ux, workflow, collaboration, analytics, shared data) and infrastructure services (agile, multi-tenancy, open apis, metadata schemas, auth) on top of cloud platform &#8211; if you&#8217;ve got one thing with them very quick to implement another because they already know how you&#8217;re set up.<\/li>\n<li>principles of openness: more transactions now via api than staff direct action.<\/li>\n<li>https:\/\/trust.exlibrisgroup.com\/<\/li>\n<li>Proquest issues &#8211; ExL &amp; PQ passing the customer service buck, so to align this. Eg being able to transfer support cases directly across between Salesforce instances.<\/li>\n<\/ul>\n<p><strong>Ex Libris prodct presentation<\/strong><br \/>\nOren Beit-Arie, Ex Libris Chief Strategy Officer<\/p>\n<ul>\n<li>1980s acquisitions not part of library systems -&gt; integrated library systems<\/li>\n<li>2000s e-resource mgmt not part of ILS -&gt; library services platform (&#8216;unified resource mgmt system&#8217;)<\/li>\n<li>now teaching\/learning\/research not part of LSPs -&gt; &#8230; Ex Libris&#8217;s view of a cloud &#8216;higher education platform&#8217;<\/li>\n<li>Leganto<br \/>\n&#8211; course reading lists; copyright compliance; integration with Alma\/Primo\/learning management system<br \/>\n&#8211; improve teaching and learning experience; student engagement; library efficiency; compliance; maximise use of library collections<br \/>\n&#8211; Alma workflows, creation of OpenURLs&#8230;<\/li>\n<li>Esploro<br \/>\n&#8211; in dev<br \/>\n&#8211; RIMs<br \/>\n&#8211; planning &#8211; discovery and analysis &#8211; writing &#8211; publication &#8211; outreach &#8211; assessment<br \/>\n&#8211; researchers (publish, publish, publish); librarians (provide research services); research office (increase research funding\/impact)<br \/>\n&#8211; [venn diagram] research admin systems [research master]; research data mgmt systems [figshare]; institutional repositories [dspace]; current research information systems [elements]<br \/>\n&#8211; pain points for rseearchers: too may systems, overhead, lack of incentive, hard to keep public profile up to date<br \/>\n&#8211; for research office &#8211; research output of the uni, lack of metrics, hard to track output and impact, risk of noncompliance<br \/>\n&#8211; next gen research repository: all assets; automated capture (don&#8217;t expect all content to be in repository); enrichment of metadata<br \/>\n&#8211; showcase research via discovery\/portals; automated researcher profiles; research benchmarks\/metrics<br \/>\n&#8211; different assets including creative works, research data, activities<br \/>\n&#8211; metadata curation and enrichment (whether direct deposit, mediated deposit, automatic capture) through partnerships with other parties (data then flows both ways, with consent)<br \/>\n&#8211; guiding principles: not to change researchers&#8217; habits; not to create more work for librarians; not to be another &#8216;point solution&#8217; (interoperable)<br \/>\n&#8211; parses pdf from upload for metadata (also checks against Primo etc). Keywords suggested based on researcher profile<br \/>\n&#8211; deposit management, apc requests, dmp management etc in &#8220;Research&#8221; tab on Alma<br \/>\n&#8211; allows analytics of eg journals in library containing articles published by faculty<br \/>\n&#8211; tries to track relationships with datasets<br \/>\n&#8211; public view essentially a discovery layer (it&#8217;s very Primo NewUI with bonus document viewer &#8211; possibly just an extra view) for research assets &#8211; colocates article with related dataset<br \/>\n&#8211; however have essentially ruled research administration systems out of scope as starting where their strength is. Do have Pivot however.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Ex Libris company update Bar Veinstein, President Ex Libris in 85 of top 100 unis; 65million api calls\/month; percentage of new sales that are in cloud up from 16% in 2009 to 96% in 2017; 92% customer satisfaction Pivot for exploration of funding\/collaboration https:\/\/www.proquest.com\/products-services\/Pivot.html aim to develop solutions sustainably so not a proliferation of systems [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[291,290,296,299,298,297,277],"_links":{"self":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts\/590"}],"collection":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/comments?post=590"}],"version-history":[{"count":1,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts\/590\/revisions"}],"predecessor-version":[{"id":591,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts\/590\/revisions\/591"}],"wp:attachment":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/media?parent=590"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/categories?post=590"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/tags?post=590"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}