Hi all,
I would like to discuss the UI of GeoNetwork and our strategy and policy towards changes. The background is that I notice that changes to the UI are handled through pull requests without enough care and without enough consultation with the PSC. I’ll try to describe my thoughts about the current UI, where we should go and what can be done to get there.
The current UI
With the move to using Bootstrap and Angular we have made good progress to allow people to customize their own GeoNetwork installation. Many parts of the applications have improved a lot and we’ve indeed invested a lot of time from an interaction designer (Max) who also looked at the esthetics. However, when you do a plain installation using the .war or installer, the homepage looks frightening to me. My first thought is “what the hell is this?” Lots of empty space, different size characters, grey areas and large picture symbols, small toolbar. Everything smashed together on a white board without consistent and attractive design. I’m serious here. The application is tremendous, it does almost everything anyone wants in a catalog. But I would be the first to run away if I wouldn’t know better…
We have no policy in place when it comes to suggested improvements, and no review process by a designer that is responsible for the final result. So we end up with pull requests that may work for one user, but damage the usability and visual appeal of the application. This is no offense to contributors, just a warning we need to be much more strict when it comes to accepting contributions. We are extremely welcoming to outside contributors, which is a great thing. But if we are not critical, the end result can be devastating. (Side note: We need contributor agreements signed from new contributors!).
We need to change this!!
Where should we go?
It is my conviction that GeoNetwork should be visually attractive when opened for the very first time after installation. I know users will likely change the UI, customize it further and put their own content. But the first impression should be good and should reflect the quality of the underlaying application.
This means that at least:
- The UI has some meaningful content. Think of an introduction explaining what GeoNetwork is, where can you find more information or assistance etc…
- Default templates should be loaded and the user should have the choice to load some sample data to get started. This has been available in older versions and now is a process that needs to be done after installation by the administrator. Meaning that the average user had to do things s/he may not have a clue about at this early stage of getting to know the application (and gone s/he is…).
- The installer should work for all OS’s and thus we need platform specific installers (wrappers) around the multi-platform installer. The installer should be able to load templates (of choice) and sample data and should also work from the command line.
- GeoServer with sample services should be an option, even though it is not a requirement.
What can be done to get there?
- When we make changes to the UI, especially to the Homepage, results and map, we should have a responsible designer that reviews the proposed improvements before proposing them for voting to the PSC. Only after these changes have been accepted by the PSC these changes can make it into a release. Our UI/UX designer Michel could take up this task from the end of April onwards. He already has experience with GeoNetwork and core developers may know him from the code sprint in Bolsena. Until then, Anton Bakker can start reviewing the UI, test and propose a number of smaller improvements.
- When making a release, after the code freeze we will allow the designer a couple of days to review and test the UI. We will also update and test the installer so we are sure the basic application is looking good and ready to go instantly after installation.
- We will maintain a Dockerfile so people can test a GeoNetwork instance by running a docker image that is configured with templates and sample data. This same Docker can be used in trainings.
Only when all of the above criteria and actions have been met / fulfilled, we will release a new version. I’m committed to put GeoCat staff time to this process and I am looking forward to hear from others.
Cheers,
Jeroen
Try GeoCat
Bridge©
An extension to ArcGIS© to instantly publish data and metadata on GeoServer, MapServer, PostGIS and GeoNetwork.
Jeroen Ticheler
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
Tel: +31 (0)6 81286572
http://geocat.net
Can’t find any email from Pierre Mauduit ? We should move that page