1 / 21

METRIDOC: A Framework for Managing and Exposing Library Event Data

METRIDOC: A Framework for Managing and Exposing Library Event Data. University of Pennsylvania Libraries. With the support of. METRIDOC University of Pennsylvania Libraries. Metrics start with a basic abstraction:. The Event. METRIDOC University of Pennsylvania Libraries.

jena-juarez
Download Presentation

METRIDOC: A Framework for Managing and Exposing Library Event Data

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. METRIDOC:A Framework for Managing and Exposing Library Event Data University of Pennsylvania Libraries With the support of

  2. METRIDOC University of Pennsylvania Libraries Metrics start with a basic abstraction: The Event

  3. METRIDOC University of Pennsylvania Libraries Viewing an Ejournal article. The Event as raw data xxx.xx.xxx.xxx|-|zucca|[26/Jul/2007:15:41:01 -0500]| GET https://proxy.library.upenn.edu:443/login?proxySessionID=10335905&url=http://www.csa.com/htbin/dbrng.cgi?username=upenn3&access=upenn34&cat=psycinfo&adv=1 HTTP/1.1| 302|0|http://www.library.upenn.edu/cgibin/res/sr.cgi?community=59| Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/418.9.1 (KHTML, like Gecko) Safari/419.3| NGpmb6dT6JXswQH|__utmc=94565761;ezproxy=NGpmb6dT6JXswQH; hp=/; proxySessionID=10335514; __utmc=247612227; __utmz=247612227.1184251774.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none);UPennLibrary=AAAAAUaWP5oAACa4AwOOAg==; sfx_session_id=s6A37A3E0-3B8E-11DC-80E985076F88F67F

  4. METRIDOC University of Pennsylvania Libraries Srvice Genre Library Parameters An Event Abstracted Cognzt Staff Orgn’l Unit User & Program Parameters Budget cntr Bibliographic Parameters College | Dept EVENT Rank Course Title Host College Date | Time URI Host Dept Environmental Parameters Location Format Instructor IP Domain Cost| Supplr Grant Spnsr URL

  5. METRIDOC University of Pennsylvania Libraries The “Event”is represented in machine-readable data, stored in a plethora of business systems. Event Types Source Target Link resolver Proxy server COUNTER ILS (Voyager, I3, Kuali-OLE) Resource sharing system Web server Social networking Srvs. Spreadsheets, databases Other targets… E-Resource Use by service, demographic, package Expenditures & Inventory planning / reader interest data Supply chain data Discovery systems & content use Research & instructional data learning management Other events…

  6. METRIDOC University of Pennsylvania Libraries MetriDoc Is a framework for : Extracting event data from systems Transforming those data into readable, normalized formats Loading transformed/normalized payload into a repository Supporting analysis through local and collaborative dissemination channels.

  7. METRIDOC University of Pennsylvania Libraries Improved Data Resolution Through Integration • Increased scope of sources • Synthesis of vectors, e.g. • Expenditure per use • Resources use by communities • Contextualized data with greaterstatistical dimension and descriptive power. • Collaborative assessment.

  8. METRIDOC University of Pennsylvania Libraries Our legacy system: Datafarm Perl Voyager cron Quaker Perl Perl Perl Perl Perl cron Perl Farmer App Logs Perl cron Perl

  9. METRIDOC University of Pennsylvania Libraries Datafarm Shortcomings • Maintainability issues • Scripts that depend on each other located in different places • Perl is very productive as long as you are maintaining your own code • Doing the same thing over again, no code reuse • Lack of notification for success and failure • Not shareable • No safe way to expose data for collaboration • Generating data for a report can be a job in itself • Schemas are not stored in a sharable format • Not reusable • Doing the same thing over and over again without building libraries for common tasks • No central code repository to share libraries within and outside of UPenn

  10. METRIDOC University of Pennsylvania Libraries

  11. METRIDOC University of Pennsylvania Libraries Current System: Metridoc Perl Voyager cron Quaker Perl Perl Perl Perl Perl cron Farmer Perl App Logs Perl cron Perl

  12. METRIDOC University of Pennsylvania Libraries Metridoc Philosophy

  13. METRIDOC University of Pennsylvania Libraries Scripting Framework

  14. METRIDOC University of Pennsylvania Libraries Scripting Example

  15. METRIDOC University of Pennsylvania Libraries Scripting Example

  16. METRIDOC University of Pennsylvania Libraries Exposing data

  17. METRIDOC University of Pennsylvania Libraries Metrics on the cheap (google charts)

  18. METRIDOC University of Pennsylvania Libraries Thoughts on complex statistics

  19. METRIDOC University of Pennsylvania Libraries The future

  20. METRIDOC University of Pennsylvania Libraries Abstracts 4 key functions, exposes interfaces for interoperability 1. Extract 2. Transform 3. Load 4. Query Target Source, e.g. Relais, Illiad, ILS Resolution Sources e.g. IdM, WorldCat Results Document Query Srvc Ingest Log Resolve Codes & IDs Normalize User Interface Parse Data Repo Format Refined output Refined output Local Data Stores Query Document

  21. METRIDOC University of Pennsylvania Libraries Partners are welcome Sponsor More at http://code.google.com/p/metridoc/

More Related