#! code: Drupal 11: Migrating From Jadu Into LocalGov Drupal: Part 2

Useful takeaways from this story.

In the first article we looked at the Jadu API and setting things up so that we could make calls to the API and parse the XML data using the migration systems available.

In the last article I mentioned something about the Jadu API that caused me a lot of headaches.

The API contains most of the information for a page, but critically, the Jadu API contains no information about the path of a page.

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

In the first article we looked at the Jadu API and setting things up so that we could make calls to the API and parse the XML data using the migration systems available. In the last article I mentioned something about the Jadu API that caused me a lot of headaches. The API contains most of the information for a page, but critically, the Jadu API contains no information about the path of a page.

How it works

I'm quire sure that this makes creating anything useful in the API a real pain since referring back to the site needs to be done with manually placed links, but it's clearly like this by design.
I couldn't find any documentation on why it is like this, but it almost feels like vendor lock-in.
Since I was migrating into a LGD site, it made sense to use the Drupal path auto system and LGD path management plugins to manage the paths on the Drupal site.
We therefore needed to know the existing Jadu URLs so that we could create these redirects.

Details worth keeping

This is critical to get right for a public facing council site like this.

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app