Today we are talking about Progressive migration with Drupal, What it is, and how you can do it with your organization with guest Stephen Cross. We’ll also cover Views JSON Source as our module of the week.

For show notes visit: www.talkingDrupal.com/466

• What is a progressive migration
• What other types of migration are there
• What problem does progressive migration solve at the ATF
• What versions of Drupal are involved
• Technical implementation
• Technical challenges
• Non-Technical challenges
• Processes needed for success
• When to use another migration process

• Drupal GovCon Presentation - Progressive Migration
• Talking Drupal #334 - Managing Drupal Teams in Government

Stephen Cross - stephencross.com stephencross

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Nate Dentzau - dentzau.com nathandentzau

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to use Drupal’s Views interface to allow visitors to browse and navigate data from another source? There’s a module for that
• Module name/project name:
  • Views JSON Source
• Brief history
  • How old: created in Apr 2020 by Pradeep Venugopal (venugopp), but recent releases are by Viktor Holovachek (astonvictor), a member of the Ukraine Drupal community
  • Versions available: 2.0.2 compatible with Drupal 8.8 and newer, all the way up to Drupal 11
• Maintainership
  • Actively maintained
  • Security coverage
  • Documentation: pretty lengthy README to help you get started
  • Number of open issues: 17 open issues, 4 of which are bugs against the current branch, although one had a fixed merged in the past week
• Usage stats:
  • 1,641 sites
• Module features and usage
  • After installing the module, you can create a view and specify it should show “JSON” instead of some kind of content entity
  • In the view settings you can then provide a URL for where to retrieve the JSON, and an optional Apath value to indicate a section of the data to show
  • It also supports contextual filters, so you can create a single view that will show different sections of data depending on the path used to access it
  • From there you can build out your view in the normal way: using fields to specify what data should be shown and how, filters to limit which rows will be shown, and sort criteria to specify the order in which it will be listed. And of course, the ability to expose controls for users to filter and sort the data in ways that meet their own needs make this an extremely powerful way to make data available to your site’s visitors
  • We spoke a couple of episodes ago about how powerful it can be to use Drupal as the “glass” or experience layer through which visitors can interact with other systems, and I think this is another great example of that