Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Oliver Pesch, EBSCO Information Services Project COUNTER and SUSHI: An Overview Oliver Pesch, EBSCO Information Services NFAIS Forum: Online Usage Statistics:

Similar presentations


Presentation on theme: "1 Oliver Pesch, EBSCO Information Services Project COUNTER and SUSHI: An Overview Oliver Pesch, EBSCO Information Services NFAIS Forum: Online Usage Statistics:"— Presentation transcript:

1 1 Oliver Pesch, EBSCO Information Services Project COUNTER and SUSHI: An Overview Oliver Pesch, EBSCO Information Services NFAIS Forum: Online Usage Statistics: Current Status and Future Directions Philadelphia, PA October 27, 2006

2 2 Overview Usage statistics – Background & overview of the need Project COUNTER – Purpose – Accomplishments – Acceptance SUSHI – The concept – The technology – Accomplishments and timeline The Future

3 3 Usage Statistics: The need Expanding scope of E-resources Usage seen as a measurement of value – Cost per use for collection management – Search counts to measure value of databases – Use counts to help measure impact of faculty research The need to collect usage data from the growing list of content providers

4 4 Usage Statistics: The problems Inconsistencies in counting – Terminology (what is a download) – What and when to count Inconsistencies in format – Each content provider has their own format – Different labels, columns and rows Inconsistencies in delivery – , versus phone request, versus FTP – Online versus paper – Amount of history offered – Timeliness

5 5 Non-profit organization includes librarians, publishers and aggregators Lead in the standardization of usage – How use is counted – How use is reported Consistent, credible, comparable

6 6 COUNTER Code of Practice Code of Practice first released Jan 2003 Release 2 released Jan 2006 Code of Practice Addresses: – Terminology – Layout and format of reports – Processing of usage data – Delivery of reports

7 7 COUNTER Usage Reports Journal Reports: – JR1: Full Text Article Requests by Month and Journal – JR2: Turnaways by Month and Journal Database Reports: – DB1: Total Searches and Sessions by Month and Database – DB2: Turnaways by Month and Database – DB3: Searches and Sessions by Month and Service Books and Reference Works: – Title Requests, Section Requests, Searches and Turnaways

8 8 Explicit report layout – consistent

9 9 Journal Report 1: Number of Successful Full-Text Article Requests by Month and Journal

10 10 Credible – COUNTER Audit Beginning 2007, an audit must be passed for a vendors service to be compliant Conducted by auditor certified accountant or by organization accredited by COUNTER At vendor expense

11 11 Usage Statistics: Still some problems COUNTER statistics provides excellent model and rules for usage statistics counting Libraries needed: – A more efficient data exchange model Current model is file-by-file spreadsheet download Background query and response model is more efficient and scalable

12 12 Usage Data Problems Expanding scope of E-resources Data proliferation (many content providers) COUNTER extremely helpful, but… – Lack of standardized containers – Time consuming to gather, assemble, report Usage consolidation applications help with assembling and reporting, not the gathering Hence, SUSHI (Standardized Usage Statistics Harvesting Initiative)

13 13 SUSHI Objectives Solve the problem of harvesting and managing usage data from a growing number of providers. Promote consistency in usage formatting (XML) Automate the process

14 14

15 15

16 16

17 17

18 18

19 19

20 20

21 21

22 22

23 23

24 24 SUSHI: A brief history The SUSHI Steering Committee – Nov Meetings between Cornell & Innovative – July 2005 – Cross-Industry Committee forms: Libraries Subscription Agents Content Providers Integrated Library System vendors

25 25 SUSHI: A brief history The SUSHI Steering Committee – July – Industry Committee forms: Cornell University – Adam Chandler Ex Libris – Ted Koppel EBSCO Information Systems – Oliver Pesch Harvard University – California Digital Library – Ivy Anderson Innovative Interfaces – Ted Fons Thompson Scientific – Patricia Brennan University of Washington – Tim Jewell

26 26 SUSHI: A brief history Technical Work – Fall 2005 – Technical Discussions First tests – Innovative and EBSCO & Swets – Early 2006 – Live Harvests University of Nebraska – Lincoln & EBSCO Washington State Univ. & Project Euclid – Spring 2006 – Migration to NISO as coordinating body – Steering Committee continues work – September 2006 – Draft Standard for Trial Use

27 27 NISO SUSHI Working Group Adam Chandler (co-chair), Cornell Oliver Pesch (co-chair), EBSCO Ivy Anderson, California Digital Library Patricia Brennan, Thomson Scientific Ted Fons, Innovative Interfaces, Inc. Bill Hoffman, Swets Information Services Tim Jewell, University of Washington Ted Koppel, Ex Libris

28 28 SUSHI Contributing Partners Founding Members: EBSCO Ex Libris Innovative Interfaces, Inc. Swets Information Services Thomson Scientific Newer members: Endeavor Information Systems Florida Center for Library Automation College Center for Library Automation (CCLA) from the State of Florida Community Colleges Otto Harrassowitz OCLC Project Euclid Serials Solutions SirsiDynix

29 29 SUSHI The Technology

30 30 SUSHI: What it is and Isnt What it is: – A web-services model for requesting data Replaces the users need to download files from vendors website – A request for data where the response includes COUNTER data Using COUNTERs schema What it isnt – A model for counting usage statistics

31 31 Web Services: the chosen approach for SUSHI Web services combine the best aspects of component-based development and the Web. Commercially accepted Widely supported (W3C) Secure … but first some definitions

