Skip to main content

Gemini 2.2 Profile for Geonetwork

By Anonymous
Astun are pleased to announce that we’ve released our implementation of the Gemini 2.2 metadata profile as an official plugin for Geonetwork 3.0.x and later versions, and that it’s now available at the official Geonetwork metadata profile site metadata101.org.

So what does this mean?


It means that you can use Gemini 2.2 as a metadata standard within Geonetwork for creating records that can be published to data.gov.uk or for your own use. Installation is easy, just follow the instructions at the repository, making sure you pick the branch that matches your Geonetwork installation.

By creating a separate plugin for Gemini 2.2, it can be used alongside other profiles such as Medin, and Gemini 2.3 when it’s released. You can ensure your metadata is stored and validated against the correct profile, and that you see the correct dropdown lists and hints when you’re creating or editing records.

We’ve made sure that the validation rules align with those used on data.gov.uk, so no more tiresome tooing and froing to ensure your records are correct. We’ve also tried to make the error messages a little more friendly too, so it’s easier to understand if things do go wrong!

What’s next?


We’re currently testing the Gemini 2.2 profile against Geonetwork 3.4.x, and all signs point towards it working just fine. As soon as we’ve finished fully testing everything, we’ll update the repository and documentation to take this into account.

When Gemini 2.3 is released we will begin testing a new plugin, with the new schematron rules and any additional changes. This will include tools for translating from Gemini 2.2 to 2.3. The timescale for this is dependent on the official release of the new standard and the guidance as to what should happen to existing metadata published under Gemini 2.2.

Labels:

Comments

Post a Comment

Popular posts from this blog

Improving project documentation with a codesprint

By Anonymous
Background  At the end of November I was asked by Francois Prunayre at Titellus to help organise and manage a 3-day code-sprint with the aim of improving GeoNetwork documentation . Documentation can be problematic for projects, even open source, where the majority of the work is done by volunteers. Updating documentation is rarely a priority for developers, who are time-poor and have actual project issues to deal with, and efforts to widen the base of contributors so that others can help, also take time. Back to the code-sprint This code-sprint was timed very well though, as it comes on the back of work being done to update GeoNetwork documentation as part of OSGeo's participation in Google's Season of Docs . This pairs a paid technical writer with an open source project for either three or six months, with the aim of seeing a rapid improvement in that project's documentation. I'm an admin and mentor for OSGeo on Season of Docs, so was well-placed to provide inp...
Post a Comment
Read more

Reflections on the Amazon Web Services Summit, 2018

By Anonymous
Last month, a handful of us from 'operations' attended the AWS Summit to keep up to date with what is going on in the Amazon Web Services world.  We've shared our reflections in this Blog and linked through to videos or slides of the sessions where we can. What is the AWS Summit? Amazon run a series of global events in major cities around the world getting to each one every couple of years; 2018 was London's turn. Amazon Web Services (AWS) is a cloud hosted computing platform, that Astun use for pretty much everything.  Our own cloud products and services such as iShare in the Cloud, Astun Data Services, Geonetwork / INSPIRE are all hosted there.  Even if what you use from us is exclusively deployed on your own premises, all of software development and most of our internal IT is done in the AWS environment.  It is critical to our business.  If you think that we are putting all our eggs in one basket, it is worth remembering that AWS is a $22 billion p.a. ...
Post a Comment
Read more

QGIS 3.0: the time has come...

By Anonymous
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 upgrad...
2 comments
Read more