Working Better Together: Library, Publisher and Vendor Perspectives

Introductions

• Panelists– Moderator: Mary Somerville

– Library: Maria Collins– Vendor: Nicole Pelsinsky– Publisher: Aaron Wood

Overview

• Case Study: NCSU experience

• Publisher and Vendor Response

• Audience Q&A

Working Better Together: Library Case Study

Maria CollinsHead of Acquisitions &

Discovery, North Carolina State University

Libraries

Background

• Land-grant university• 34,000 students; 8,000

faculty• 2 main libraries plus 3

branches • Acquisitions &

Discovery– Centralized technical

services– Re-organized- June 2011– Moved to Hunt – Nov

2011

NCSU Organizational Culture

• Willingness to take risks• View failure as opportunity for

iterative growth• IT support for developing systems-

related solutions• History of partnerships

Partnership Example• Vendor/Partner:

YBP• Service: Shelf

ready• Benefit

– Less cataloging– More time for cross-

training– Solves space

concerns at Hunt

Partnership Example

• Vendor/Partner: EBSCO/Serials Solutions

• Service: Support for E-Matrix

• Benefit– Realize the benefits

of other data sources

– Compliment in-house services

Partnership Example• Vendor/Partner:

JISC, Kuali OLE, Publishers

• Service: GOKb• Benefit

– Large-scale collaboration

– Enhance data– Community focus

Partnership Example

• Vendor/Partner: ebrary and YBP

• Service: Demand-driven acquisitions

• Benefit– Transforming the

way we do things– Just in time access– Savings

Partnership Example• Vendor/Partner: OCLC and Serials Solutions

• Service: Record outsourcing

• Benefit– Collective brain

trust– Time-saving– Outsourcing

Partnership Example

• Vendor/Partner: Endeca

• Service: Discovery layer

• Benefit– Timely discovery

services for patrons

Tangible Results for NCSU

• Better data• Better linking• Better discovery• Better electronic

resource management

• Access to global information networks

• Freed-up local resources

Cultural Results for NCSU

• Workflow focused • Allowed for organizational change • Improved change management • Systems-culture • Flexible and open to innovations from

varied sectors

 

Best Practices for Collaboration

• Support iterative communication• Define deliverables• Be willing to experiment• Don’t over complicate • Handling exceptions is now core work• Focus on broader workflows

Best Practices for Collaboration

• Accept non-traditional solutions• Involve stakeholders• Knowing when to fold’em• Take advantage of community interest in

problems• Be aware of what’s going on

Value of Partnerships: Winning the Prize

Areas of Opportunity

• Ebook management

• Data support– Linked data– Standards– KB data

• Workflow support• Open Access

WORKING BETTER TOGETHER: LIBRARY, PUBLISHER AND VENDOR PERSPECTIVES

Charleston Conference 2013

PARTNERING BETWEEN SERVICE PROVIDERS AND LIBRARIES

Implementationso Process and overviewo Milestones and outcomeso Training and documentation

Trackingo ERMs = organizing documentation for your libraryo Administrative consoles = tracking and reporting

Maintenanceo Collections and holdingso Understanding the data foundation = knowledge bases

PARTNERING BETWEEN SERVICE PROVIDERS AND CONTENT PROVIDERS

Improving and Refining Datao Optimizing metadata mappingso Capitalizing on new and unique data elements o Data improvements

More Robust Linkingo Improving the OpenURL experience (i.e. IOTA initiative)o Direct linking

SERVICE PROVIDER (KNOWLEDGE BASE) AS INTERMEDIARY BETWEEN LIBRARY/PUBLISHERS

Library

Service providerContent

Provider

Patron?

Nicole Pelsinsky – MLIS, PMCManager of Global Implementation Servicesnicole.pelsinsky@proquest.comwww.proquest.com

Collaborative Efforts between Service Providers and Content Providers

Direct LinkingDiscovery services had tended to be reliant on link resolvers for the delivery of content. This was problematic for non-journal, non-book content, particularly the archival and multimedia content that Alexander Street provides. At the 2010 Charleston Conference, Summon and Alexander Street talked this through and direct linking was the result

Metadata Schema MappingsWhen Alexander Street first started sending track-level audio metadata to Summon, the mapping from Alexander Street’s MARCxml into Summon’s modified MODS was reliant on the overall MARC to MODS mappings, which were optimized for monographic and serial content, not component part content, such as tracks.

This resulted in lists of seemingly identical track results, since there was little metadata to differentiate them based on the mapping.

Alexander Street and Summon worked together to make the mapping inclusive of other publication-related fields, such as the 773 (Host Item Information), so that end users could differentiate based on album title, label, and release date

Database/Collection RecommenderSummon’s suggested specialized collections based on user searches are inclusive of multimedia databases and highlight Alexander Street music collections

Future Collaboration

So Many PossibilitiesEnhanced audio track search result display through cover art delivered through Bowker’s Syndetics

Inclusion of non-book, non-serial content in 360 MARC

Auto-activation of publisher collections in various knowledge base services, including Summon

Linked data

But What Collaborations Would Most Benefit You?

Questions?Maria CollinsMaria_Collins@ncsu.edu

Nicole PelsinskyNicole.Pelsinsky@serialssolutions.com

Mary SomervilleMary.Somerville@ucdenver.edu

Aaron Woodawood@astreetpress.com