Managing Content Migration

Confab Higher Ed - Indianapolis, IN

Transcript

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

   View Slide

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.
   

   View Slide

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.
   

   View Slide

4. Web Governance is people being able
   to answer who can get things
   published on the institutional website.
   

   View Slide

5. Most of the information that exists
   about content migration comes from
   consultants.
   

   View Slide

6. Defining Migration v. Maintenance
   

   View Slide

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

   View Slide

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

   View Slide

9. ● Content inventory
   ● Author Permissions Audit
   ● Stakeholder Interviews
   ● Taking stock of the information architecture
   ● Eliminating Outdated Content
   Where Migration & Maintenance Intersect
   

   View Slide

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?
    

    View Slide

11. View Slide

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
    

    View Slide

13. View Slide

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
    

    View Slide

15. View Slide

16. View Slide

17. Avoid the pitfalls of overly
    complicating things.
    

    View Slide

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
    

    View Slide

19. What are your unique challenges to
    managing content & migration?
    

    View Slide

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

    View Slide