How do you verify that 50,000 pieces of content have migrated successfully into your new Drupal 8 site? And keep your sanity? The Migrate QA module helps bring order to the process by providing a framework for managing the approval of migrated content, right on the target site. It reduces how many external spreadsheets you need for tracking migration issues. Designed to support an iterative migration process, so you don't have to worry about losing your notes when migrations are rolled back. This session will primarily cover how it is used by content approvers. It will also introduce developers to how to integrate into their migrations, and discuss future plans for the system. Module: https://www.drupal.org/project/migrate_qa Presentation Video: https://www.youtube.com/watch?v=VjgeZj9PR64

1. Introducing the Migrate QA Module
Make Migrating to Drupal 8 a Breeze

2. Session Overview
! Purpose
! What it looks like
! How to use it
! How to customize it
! Tiny bit of how it’s put together and how to set it up
! What’s next

3. Aims of Migrate QA

4. To answer:
Did it work?

5. ! All required content?
! Looks right?
! References intact?
! All data is correct?
Did it work?

6. To bring peace of mind to
the process of validating
a migration.

7. To bring peace of mind to
the process of validating
a migration.
While it’s being developed.

8. Origins - Before the System

9. Long term focus on
migrations

10. Started with small
migration

11. Used spreadsheets to
collaborate with QA team

12. Used spreadsheets to
collaborate with QA team
… Disconnected

13. Spreadsheet

14. Views for reviewing
migrated content

15. Lightweight flagging
system to identify content
that may have problems

16. The ideas began to form

17. Highlights of the system

18. The QA process
happens on the
target site

19. Supports an
iterative process

20. Configurable
(you can add
custom fields)

21. Content flagging, identifying
potential problems:
Scripts, inline styles, etc.

22. Let’s take a look at it already

23. Migrate Status tab

24. Migrate Status tab

25. Migrate Status tab

26. Migrate Status tab: Original URL

27. Migrate Status tab: Status

28. Migrate Status tab: Key Content

29. Migrate Status tab: Notes

30. Migrate Status tab: Tracker Tags

31. Migrate Status tab: Flags

32. Tracker Edit

33. Tracker Edit

34. About Tracker Types
! Trackers can be imported before the content migration.
! Tracker Types represent the origin of the tracker.
! “Crawled Links” for URLs gathered from a crawl.
! “Planned Media” for Videos and PDFs.

35. QA Views, Reports

36. Migrated Content Section

37. Migrated Content: Rows

38. Migrated Content: Rows

39. Migrated Content: Rows

40. Migrated Content: Filters

41. Migrated Content: Bulk Actions

42. Migrated Content: Flagged

43. Migrated Content: Media

44. Migrated Content: Media

45. Migrated Content: Not Migrated

46. Everyday Usage

47. The Cycle
ADJUST
MIGRATIONS UPDATE TRACKERS
REVIEW CONTENT
(RE)RUN
MIGRATIONS 01
02
03
04

48. 01 Run Migrations
A. Run content migrations
B. Run QA migrations

49. 02 Review Content
A. Use QA views to sort content. Examples:
a. Key content
b. List from marketing department
c. Memos section
B. Examine individual pieces of content

50. 03 Update Trackers
A. Edit trackers to add notes, tags, and set approval status
B. Return to QA views for continued review

51. 04 Update Migrations
A. Developer reviews QA lists for grouped issues
B. Developer adjusts migrations scripts and mappings

52. 05 Re-Run Migrations (Returning to step 1)
A. Content and QA migrations are rolled back and re-run
B. Trackers are still associated with the correct content
C. Continue with another round of content review, tracker updates, and migration revisions.

53. Customization
How To Make It Yours

54. Customize Available Tracker Statuses

55. Set the Tracker Types

56. Add Tracker Tags

57. Add Custom Fields

58. Customize Reports
! Add fields, remove fields
! Add filters, remove filters
! Reports are built using Views

59. ! Nodes and Media are demonstrated so far
! The same system can be used for anything that can be:
○ Referenced by entityreference fields
○ Displayed in views
! Examples:
○ Blocks
○ Taxonomy
○ Users
○ Paragraphs
Track more entity types

60. Entity Structure

61. Entity Relationship Diagram
TRACKER
FLAG
ISSUE
NODE
Issues Ref
Tracker Ref
CONNECTOR
Migrated Content Ref
Tracker Ref
MEDIA
1
2
3
4
Standalone Tracker Migrations
Content Migrations
QA Migrations
Manual Creations
4
2
2331
3
n
1
1
1
1

62. Configuration and
Setup

63. Drupal’s Migrate API is used for
the QA setup.
So developers have a consistent
framework for their work.

64. ! Tracker Migrations
! Connector Migrations
○ Use migration_lookup to maintain the connections between tracker and content
! Flag Migrations
○ Use a regex plugin to do the search
! Examples will be included in the module soon
QA Migrations

65. When to Add
Any time!
It can be added to migrations currently in development.

66. What’s next

67. Example Migrations

68. Documentation

69. Issues
● Entity type and relationships
already exist
● Todo: Streamline creating and
selecting Issues
● Todo: Group content by issue,
and by issue tags

70. UI Improvements
! QA views
○ Use facets instead of filters
○ Add CSV export
○ Enable inline editing
! Adjust detail display of Trackers: obvious headings, spacing between groups, make
code look like code, etc.
! Rearrange menus and tabs a little
! Make naming of things more consistent

71. Complete roadmap in
drupal.org issue
https://www.drupal.org/
node/3047025

72. Suggestions and Questions
BoF for followup discussion
3:15 in BoF room 4

73. Join us for
contribution opportunities
Friday, April 12, 2019
Mentored
Contribution
9:00-18:00
Room: 602
First Time
Contributor Workshop
9:00-12:00
Room: 606
General
Contribution
9:00-18:00
Room: 6A

74. What did you think?
https://seattle2019.drupal.org/sessions/introducing-the-migrate-qa-module
Take the Survey!
https://www.surveymonkey.com/r/DrupalConSeattle

75. Come see us at
BOOTH 201
David Lanier
dlanier@phase2technology.com
@nadavoid