Managing Content Migration

Cf646ba7fe1adf2bd8d52907a3c506f2?s=47 Ron Bronson
November 08, 2017

Managing Content Migration

Confab Higher Ed - Indianapolis, IN

Cf646ba7fe1adf2bd8d52907a3c506f2?s=128

Ron Bronson

November 08, 2017
Tweet

Transcript

  1. Tackling Content Migration & Maintenance Ron Bronson Confab Higher Ed

    2017
  2. About Ron Bronson • City webmaster & service designer, Bloomington

    (IN) • Founder of Indiana Design Week & Lead of IxDA Indianapolis • Over a decade in .edu & government. • Finnish baseball fan, brunch enthusiast, Skeeball professional.
  3. The fallacy of good experiences: Notion that people like engaging

    with our content/platforms and thus we should keep doing things the way we’ve always done them.
  4. Web Governance is people being able to answer who can

    get things published on the institutional website.
  5. Most of the information that exists about content migration comes

    from consultants.
  6. Defining Migration v. Maintenance

  7. Content Migration: Conversion, reorganization and/or consolidation of existing content to

    new platform or infrastructure.
  8. Content Maintenance: Processes and operations of existing web content infrastructure.

  9. • Content inventory • Author Permissions Audit • Stakeholder Interviews

    • Taking stock of the information architecture • Eliminating Outdated Content Where Migration & Maintenance Intersect
  10. • Identifying the content • Audit • Inventory • Assigning

    responsibility • Measurement/analytics to determine relevance • (Keep/Cull/Rewrite) • What artifacts are we using? • How do we get non-technical stakeholders to care. What are you migrating for?
  11. None
  12. • Lack of expertise devoted exclusively to content. • Too

    many moving parts. • People lacking the authority to engage the people necessary to move the project forward. The Challenges of Managing Content
  13. None
  14. • Migrated only the top 500 pages (along with attachments)

    • Developed a separate system for Board/Commission/Agendas not housed in web CMS • Anyone w/ an account can edit pages • New pages controlled by IT department Moving Migration Forward
  15. None
  16. None
  17. Avoid the pitfalls of overly complicating things.

  18. • Assess what the most important pieces are • Don’t

    try to tackle everything at once • Recognize your constraints ◦ Institutional ◦ Internal ◦ Departmental • Understand what matters • Spare the details Moving Migration Forward
  19. What are your unique challenges to managing content & migration?

  20. Kiitos! ron@ronbronson.com ronbronson.com