Skip to main content

Apache Zeppelin integration with Geonetwork

We've been exploring Apache Zeppelin as a way of providing a powerful and flexible analytical interface for Geonetwork and are pleased to announce beta integration with the Geonetwork login credentials.

Astun use Geonetwork 3.2 as our metadata portal, supplying metadata to local authorities and government bodies, for both INSPIRE and Enterprise use. A question our customers often ask is which metadata records are the most popular? Our Enterprise customers also have more detailed requirements, such as discovering which metadata records have been started but not finished, how many have been published and so on.

Geonetwork itself provides search and content statistics, but only to users with Administrative rights, and it's not always straightforward to extend these to include new search options.

Enter Apache Zeppelin!

From the blurb:
Apache Zeppelin is a web-based notebook that enables data-driven, interactive data analytics and collaborative documents with SQL, Scala and more.

It's possible to connect Zeppelin to PostgreSQL, which is the database we use behind the scenes to store not only the Geonetwork metadata, but also user information, metadata status, and so on. Therefore, we can use Zeppelin to interrogate the Geonetwork catalog using SQL, and do more analysis than is exposed by Geonetwork itself.



Zeppelin provides a safe, read-only front-end to the database, avoiding any concerns about data integrity. Query results can be displayed in a number of ways, so the end-user can choose the most appropriate chart type for their data. Users can embed their results in reports, or send links to colleagues, and can schedule query updates to ensure the reports are always up to date.

Integration with Geonetwork


The holy grail of this work is to seemlessly integrate Geonetwork and Zeppelin so that users don't have to log in to both packages, and maintain two sets of passwords. Eventually we also want to style Zeppelin so that it fits with the new, clean Geonetwork style, and link to it from the Geonetwork home page.

The first part of this wish-list is now complete! We commissioned GeoCat, as core Geonetwork developers, to build the necessary components, and a beta-version of this code is now available on GitHub. This can be configured to connect to a Geonetwork PostgreSQL database and will allow you to log in with your Geonetwork Administrative credentials.

Watch this space for further enhancements!

Comments

Popular posts from this blog

Astun Conference 2018

In late September and October Astun hosted two regional conferences in Bristol and Leeds. In the current environment it isn’t easy to persuade people in Local and Central Government to take a day out of their schedules and travel to to a conference, so getting over 70 delegates over the two days was a strong indication of the value that Astun brings to its clients. After a brief welcome from Steven Feldman (Bristol) or Dan Ormsby (Leeds) Mike Saunt, Astun’s founder and MD, gave a keynote entitled “Much ado about Mapping” Mike talked about Astun as a passionate company, passionate about geo, passionate about open, passionate about the cloud and fanatical about support. He ran through the way Astun’s offer had evolved in the last year with new features, an improved user experience, simplified administration, more automation of cloud deployment and most importantly major investments in testing, quality enhancement and reducing technical debt. Then Mike moved on to the direction of travel for…

QGIS 3.0: the time has come...

QGIS 3.0 was released in February, and although it's labelled an 'early adopter' release, with the long term release (LTR) available in October, there's plenty in it to excite not just the early adopters, but the rest of us too. We've had a chance now to have a good look at it, kick the tyres a bit and see what everyone has to say about it, so here are our thoughts.

There are a few big steps forward - for example 3D support and multiple map canvasses - and while many of the other changes are relatively minor on their own, put together they represent a major leap in usability and effectiveness. There's been work on consolidation, upgrades of core packages, efficiency and speed improvements, resulting in a slicker, easier to use and more tightly integrated application.

You could say that the 'easier to use' bit is the best thing about QGIS 3.0 - and when you think about it, that's not a description that could be applied to most application upgrades or…

Making home working work!

I was chatting to a personal acquaintance recently about work and we got on to the subject of home working. The organisation she worked for was going through a period of change and they were planning on moving some of their office staff to home working on a permanent basis. She was after my views on how we manage to make that work effectively at Astun. This blog, which is very much a manager's perspective, is what I told her!

Before we get on to to the two key themes of this blog - the Technical and Cultural - a quick bit about Astun first! 1. Astun's circumstances We employ around 21 people, of which 6 or so work from an office in Epsom, and the rest work from home on a permanent basis. From my home in Bristol, I line manage 13 of those people, 3 of which are office based, the rest primarily work in the UK, as far north as Tyneside & Lancaster and as far south as Southampton. I have one member of the team who is based in Seville in Spain.
2. Technical Use of technology is k…