Walk this way:
Online content platform migration
experiences and collaboration
Matthew Ragucci, Wiley
Xiaoyan Song, North Carolina State University
Athena Hoeppner, University of Central Florida
Meet the Presenters
Matthew Ragucci
Associate Director of Product Marketing
Wiley
Xiaoyan Song
Electronic Resource Librarian
North Carolina State University
Athena Hoeppner
Discovery Services Librarian
University Central Florida Libraries
@athenahoeppner
Agenda
• Introductions
• Publisher migration experience
• Librarian migration experience
• Content Platform Migration working group
• Timeline and next steps
Wiley’s platform perspective
Publisher migration experience
Wiley Platform Timeline
2008 2010 2016 2018 2020
Wiley acquires
Blackwell
Launch of
Wiley Online Library
Wiley acquires
Atypon
WOL moves to
Literatum
BRO moves
to WOL
ACSESS titles
move to WOL
Wiley Online Library migration to Literatum
• Move from homegrown to known product
• A long time coming…
• Cross-team collaboration required
• Leveraged external relationships
• Communications cadence and planning
• Hard cutover (less room for error)
Data exchange experience
• Redirects proved essential
(preferably in perpetuity)
• New linking for vendors
OpenURL parameters
KBART files
MARC records
Chapter and article-level metadata
• Proxy stanza updates
• CrossRef refresh
• Usage data (remained until 2019)
Resources
 Migration hub site
 Global email campaign
 Thorough technical FAQ
 Brief checklist
 URL Crosswalk document
 Trained support staff
Challenges
• Rolling launch date
• Finding the “right” person(s)
• Meeting all stakeholder needs
• Post-migration troubleshooting
• Did we do it right?
NC State University Libraries perspective
Library migration experience
Migrations at NC State Libraries
Start with Getting Notified
 Direct emails from publishers
 Listserves
 Notification from knowledge base
(KB) vendor
 Emails forwarded from
colleagues
 Issues reported by patrons
Assess the Impact
 When is it happening?
 What resources will be
impacted?
 Will they be redirected
permanently?
 What actions to take?
Take Applicable Actions
 Update MARC
records
 Communicate with
vendors to update
metadata/linking
Take Applicable Actions
 Update EZProxy
 Seek further clarification from
publishers
Take Applicable Actions
 Download usage
 Set up new administration accounts
 Inform public service librarians with
changes impacting our users
 Coordinate with internal colleagues
to update discovery systems and
tools
Snags
 Not always receive migration notice
 Challenge to identify records in ILS not coming from KB
 Problems with older contents
 Affected resources used by classes
 Migration during peak usage period
