Agent 2.0: Channeling in E-Space ASIDIC Fall 2008 Meeting Salem, Massachusetts Tina Feick, Director of Sales

Easy!

Complex!?!?

It’s the E-World – Why isn’t still EASY?????????????? An Adventure Like Nothing on Earth Get Ready. Get Set. Get Lost.

WEB 2.0 Web 2.0 Business 2.0 Library 2.0

Web Wikipedia A tag cloud (constructed by Markus Angermeier) presenting some of the themes of Web 2.0.tag cloud

Agent 2.0 Focus Usability Design Participation = Partnership Economy Convergence Remixability = Interoperability Standardization

Brain Rules – Web 2.0 John Media, Brain Rules. Seattle, WA: Pear Press, Rule #4 – We don’t pay attention to boring things – No such thing as multitasking!! Rule #3 – Every brain is wired differently – Experience makes the difference. Rule #12 - We are powerful and natural explorers – Curiosity is everything! Rule #7 – Sleep well, think well.

Agent 2.0 – Gathering Data Database –Title Record - Added fields to record elements –Multiple format options –Publisher profile –Account profile –Increased costs

Pricing Data  All formats – print, P&E, e-only  All types – e-journals, databases, e-books  Subscriptions, backfiles, packages  DDP – Deep Discounted Pricing  Tracking Thousands of Prices – All Over the Map!!  Changing pricing policies  Our World is FULL of Spreadsheets

Services for Libraries TRADITIONAL –Online Database, Management Reports, EDI Invoicing & Claiming, Bibligraphic Updates BEYOND TRADITIONAL FOR LIBRARIES Aggregation – e-platforms A-Z e-journal title list programs Open URL resolvers Mini ERM systems License Banks Federated Searching Consortia Services Usage Statistics 11

Got Data – Need to Transfer Interoperability Requireswww.niso.org Standards! “A large stick or cudgel, used by the lightly more anal-retentive to beat the slightly less anal-retentive.” – The Devil’s Dictionary 2.0

DO YOU LIKE SUSHI? Z Standard Usage Statistical Harvesting Initiative 13

SUSHI - What it is? What it is: –A web-services model for requesting data Replaces the user’s need to download files from vendor’s website –A request for data where the response includes COUNTER data Using COUNTER’s schema –Load into ERM Systems What it isn’t: –A model for counting usage statistics –A usage consolidation application sushi 14

SUSHI ARCHITECTURE –Library’s consolidation client 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 15

COUNTER & SUSHI 21 Consolidators/Publishers committed to implement version 1.5 of SUSHI. (2 implemented now; 4 to earlier versions) COUNTER 3 (Journals and Databases) just announced –Includes SUSHI –Compliance by August 2009 –Extended –Revised XML Extended schema –Consortium reports 16

I2 (Institutional Identifier) Standard identifier for each institution Same identifier to be used across publishers and agents Define hierarchies and combinations (consortia) 17

SERU Recommended Practice (RP) Shared E-resources Understanding NISO RP Common understanding between publishers/platforms and libraries 22 publishers, 48 libraries NEW INITIATIVE – with EDItEUR – ONIX PL (Publisher’s License) – extension of License Expression Working Group - To load license elements into ERM 18

Agents Supporting Libraries & Partnering with Content Providers Back to BRAIN RULES for 2.0 Agents can multitask. Agents have the experience. Agents have the staff to explore options. Agents work while you sleep so everyone can think well! Agents need to have the flexibility to handle all business models. 19

THANK YOU! 20 Agent 2.0  Tina Feick