1 / 35

From Shoeboxes to Mashups: ERMs and Decision Support

From Shoeboxes to Mashups: ERMs and Decision Support. Tim Jewell University of Washington NISO Conference: “Understanding the Data Around Us” November 2d Magnolia Hotel, Dallas. The “Shoebox”. “Shoebox” Data Elements. Journal Call Number Priority (1, 2 or 3) Price Location

efrat
Télécharger la présentation

From Shoeboxes to Mashups: ERMs and Decision Support

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. From Shoeboxes to Mashups:ERMs and Decision Support Tim Jewell University of Washington NISO Conference: “Understanding the Data Around Us” November 2d Magnolia Hotel, Dallas

  2. The “Shoebox”

  3. “Shoebox” Data Elements • Journal • Call Number • Priority (1, 2 or 3) • Price • Location • Duplicated? • Selector • Fund • Faculty consulted • Other Selectors Consulted

  4. Collection Development Context: • Financial • Chronic pressure on University and Library budgets • Increased importance of accountability and evidence to support decision-making • Market • E-journal “packages” • Licensing issues • Cancellation limits • Long-term access/archiving • Publisher consolidation • Organizational: the end of rugged individualism?

  5. Collection Development Support Applications • “Serials Cancellation” projects • “Databases” • Journals • Print • Electronic • Analysis of E-journal packages • Proposals/Offers • Periodic Re-analysis • Refocus Budgeting/Spending • All these tending to merge

  6. UW Serials Review Toolkit

  7. “Local” Journal Metrics • Cost/payment • Usage • Print • Electronic • COUNTER • Cost per Use • ILL use • Faculty data • Publications • Citations • Requests • Priority judgments

  8. “Global” Journal Metrics • Retail/List Price • ISI • Impact Factor • Emerging • Journal Cost-effectiveness • Eigenfactor • Usage Factor • MESUR • “150-200 Metrics” • Article: “The new metrics of scholarly authority” (Michael Jensen, Chronicle of Higher Education, June 15, 2007)

  9. But Don’t Forget • Fund Code, Selector • Package Information • Publisher • Cancellation Limits • Print vs. Online • Archiving/continuing access rights • Portico, LOCKSS coverage? • Subscribed vs. Nonsubscribed titles

  10. What reports or “views” do we want, with what comparisons? • Different for types of resources • Databases • Journals • Journal to Journal Comparisons • Package Comparisons • E-books • Different levels of analysis • “Selector” or Department • “Fund Group” or Broad Area • Campus • University • Consortium • Trends?

  11. From Usage Data Management to Serials Decision Support: Questions and Design Criteria • What data/metrics do we want? • Everything available/ “I want it all?” • How do we want to display/report it? • In all sorts of ways/ ”My way” • Where should data be organized and stored for optimal use? • Where best support for #1and #2 is available/”I want it easy”

  12. The Metrics Landscape: Products and Services • “Serials Service” Vendors • Serials Solutions • Ulrich’s Serials Analysis • 360 Resource Manager • SWETS • Scholarly Stats • Thomson Scientific • Journal Citation Reports • Journal Use Reports • ILS Vendors • ERMs from Ex Libris, III, SIRSI/Dynix

  13. Some quick takes on “metrics services” • ISI Journal Citation Reports • Impact Factor well-established • But open to question, reports not integrated with other data • Ulrich’s Serials Analysis System • Provides current pricing and subject categories • But only provides links to Impact Factor • Serials Solutions 360 Resource Manager • Provides peer comparisons/benchmarks • Not yet clear what else is provided • Journal Cost-Effectiveness • Relative Cost Index an interesting idea, • But sustainable? • EigenFactor • Interesting alternative using “page rank” approach, • But validated, sustainable?

  14. Scholarly Stats • Features • Relatively low-cost way to aggregate usage data • Well-designed reports • Most- and least-used journals • Analysis by package/platform • SUSHI support • Issues • No tie to payment information • Price paid • Fund codes • No tie to other metrics • Comprehensiveness and pricing

  15. ISI Journal Use Reports • Features • Includes multiple metrics: • Impact Factor • COUNTER Usage data • Publications • Citation • Flexible reporting • “Profiles” • Budget/fund codes? • Reports can be exported(?) • Issues • Must upload serials holdings data • Lacks some local information: • Prices Paid • License Information • Too tied to ISI journal coverage? • Lacks other metrics • Pricing model?

  16. The DLF Electronic Resource Management Initiative, Phase I

  17. License terms Trial Price Assess need/budget Order, Register Evaluate Catalog User feedback Digital Registry Usage stats Proxy server Review alternatives Gateway Review problems WebBridge Inform users Track problems Troubleshoot Manage changes Provide Training Investigate Evaluate Monitor Provide Access Contact info Provide Support Administer Payment, manage financials Setup contacts Customize interface Holdings management Set up usage statistics

  18. The DLF Electronic Resource Management Initiative, Phase II • License Expression • Professional Training in License Term Mapping (ARL/DLF collaboration) • ERMI/ONIX • E-Resource Usage Statistics • Protocol for automated delivery (SUSHI) • ILS/ERM Interoperability

  19. Integrating usage statistics into a collection assessment tool via Innovative’s ERM module NWIUG 2007 Created by Hana Levay levay@u.washington.edu and Diane Carroll carroldi@wsu.edu

  20. ERM Beta • Can now accept SUSHI feeds • UW using ScholarlyStats to gather • Easy to generate COUNTER-style reports within ERM • Brings in data from order records to calculate cost per use

  21. Project Muse Statistics Export Average cost per title = $26121/354 titles =$73.79

  22. A Close-Up View of Statistics Export CPU per title = Cost per title / Use for title CPU: Africa Today = $73.79/156 = $0.47

  23. Project Muse Order Record

  24. A Close-Up View: Project Muse

  25. WSU Serials Decision Database • Database designed for selectors to make a decision to add, cancel or renew a title • The complete serials decision database contains subscribed and unsubscribed titles • This example contains only subscribed titles so the same set of titles can be compared to results obtained only from Millennium • Handout 1: WSU Serials Decision Database • Row 1 – Source of the information • Row 2 – Label for data found in the columns

  26. Millennium Title, ISSN, Order record #, location, vendor, fund code, cost Access provider Ejournal coverage, Archival access and license restrictions Subscription agent Title, format purchased, subscription period, publisher, ISSN Scholarly Stats and publisher website Ejournal use statistics Calculated Cost per use What sources were included for assessment of subscribed titles?

  27. ILLiad Interlibrary loans borrowed (ILLiad), ISSN Web of Science Number of authored papers Number of papers referenced by institution’s authors Calculated information on the priority of the titles What sources included subscribed and unsubscribed titles?

  28. Steps in Creating WSU Reports • Create list of current subscriptions using Checkin Record • Create list of order records • Merge Checkin and Order records • Create list for Resource and License Record data • Add usage statistics and cost per use

  29. Create List challenges • Can not do one create list that will pull data from the Bib, Order, Checkin, Resource and License records. • Must do this report in stages and merge data to get information on each subscribed title on one line on a spreadsheet.

  30. Making Millennium more friendly for journal collection assessment Greater integration of data • Need to be able to download journal, provider, licensing restrictions, coverage and use data in a create list Expanded use of import function introduced with ERM • Can already load coverage information • Need the ability to upload data such as Web of Science use data, priorities, other local use information and link it to the checkin records

  31. III Millennium ERM • Features • Includes fund codes • Can include license terms • Includes price paid • Includes subscription period • SUSHI Support (automated intake) • Generates cost per use • Issues • Complex reporting steps • Limited flexibility • Cost per use not always meaningful • Support for alternate metrics?

  32. Revised Serials Collection Assessment Design Criteria • “I want most of it”, but especially . . . • Prices paid • Local “budget structure” data • COUNTER Stats • Alternate metrics • “I want it my way” • Customizable reporting • By “fund code” • By “platform” or “package” • Peer library comparisons/benchmarking • Sort, recombine, display as needed • “I want it easy” • Or at minimal time investment/ inconvenience . . .

  33. SUSHI Generalized? User Consolidated Statistical Reports Reports Interface Data Consolidation Consolidated Data ERM knowledge base Import (manual) SUSHI (automatic) Webinterface Webinterface Webinterface SUSHI SUSHI SUSHI Usage Metric A Metric B Usage Metric C Metric D

More Related