Phil Norton

I've been happy with my Kobo Aura ebook reader since I bought it 8 years ago. It's light, has a crystal clear e-ink display, a decent back light, and the battery still lasts quite a long a while. I've read many books on it, most of which I have bought through the Kobo store. The DRM free service they provide is very convenient and give me access to a wide selection of books for a reasonable price.

When I go travelling I never take the Kobo Aura with me as it's a bit of an awkward size. It's larger than a phone and smaller than a tablet so it could easily fit into luggage, but it just never occurs to me to take it with me. I normally read ebooks on my phone via the Kobo app.

Importing content with the Default Content module is really useful when populating a site with content. There's an increasing number of recipes and modules that can be used to populate a site with content either for setup or demonstration purposes.

Default content is really useful when figuring out how a system works as it can show relationships between content types that are not always simple to discern through the site itself. It also has a place when deploying content between sites as you can package up some default content and include that in a deployment step.

Occasionally, you'll want to tweak the content that is imported for different situations; with the reasons why you would want to do this being numerous. It might just be that you have a demo site and you wanted to tweak the content imported to better tailor it for the user. You could have a single recipe that contains the content and want to alter that for a specific demo.

This is the fourth article in a series looking at migrating from Jadu into a LocalGov Drupal (LGD) site for the Central Bedfordshire site. 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.

Now it is time to move onto what became the most complex part of the Central Bedfordshire migration, which was moving directories data from Jadu to LGD. Directories were used on the Jadu site to store all sorts of information that included schools, the location of car parks, contact information of homecare providers, and even an a-to-z glossary of recycling. Clearly, this data served different purposes but all of this data was hand created and important to bring across during the migration work.

I've had a Raspberry Pi 5 with 16GB RAM sat on a shelf of my office for the last year so I decided to do something with it. It was originally intended to be used in an enclosure I had backed on Kickstarter, but that doesn't look like it will be released, so the Pi has been gathering dust.

Rather than just using the Pi in the open on my desk I like to put them in cases or enclosures. This makes sure they don't get damaged, but can also add additional features like cooling or extra drives and ports. I have a couple of different Raspberry Pi around the house, acting as network firewalls, or media servers so I'm familiar with different cases and allowing the use of NVMe drives.

Whilst looking for a decent case I stumbled upon the new Argon Industria HMI 7C enclosure with the 7 inch Touch Display 2. This case was compatible with the Raspberry Pi 5 and I just needed to also get a Raspberry Pi touch display 2.

This is the second article in a series looking at migrating from Jadu into a LocalGov Drupal (LGD) site for Central Bedfordshire. 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 second article we looked at reproducing Jadu URLs to create redirects for migrated content, even though the Jadu API doesn't contain any URL information.

Now that we have a the Jadu connection created and redirects working we can start tackling other aspects of the migration, so let's look at migrating the main content of the site from Jadu. We can pull structured pages of content out of the Jadu API and apply them to the structure of a LGD site, maintaining the same hierarchical structure and order of pages.