Our Wish
Seamless transition with minimal interruption to our users
CPM Working Group
How the Work Group Came To
Be
• NISO Information Policy and Analysis Topic
Committee sought ideas for new working
groups
• Kim and Athena members of IPA
• Duke U Press migrated
platforms in Nov. 2017
Publishers:
1 every 5-10 years
Content Platform Vendors:
5-10 per year
Librarians:
10+ per year and
(librarians reported over
content platforms
2016 to 2019.)
So Many Migrations
Alastair Rae / CC BY-SA (https://creativecommons.org/licenses/by-sa/2.0)
https://commons.wikimedia.org/wiki/File:Red-
billed_quelea_flocking_at_waterhole.jpg
Finding Participants
Develop a recommended practice to help
standardize the processes and provide
provide recommendations to improve
communications before, during and after
during and after migrations.
The Work Item
Geese flying in a row. Good Free Photos.
https://www.goodfreephotos.com/animals/birds/geese-flying-in-a-row.jpg.php
Investigate the state of migrations
• Interviews / Surveys /
Literature review
• Vendor communications and
checklists
• Timelines / Cycles / Decisions
L. Shyamal / Public domain. https://upload.wikimedia.org/wikipedia/commons/7/75/Migrationroutes.svg
Review related standards and organizations
• TRANSFER Code of Practice
• KBART/KBART Automation
• DOI/Crossref
• Authentication
• Usage (COUNTER & SUSHI)
ABCEditer / CC BY-SA (https://creativecommons.org/licenses/by-sa/4.0)
Stakeholder Perspectives and Experiences
• Publishers
• Content platform providers
• Libraries
• Other technology providers
Creative Commons Zero - CC0. https://www.pxfuel.com/en/free-photo-xcqry
Planned Deliverables
NPS graphic/ S. Sparhawk.. https://www.nps.gov/subjects/pollinators/images/Migration-cycle1.jpg
• Recommendations for publishers and
vendors to ensure migration addresses
librarians’ and end users’ needs
• Communication plan
• Checklists for publishers, vendors and
librarians
• Glossary of key terms
Timeline
General Timeline *
Appointment of Working Group Participants April – May 2019
Approval of Charge and Initial Work Plan May – June 2019
Information Gathering June – October 2019
Write Initial Draft October 2019 – July 2020
Comment Period August 2020
Completion of Final Draft September – October 2020
Publication and Promotion October – December 2020
* Dates subject to change
Questions?
mragucci@wiley.com
xsong9@ncsu.edu
athena@ucf.edu

Walk this way: Online content platform migration experiences and collaboration

  • 1.
    Walk this way: Onlinecontent platform migration experiences and collaboration Matthew Ragucci, Wiley Xiaoyan Song, North Carolina State University Athena Hoeppner, University of Central Florida
  • 2.
    Meet the Presenters MatthewRagucci Associate Director of Product Marketing Wiley Xiaoyan Song Electronic Resource Librarian North Carolina State University Athena Hoeppner Discovery Services Librarian University Central Florida Libraries @athenahoeppner
  • 3.
    Agenda • Introductions • Publishermigration experience • Librarian migration experience • Content Platform Migration working group • Timeline and next steps
  • 4.
  • 5.
    Wiley Platform Timeline 20082010 2016 2018 2020 Wiley acquires Blackwell Launch of Wiley Online Library Wiley acquires Atypon WOL moves to Literatum BRO moves to WOL ACSESS titles move to WOL
  • 6.
    Wiley Online Librarymigration to Literatum • Move from homegrown to known product • A long time coming… • Cross-team collaboration required • Leveraged external relationships • Communications cadence and planning • Hard cutover (less room for error)
  • 7.
    Data exchange experience •Redirects proved essential (preferably in perpetuity) • New linking for vendors OpenURL parameters KBART files MARC records Chapter and article-level metadata • Proxy stanza updates • CrossRef refresh • Usage data (remained until 2019)
  • 8.
    Resources  Migration hubsite  Global email campaign  Thorough technical FAQ  Brief checklist  URL Crosswalk document  Trained support staff
  • 9.
    Challenges • Rolling launchdate • Finding the “right” person(s) • Meeting all stakeholder needs • Post-migration troubleshooting • Did we do it right?
  • 10.
    NC State UniversityLibraries perspective Library migration experience
  • 11.
    Migrations at NCState Libraries
  • 12.
    Start with GettingNotified  Direct emails from publishers  Listserves  Notification from knowledge base (KB) vendor  Emails forwarded from colleagues  Issues reported by patrons
  • 13.
    Assess the Impact When is it happening?  What resources will be impacted?  Will they be redirected permanently?  What actions to take?
  • 14.
    Take Applicable Actions Update MARC records  Communicate with vendors to update metadata/linking
  • 15.
    Take Applicable Actions Update EZProxy  Seek further clarification from publishers
  • 16.
    Take Applicable Actions Download usage  Set up new administration accounts  Inform public service librarians with changes impacting our users  Coordinate with internal colleagues to update discovery systems and tools
  • 17.
    Snags  Not alwaysreceive migration notice  Challenge to identify records in ILS not coming from KB  Problems with older contents  Affected resources used by classes  Migration during peak usage period
  • 18.
    Our Wish Seamless transitionwith minimal interruption to our users
  • 19.
  • 20.
    How the WorkGroup Came To Be • NISO Information Policy and Analysis Topic Committee sought ideas for new working groups • Kim and Athena members of IPA • Duke U Press migrated platforms in Nov. 2017
  • 21.
    Publishers: 1 every 5-10years Content Platform Vendors: 5-10 per year Librarians: 10+ per year and (librarians reported over content platforms 2016 to 2019.) So Many Migrations Alastair Rae / CC BY-SA (https://creativecommons.org/licenses/by-sa/2.0) https://commons.wikimedia.org/wiki/File:Red- billed_quelea_flocking_at_waterhole.jpg
  • 22.
  • 23.
    Develop a recommendedpractice to help standardize the processes and provide provide recommendations to improve communications before, during and after during and after migrations. The Work Item Geese flying in a row. Good Free Photos. https://www.goodfreephotos.com/animals/birds/geese-flying-in-a-row.jpg.php
  • 24.
    Investigate the stateof migrations • Interviews / Surveys / Literature review • Vendor communications and checklists • Timelines / Cycles / Decisions L. Shyamal / Public domain. https://upload.wikimedia.org/wikipedia/commons/7/75/Migrationroutes.svg
  • 25.
    Review related standardsand organizations • TRANSFER Code of Practice • KBART/KBART Automation • DOI/Crossref • Authentication • Usage (COUNTER & SUSHI) ABCEditer / CC BY-SA (https://creativecommons.org/licenses/by-sa/4.0)
  • 26.
    Stakeholder Perspectives andExperiences • Publishers • Content platform providers • Libraries • Other technology providers Creative Commons Zero - CC0. https://www.pxfuel.com/en/free-photo-xcqry
  • 27.
    Planned Deliverables NPS graphic/S. Sparhawk.. https://www.nps.gov/subjects/pollinators/images/Migration-cycle1.jpg • Recommendations for publishers and vendors to ensure migration addresses librarians’ and end users’ needs • Communication plan • Checklists for publishers, vendors and librarians • Glossary of key terms
  • 28.
    Timeline General Timeline * Appointmentof Working Group Participants April – May 2019 Approval of Charge and Initial Work Plan May – June 2019 Information Gathering June – October 2019 Write Initial Draft October 2019 – July 2020 Comment Period August 2020 Completion of Final Draft September – October 2020 Publication and Promotion October – December 2020 * Dates subject to change
  • 29.