Presentation given at the Charleston Conference on November 3, 2011.  Information about Project Transfer (v. 2.0) for librarians and publishers

Bazeley, Jennifer W

Devenport, Tim

English

Scholarly Commons @ MiamiOH (Miami University)

Transfer 2.0 and Beyond! An UpdateCharleston Conference, November 2011Tim Devenport (EDItEUR) & Jennifer Bazeley(Miami University, King Library)OverviewContext• Journal transfers and unintended consequences• Feedback from customers and providersSo what to do about it?  • What is Transfer?!• The Transfer Code of Practice• But does it work?• A basic, but effective, alerting service• Spreading the word – communication & advocacy• Who’s on board?  Publishers endorsing TransferPutting it all to work• What the alerts look like• Integrating Transfer information into an e-resource workflowAnd looking ahead• Upgrading the alerting service• Topics under discussion right now• Getting involved – how you can profit from and contribute to TransferBright hopes & unintended consequences• Why journals migrate between publishers• It all seemed like such a great idea …• The “vulnerability” of e-resource access during transfers• Problems:– Interrupted access– Delayed access– Disappearing back files– Wrangling over entitlements– Changed login or authentication procedures– Admin load in fixing new or altered setups• Causes: – Poor communication– Different infrastructure– Missing or scrambled data– Lack of coordination or time– Competing or contrary motivationsFeedback from customers …• Anecdotally, and very publicly on the lists, librarians have drawn attention to the difficulties and frustrations they face with transferred titles• An ICOLC/Transfer survey* of librarians in May 2011 sought to analyze these concerns further:• 91.4% of librarians surveyed felt that the transfer of journals between publishers causes them “very” or “fairly” significant problems• Almost 50% of respondents spend a lot of time amending serials management systems and internal records as the result of transfers• The area where the highest percentage of respondents said they have often experienced problems was “subscription information” (delays in data being transferred to the new publishers, intermediaries not being informed)• When asked to list the two most significant transfer issues that cause them problems, librarians mainly cited access to current content and the time required to amend their systems. • Access to archives/backfiles, big deals, and pricing were also cited*164 respondents: 65% North America, 14% Europe, 14.5% Asia-Pacific… and from providers too• Publishers themselves also report problems with the transfer process• Quite apart from the attendant risks of disgruntled customers, bad press and the possibility of cancellation!• A Transfer survey* of publishers (in both “Transferring” and “Receiving” roles) in June 2011 surfaced a number of issues:• The area where the highest percentage of Transferring publishers had often experienced problems was the transfer of subscriber information. Over 70% of respondents sometimes or often had problems in this area.• Many Transferring publishers did not know whether there had been communication with a large number of third-part organizations, including A&I services and link resolver companies.• The areas where Receiving publishers had most often experienced problems were the receipt of subscriber information and content files.• 55% of Receiving publishers grace online access to existing subscribers for one month or more.• 60% of respondents did not have a central coordinator responsible for overseeing the transfer of journal publishing arrangements.*151 respondents: 34 commercial publishers; 8 nonprofits; 16 societies; 7 university pressesWhat is Transfer?!• A voluntary Code containing best practice guidelines for both Transferring and Receiving publishers• Supported (to date) by 36 publishers who publicly endorse the Code• An alerting service, communicating details of journals “on the move” to almost 400 registered recipients – mainly librarians• An ongoing, if informal, program of education and presentation to help different constituencies in the library supply chain better understand each others’ problems and priorities• Supported and championed by a small working group – 8 publishers, 5 librarians and 6 others – meeting once every two monthsThe Transfer Code of PracticeThe Code is now in a revised Version 2.0, and currently covers six main areas:• Access to the transferred title: – Includes ensuring continued access to customers where the Transferring publisher has granted perpetual access entitlements.• Provisions around digital content files: – Covers the transfer of digital files and spans both current (born digital) and archival (digitized from print) content, where available.• Subscription lists: – Covers early transfer of subscription lists and an outline of subscriber data types.• Journal URLs: – Covers transfer of journal-related domain name(s) and provision of a link or redirect to the new journal home page.• DOI name ownership: – Covers changes to Digital Object Identifier (DOI) name ownership.• Communication: – Covers communication to customers and relevant intermediaries. Customers here include recipients of electronic ToC alerts.But does it work?• By registering as Transfer compliant, publishers agree to abide – where commercially possible – by the terms of the Transfer Code of Practice– Remember: this endorsement and signup is entirely voluntary• Librarians and societies are increasingly requesting Transfer compliance in their licensing and contractual agreements with publishers• Other reports and initiatives (from JISC Collections and others) are citing Transfer and recommending compliance• Transfer’s recommendations provide a useful framework for overhauling internal procedures and encouraging a degree of “self regulation” on the part of publishers• But it’s hard to give the Code more “teeth” as we have to be careful to avoid any anticompetitive practices• And a recent informal list serv poll alerted us to several ongoing issues, some involving Transfer-compliant publishersA basic alerting service• Publishers provide a simple set of information items about the title transferred– Names of Transferring and Receiving Publishers & contact persons at both– Title and ISSN of journal being transferred– Effective transfer date– And some other information: see examples later• Wherever possible, contact points for both Transferring and Receiving publishers are included• Email alerts are generated and sent to subscribing recipients– Most recipients to date are librarians, but other players such as subscription agencies also interested on behalf of their customers• 215 journal transfers had been notified using this mechanism by Summer 2012 and more have followed• Simple but effective.  Doesn’t itself solve problems, but gives a pretty good heads-up that “this might be a title to watch!”Spreading the word• Transfer can only be effective if its recommendations are known and understood within the supply chain• So we like to take opportunities like this to brief diverse audiences and argue for wider uptake• We recognize that different players in the transfer process have different concerns and motivations• And try to tailor information accordingly for Publishers, Societies, and Librarians• Central control or coordination within the publishing house helps avoid problems and encourages prompt and effective communication to the market• Publishers need to be aware of the downstream effects of transfer operations, so that they can avoid or mitigate any problems that could arise• Societies are encouraged to support Transfer compliance, whether they self-publish or partner with commercial publishersPublishers endorsing TransferALPSPAmerican Diabetes AssociationAmerican Institution of PhysicsAmerican Psychological AssociationBerg PublishersBiomed CentralBrill PublishersCambridge University PressCo-Action PublishingEarthscan PublishersEdinburgh University PressElsevierEmeraldEuropean Respiratory SocietyFuture ScienceGUD PublishingIOPIOS PressLiverpool University PressManchester University PressNature Publishing GroupOxford University PressPalgrave MacmillanPier ProfessionalPortland PressRoyal Society of ChemistryRural Sociological SocietyRockefeller University PressSage PublicationsSociety for General MicrobiologySpringerSymposium JournalsTaylor & FrancisWalter de GruyterWiley BlackwellWolters Kluwer HealthPutting it all together• Practical uses for Transfer– What can librarians do with Transfer?• Encourage publishers that you buy from to endorse Transfer (if they don’t already)• Subscribe to the Transfer Notification list via e-mail– https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=TRANSFER• Use Transfer notifications in your day to day e-resource workflowE-Mail Account: My Transfer Listserv Folder My Library Subscribes to Circled TitlesInformation On Changes Communicated By PublisherRight-Click on the Flag and Choose “Custom”Custom Box: Click Arrow at Right of Due Date to Set Custom DateChoose Due Date: E-Mail Will Show Up in To Do List on This DateOptional: Add a Pop-Up ReminderE-Mail Appears in To-Do ListCheck E-Mail – Begin Process to Update Catalog Links for These TitlesUpgrading the alerting service• The basic alerting service “does a job” and is in daily use– Drop in some numbers– Put in a couple of very recent postings• But is somewhat restrictive and not very scalable• So enhancements were proposed by the Transfer team to UKSG• JISC funding was approved for an ETAS (Enhanced Transfer Alerting Service)• Encompassing improvements in the alerting service itself and putting in place a proper, searchable database to underpin and complement the service• MIMAS (based at the University of Manchester, UK) will host and run the service as part of JUSP (Journal Usage Statistics Portal)• ETAS has been designed and built: currently undergoing road trials for internal critique and sign off – should go live very soonShiny new services – ETAS preview!ETAS Search ResultsShiny new services – ETAS preview!Shiny new services – ETAS preview!Topics under discussion right now• Our work here is not done!• Suggested improvements or extensions under debate, beyond Version 2.0– Preservation is becoming a hot topic, both for the agencies involved and in registries of such services.  Should the Transferring publisher clarify whether content will remain a part of existing arrangements?– Transferring publishers could identify and pass on information about existing discovery services and link resolvers: should that be formally encouraged?– Should we research and suggest steps that publishers could take to ensure the continued discoverability of articles by search engines?– Similarly, might we consider including guidelines about redirecting social media sites and apps?– Subject to thinking through data protection issues, might Transferring publishers consider transferring email alerts, or at least contact registrants and provide a link for future sign up at the Receiving publisher?– More prosaically, should we more formally recommend use of the Transfer alerting service and its improved database?– Questions, questions!• In all this, we need to tread carefully around commercial sensibilities, whilst tapping into “community altruism”Getting involved: sign up & contribute!• Learn more about Transfer:– www.uksg.org/transfer• Sign up for the alerting service:– www.jiscmail.ac.uk/Transfer• Get in touch with any of the folks on the Transfer team:– Alison Mitchell (NPG), co-chair A.Mitchell@naturecom– Elizabeth Winter (Georgia Institute of Technology), co-chair– Tim Devenport (EDItEUR) tim@editeur.com– Jennifer Bazeley (Miami University, King Library) bazelejw@muohio.edu• And if you represent a publisher not yet on our august list – talk to us about endorsing the Code of Practice – which you’ll find at: http://www.uksg.org/Transfer/Code• Thanks for your interest and for helping us to help you!

Transfer 2.0 and Beyond! An Update

http://sc.lib.miamioh.edu/bitstream/2374.MIA/5120/1/Transfer_Charleston2011_pres.pdf

Transfer 2.0 and Beyond! An Update

Abstract

Similar works

Full text

Available Versions

Scholarly Commons @ MiamiOH (Miami University)