1 / 8

Collaboration with Vendors: Participating in the Process

Learn how to collaborate effectively with vendors in the product development process, participate in library advisory groups, engage in community-wide groups, and achieve mutual goals. Gain insights on how to leverage your membership organizations and make your voice heard. Contact Adam Chesler for more information.

aeldridge
Download Presentation

Collaboration with Vendors: Participating in the Process

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. Collaboration with Vendors:Participating in the Process Adam Chesler American Chemical Society North Carolina Serials Conference April 15-16, 2004

  2. Pre-Alpha Test • Be vocal: don’t be shy about making observations/comments (includes compliments AND criticisms) • Note competitors’ products/services you like/dislike • Arrange visits (vendors on campus, at conferences) • Leverage your membership organizations or other vendors (eg, sub agent) to get word out about ideas/comments

  3. Alpha/Beta Test • Alpha stage: specs drawn up, and prototypes developed • Make your opinions known early and often • Get a head-start on being a beta-tester • Beta stage: testing (eg, a dry run) • Try out new service/product and supply feedback • Not all fun/games: have to spend time learning/using/assessing product • Ask for discount on finished product!

  4. Library Advisory Groups • Many vendors have them • Opportunity to take on-going role • In product development • In organization’s development • Will involve meetings and sometimes, travel (at a conference, at vendor’s office)

  5. Community-wide Groups • COUNTER (www.projectcounter.org) • Usage statistics • ARL, ACRL, ICSTI, NCLIS, STM, AAP/PSP, JISC, ASA, UKSG • NISO (www.niso.org) • Standards across industry • ALA, ASIS&T, ACS, Elsevier, ISI, EBSCO, Gale, ProQuest, OCLC, SIRSI, Infotrieve, Barnes & Noble • NFAIS (www.nfais.org) • Information aggregators • AEA, ATLA, BL, BIOSIS, CAS, HighWire, MMS, NLM, Ovid • NASIG (www.nasig.org) • library-oriented, but vendors actively participate/join/lead • ALA (www.ala.org) • Publisher/Vendor-Library Relations Interest Group • Joint committee w/ AAP • CLIR/PSP • Working group identifying shared concerns and leadership strategies

  6. Collaboration: Examples • Pricing • PEAK: Elsevier/University of Michigan, Vanderbilt, etc. • Publishing • Organic Letters: ACS w/ SPARC • BioOne: AIBS, Allen Press, SPARC • Project MUSE: JHU Press/Eisenhower Library • Standards • SISAC: development of EDI initiatives • Licensing • Faxon’s KLibrary: bibliographic/account management service • Distribution • Hosting: University of Toronto, OhioLINK, others • Archiving • LOCKSS: Stanford; numerous publishers • Mellon Foundation-based efforts (Yale/Elsevier)

  7. Mutual Goals • Collection and data about users/usage of content • Reliable, permanent archive • Providing service for readers, authors • Development of standards/best practices • Healthier, co-operative environment and better products/services

  8. Contact Information Adam Chesler Assistant Director, Library Relations/Sales 1155 16th Street NW Washington, DC 20036 (781) 381-2814 or (617) 230-3201 a_chesler@acs.org

More Related