32 32 Definitions XML Schema (XSD) A language for describing the structure and constraining the contents of XML documents. (reactivity.com glossary)

33 33 Definitions XML Schema (XSD) A language for describing the structure and constraining the contents of XML documents. (reactivity.com glossary)

34 34 Definitions Web Services Open, standard (XML, SOAP, etc.) based Web applications that interact with other web applications for the purpose of exchanging data. (lucent.com)

35 35 Definitions Simple Object Access Protocol (SOAP) SOAP is a lightweight XML based protocol used for invoking web services and exchanging structured data and type information on the Web. (oracle.com)

36 36 Definitions Web Services Description Language (WSDL) is an XML format published for describing Web services. (wikipedia.org)

37 37 Web Services: An example System A provides online information about companies. System B provides real-time stock quotations. Using Web Services, System A can integrate real- time stock quotes into their company data.

38 38 System BSystem A Real Time Stock Quotes (web service) Online Company Data Internet System A sends the stock symbol to System B. Stock symbol

39 39 System BSystem A Real Time Stock Quotes (web service) Online Company Data Internet System B returns the quote. All of this happens in milliseconds. Stock symbol Stock quote

40 40 System B System A Real Time Stock Quotes Online Company Data Internet Messages are formatted in XML, and the protocol used to communicate is SOAP (Simple Object Access Protocol). Stock symbol Stock quote SOAP

41 41 XML messages for SUSHI Report Request – Requester – Customer Reference – Report Definition Report Response – Requester – Customer Reference – Report Definition – COUNTER report as payload

42 42 SUSHI Architecture The next series of slides graphically show a SUSHI transaction – Library system requests a usage report – SUSHI client makes the request – SUSHI server processes request – SUSHI server prepares COUNTER report – SUSHI server packages and returns response – SUSHI client processes COUNTER report

43 43 Content ProviderLibrary Internet The Library and Content Providers systems are both connected to the internet. The Library and Content Providers systems are both connected to the internet.

44 44 Content ProviderLibrary SUSHI Client Internet The SUSHI client is software that runs on the librarys server, usually associated with an ERM system. ERM

45 45 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The SUSHI server is software that runs on the Content Providers server, and has access to the usage data.

46 46 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Request Internet ERM When the ERM system wants a COUNTER report, it sends a request to the SUSHI client, which prepares the request. ?

47 47 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Request Internet ERM The SUSHI request is sent to the Content Provider. The request specifies the report and the library the report is for. ? Request

48 48 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The SUSHI server reads the request then processes the usage data. ? Request

49 49 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The SUSHI server creates the requested COUNTER report in XML format. ? COUNTER

50 50 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM A response message is prepared according to the SUSHI XML schema. ? COUNTER Response

51 51 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client. ? Response COUNTER

52 52 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client. ? Response COUNTER

53 53 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The SUSHI client processes the response and extracts the COUNTER report. ? Response COUNTER

54 54 Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The extracted COUNTER report is passed to the ERM system for further processing. COUNTER

55 55 Report Request: Detailed View –

56 56

57 57

58 58

59 59

60 60 Report Response: Detailed View –

61 61

62 62

63 63

64 64

65 65

66 66

67 67

68 68

69 69 Example code for SUSHI client public static void GetReport() { ReportRequest request = new ReportRequest(); request.Requestor = new Requestor("11", "Requestor Name", request.CustomerReference = new CustomerReference(customerId, customer); ReportDefinitionFilters filters = new ReportDefinitionFilters(new Range(dateStart, dateEnd)); request.ReportDefinition = new ReportDefinition(filters, "Report 1 (J1)"); SushiWsClientProxy.SushiwsPort service = new SushiWsClientProxy.SushiwsPort(); ReportResponse response = service.RetrieveJournal1Report(request); }

70 70 Content ProviderLibrary SUSHI Server Usage Data SUSHI Client Internet ERM SUSHI is a Web Service which sends an XML Request to a content provider to obtain an XML response containing the usage report. ? Response COUNTER Request SOAP

71 71 Making it secure Follows Web Services conventions Levels – Secure SSL – Trusted Server can profile trusted clients Clients must deliver known customer ID – Authorization Information providers can introduce customer level authorization

72 72 SUSHI: Extendable & adaptable Built for flexibility Current SUSHI standard – Handles additional reports – Allows for systematic harvesting of usage from multiple institutions – Adapts to a variety of security models

73 73 COUNTER: Looking Ahead Implementation of the Audit Tuning the COUNTER Code of Practice for Consortia Research the need for new metrics – Unique Article Count Research the need for new reports – Track usage by date published? – Track usage at the item level? – Special reports for Consortia?

74 74 SUSHI: Looking Ahead Address any issues from trial use of standard Education and awareness Continued cooperation between SUSHI & COUNTER – NISO/SUSHI maintains the COUNTER XML Schema Address Additional COUNTER Reports – Books and Reference Works Address the needs for Consortia Promote and encourage the up-take of SUSHI!

75 75 Summary of Resources Project COUNTER – COUNTER Auditing Requirements and Tests – SUSHI Web Site – JURO: Journal Usage Report Online –

76 Thank you Oliver Pesch


Download ppt "1 Oliver Pesch, EBSCO Information Services Project COUNTER and SUSHI: An Overview Oliver Pesch, EBSCO Information Services NFAIS Forum: Online Usage Statistics:"

Similar presentations


Ads by Google