GeoNetwork 3
CC Attribution - NonCommercial - ShareAlike 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Gravin, Florent
The presentation will provide an insight of the new functionalities available in the latest release of the software. Publishing and managing spatial metadata using GeoNetwork opensource has become mainstream in many Spatial Data Infrastructures. GeoNetwork opensource 3.0 comes with a new, clean user interface based on AngularJS, Bootstrap and D3. Other topics presented are related to performance, scalability, usability, workflow, metadata profile plugins and catalogue services compliance. Examples of implementations of the software will also be given, highlighting several national European SDI portals as well as work for Environment Canada and the collaboration with the OpenGeoPortal project.
 Hello. So here today we're going to speak about Metadata Catalog, provided by GeoNetwork Open Source Solution. So I would like just to introduce that Metadata Catalog is, for me it should be the main entry point on every SDI, because it's the best way to reach your data, to find your data. So whatever the size of your SDI or whatever the layer you want to provide to people and whatever to who, just the catalog is here to help people to find your data. So it's really important because when you publish data, you want to promote them. You want people to know them and use them. And the best way to find them is to use the catalog. For example, even if you just like publish like 10 layers on a GeoServer, the get capabilities requests could be a way to find some layers. But a catalog provides really more tools to find because you can search your data. Every aspect of your data are indexed. You can perform research. And it's a very good way to find all data that are available. So that said, I will start the show. So I'm from Graven from camp to camp. So I've been working on GeoNetwork 3 for a while. And I will present during this talk the solution. GeoNetwork is an open source solution for metadata catalog. And what is really important this year about GeoNetwork, we just released a major version, the version 3.0. So we're really glad to provide this new version to all GeoNetwork users. And my speak will be about showing what's new in this version. So first, to start with an overview, I will speak about the search interface, the new map viewer, how to manage and edit your metadata, the admin console, and advance features. And I will provide some links to see how GeoNetwork 3 works in production instances. So first, a little bit of history. So here, the team of GeoNetwork developers. We meet every year in Balsena just for a code sprint and to share ideas about the vision of the solution. And two years ago, we were wondering what could be the next step for GeoNetwork. And we wanted to provide something really new and something really fresh. And we came out. Like we wanted just to build a new application. And we wanted to improve the user experience with the metadata catalog. Because it's not often the most exciting task for administrators or data managers. And yeah, we wanted to focus on the user experience, the user interface, and many things that could make their life a bit easier. So we started with a prototype two years ago. And we guys were pretty busy the two last years developing the version 3. So we decided it was convincing. And we wanted to move forward. We wanted to just jump in the trend of the new technologies, play with new HTML5 technologies, with easier styling, easier everything, faster layout. And we wanted to integrate those new libraries into our user interface. And so we started with this prototype. And we developed the admin console for our first project two years ago, then the editor. And then this year we focused for the release, a lot of the search, and the rich viewer interface. So thanks to all the customers that have funded this huge work. And let's jump into the new features of this version 3. So last min version, but the version 3 came out during April. What's really new? So the first thing that comes from your eyes when you see the new version is the new user interface. But it's not all the changements not just related to the interface. But it's the more thing that comes to every people's mind. So we wanted to focus on those parts, better user interface, a rich map viewer. So it's very important thing that we wanted to not be just a metadata search form, a metadata resist list. But we wanted also to provide you eyes and tools to exploit the data you're looking for. Because you are here to find data. And what we wanted you is to make you able to directly visualize your data, whatever the type there are. So I will come back to that afterwards. We work on the metadata view. So we really improve the way we render our metadata, so to show every details. And we work a lot on the editor and min. So I will show all this UI in the next steps. And what's important, we decided to move to AngularJS Bootstrap OpenAir 3 for our interface. Because we experienced that those technologies work way together on web mapping sites. So because there is a web mapping view in GeoNetwork, we wanted to follow that train. And it's pretty good for GeoNetwork that we have moved to those technologies. New requirements. So yeah, we don't support very old browser's versions. You need to move to Java 7 and things like that. So I'm focusing more about the UI. But during those two last years, huge improvements have been done to the core of GeoNetwork as well. So it's really important that I mention that to you, even if it's not maybe not concrete. But we are trying to make the core code of GeoNetwork really homogeneous and modular. So we divide all the core into different models. We're trying to integrate last spring framework. It's already there. But we're trying to move all our services to spring services, to remove the database connection to Ibanez and GPA. So our code is really more up to date, the core code, the Java code. And it's really easier to maintain and to get contributions. We work a lot also on optimization, on the search, on the search queries, the index, and many, many other improvements and backfixes. So searching the information. So it's the start of GeoNetwork users. So what is it? So we're just providing a new user interface for that. We provide new features like that it's really better for user experience is the routing. So it means just every search is stored. The history of your search is stored and binding with the URL. So like that, you can navigate through your browser's history and you're just navigating to your search history or what metadata you just viewed or things like that. So it's very useful. Customization, we put a lot of effort to let the users, not the users, but the developers of GeoNetwork. I mean, not the core developer, but people who want to get a new GeoNetwork and want to customize their view and want to customize their interface, we provide a huge effort to let them do. So the technology with bootstrap and everything, it makes them easier to customize with different styles or layouts. But our UI main code is based on an easy customization for those people who want. And for sure, a very important new feature for the UI is a rich map viewer. So let's just screenshot here. It's the homepage of the new GeoNetwork. So it's like before, you can find the same information, main input, because Google style, you want just to search from data, you have your data. We provided some classification. We want to just provide you entries for your catalog, classic entries like categories, topic categories, inspired terms, or different types of metadata. So that way, it's a very easy way for users just to jump in your data and look for what they want. Here, when you make your first research, you come here on the result page. So it's just an example of what the result page could look like. But as I told you, you can easily customize everything there. So if you want a form or faceties, things, or how do you want to show the result list. But here's just an example on this page. What's new here, compared to all versions, is the facet components. It's hierarchical faceties. So it's really useful for people who want to classify all their metadata in a hierarchical way. So everything is indexed and based on teresoryses if you want to organize your data like that. The metadata view. So here, it's just important that before, we used a service that parsed XML to render the metadata view. And now, it's pretty much faster. We just displayed the metadata from the index. So everything is stored client-side. So that way, we can just navigate to all the metadata sets with previous next. It's just instant. And we can render the metadata the way we want just by with layout or staining classes. So that point is really better. Now, the main map viewer. So as I told you, we wanted that people, they can just exploit the data they are looking for. So mainly, it's geo-network is a geospatial metadata catalog. So all the data are mainly geospatial. So one of the most pre-kined of data is WMS or Chef Filet, or things like that. And we just want them to be able to see the data they look for. So for us, the approach is geo-network is a metadata catalog and provides services, server-side, to manage your metadata. But client-side, we want that it's more than just a catalog. It could be sufficient to provide what you need from a simple SDI. So there is a way to look for your data, and there is a way to view your data. So I think it's all what people need and want when they just want to provide data. So here, it's a rich feature map viewer. So the last version, it was very simple, just a map. But there, you can find anything you want. Here, you can search for data that are stored in services of data catalog in geo-network. You can find it from WMS, WFS, KEMF, GeoGison. There is a layer tree. You can save your context, load context, draw, print. So everything is there if you need to. What I told you is that it's easy customizable. So when a customer wants a geo-network, he often wants to have specific styles, specific layout, and look. So it's really easy to just extend the default web page with components, with AngularJS directive, or with all the JavaScript code. Really easy to extend that and build your own view. Like build your own web form, build your own layout, and the way you want to display that. So here, it's an example. We can have another example. Pretty looks like the same as the default, but something like the radars, like the styles, the color, the size. Here is another example where it's kind of completely different, but you find the same thing just displayed in a different way. But here is an example of what your catalogue can look like very easily. So example of exploiting data and CWMS data, you can have different tools to exploit that to change the way you want to display the data. Here, for our customers, we also put cesium. You can activate the 3D mode or stay in 2Ds. So depending on the data you want to see. And the coming feature is going ahead with that. And if you have WFS or WPSSOS linked to your metadata, you will be able to exploit those services through the viewer. So WFS, you can already see every feature you have. If you have a process linked to metadata, you can launch this process to the viewer and exploit the data. And it would be the same from SOS. So now, the editor part. So it's the part for data management. And we focused also a lot on the editor to try to improve the user experience about how to edit their metadata. It's a bit complex in the geonetwork world because it has to respond to a lot of needs. And it has to be compliant to huge standards like ISO, different ISO things. We also come compliant with open data. So you can use geonetwork as an open data catalog as well. It's not very spread this way, but you really can do that. So here's how the editor looks like. So we put an report also to make it more understandable. And it's really easier to customize. Before, it was really hard to create a new profile, edition profile. Now, we just build an engine based on a config file where you can just pick what field you want to edit. And you can have different profile of edition on the same page and just pick the one you want. And it's going to just display the field you want to edit wherever there are deep in the metadata. So we provide by default an inspire editor as well. So it can be really useful for some people. So here, when you want to create a metadata, you choose the type. You can choose template. You create your new metadata. You arrive on this kind of editor with everything binding bound on the isoskemas. And on the right, you have different things like validation process, suggestion to help you to fill your metadata. We have tooltip and help on every field of the schemas. We have a wizard on the top right to help you to add resources to your schemas. There are new features like generating automatically the thumbnails from the WMS layer. So we just get the image and we put it as a thumbnail of the metadata and things like that. Multilingual editing, if you have multilingual metadata. So everything is managed there, like tetherers, keywords, all many different widgets and high level widgets to make really the edition really, really easier. The view, so the view is really important. We really focus on that. There is a new engine for rendering the metadata. So it's really easier for people who want their custom view. It's really fast. It's written in Groovy. And it's really small services. You can debug. Pretty efficient. And this came out with a caching system. So now if the metadata haven't been edited and the formator that's the engine that render the metadata have been already triggered, then the HTML response is stored. And you can have pretty fast all the rendering of the full metadata. So here it looks like. So we wrote a default formator. So it just displays all in the metadata document and displays all the fields. And you can also very easily customize these formators to have yours. And now at last, very briefly, the administration. So you just have to know also the console has been completely redesigned with different colors, different entry, and different visual effects to help you to find what you need. So very fast, new Arvester management system. So you can jump into different harvesting nodes and get some information. You have feedbacks. So everything has been really improved to make better user experience. And lots of things have been added also, new features, new stuff, like statistics about the usage of your catalog, the metadata, and things like that. So you can find this presentation online. There is some example of GeoNectar 3 that are already in production like that. You can see how we can customize the UI and things like that. You can see what it could look like and see maybe mine could look like that. Different challenges for coming next year and after. We have huge perspective coming on. And that's it. So thank you to you. And thank you to all contributors and to all people who contribute to the translation as well. And that's it. Thank you very much. Questions for Floren? Yes, Miguel, please. Hello? Yes. I have two small questions. The first one is about the map view. It now, I think it doesn't support shape files as a format. Are you planning to implement that in the future? It's not on the early schedule. Usually, shape, yeah, I don't really know what to say. Usually, you can have, on the metadata, it's linked to a WMS, and if you want to provide the data by itself, you just join a zip file containing the shape file, or things like that. Or you can use extractors to extract the data to shape file format from WMS services or WFS services. But we don't support the native shape file format in the viewer right now. Just geogison, KML, KMZ, and this one. And the second question is about those geospatial formats like KML or GeoJSON. They are stored on the server. Even if you have a Postgres database behind the geonetwork, are you also planning to convert and start on the database? Or you think of it? What do you mean? Usually, when there is a KML file linked to a metadata, it's an external link. Oh, it's in a, but it's also a way of uploading it, isn't it? Yeah, you can upload also resources. But it's another protocol. And if you upload a KML, you will be able just to download the KML. You have to tell what protocol it is. And if it's a KML protocol, you just need to provide a URL or thing like that to reach the file. OK, thank you. Yes, please. Hi, I'm Jorgen from Denmark, Danish Geodata Agency. We have an installation, an older one, a two-point something. If we want to migrate, what would you be your best advice? Should we migrate or should we stay at a point, two-point something? Yeah, all the migration process is managed by GeoNetwork. So I will advise you just to save your database, because we never know. And then just update your GeoNetwork vision, and it should migrate the database by itself. So the data model is the same underneath, or what? Yeah, it's compatible. OK, super. Thank you. And we have lots of feedbacks and experience back about that on the mailing list. So I would suggest you just to read some posts on the mailing list, because many people have done that recently. So you can find it there. Thank you very much.
 Hello.  So here today we're going to speak about Metadata Catalog,  provided by GeoNetwork Open Source Solution.  So I would like just to introduce that Metadata Catalog is,  for me it should be the main entry point on every SDI,  because it's the best way to reach your data,  to find your data.  So whatever the size of your SDI or whatever the layer you  want to provide to people and whatever to who, just the  catalog is here to help people to find your data.  So it's really important because when you publish data,  you want to promote them.  You want people to know them and use them.  And the best way to find them is to use the catalog.  For example, even if you just like publish like 10 layers  on a GeoServer, the get capabilities requests could  be a way to find some layers.  But a catalog provides really more tools to find because  you can search your data.  Every aspect of your data are indexed.  You can perform research.  And it's a very good way to find all  data that are available.  So that said, I will start the show.  So I'm from Graven from camp to camp.  So I've been working on GeoNetwork 3 for a while.  And I will present during this talk the solution.  GeoNetwork is an open source solution for metadata catalog.  And what is really important this year about GeoNetwork,  we just released a major version, the version 3.0.  So we're really glad to provide this new version to all  GeoNetwork users.  And my speak will be about showing what's new in this  version.  So first, to start with an overview, I will speak about  the search interface, the new map viewer, how to manage and  edit your metadata, the admin console, and  advance features.  And I will provide some links to see how GeoNetwork 3 works  in production instances.  So first, a little bit of history.  So here, the team of GeoNetwork developers.  We meet every year in Balsena just for a code sprint and to  share ideas about the vision of the solution.  And two years ago, we were wondering what could be the  next step for GeoNetwork.  And we wanted to provide something really new and  something really fresh.  And we came out.  Like we wanted just to build a new application.  And we wanted to improve the user experience with the  metadata catalog.  Because it's not often the most exciting task for  administrators or data managers.  And yeah, we wanted to focus on the user experience, the  user interface, and many things that could make their  life a bit easier.  So we started with a prototype two years ago.  And we guys were pretty busy the two last years  developing the version 3.  So we decided it was convincing.  And we wanted to move forward.  We wanted to just jump in the trend of the new technologies,  play with new HTML5 technologies, with easier  styling, easier everything, faster layout.  And we wanted to integrate those new libraries into our  user interface.  And so we started with this prototype.  And we developed the admin console for our first project  two years ago, then the editor.  And then this year we focused for the release, a lot of the  search, and the rich viewer interface.  So thanks to all the customers that have  funded this huge work.  And let's jump into the new features of this version 3.  So last min version, but the version 3 came out during  April.  What's really new?  So the first thing that comes from your eyes when you see  the new version is the new user interface.  But it's not all the changements not just  related to the interface.  But it's the more thing that comes to every people's mind.  So we wanted to focus on those parts, better user interface,  a rich map viewer.  So it's very important thing that we wanted to not be just  a metadata search form, a metadata resist list.  But we wanted also to provide you eyes and tools to exploit  the data you're looking for.  Because you are here to find data.  And what we wanted you is to make you able to directly  visualize your data, whatever the type there are.  So I will come back to that afterwards.  We work on the metadata view.  So we really improve the way we render our metadata, so to  show every details.  And we work a lot on the editor and min.  So I will show all this UI in the next steps.  And what's important, we decided to move to AngularJS  Bootstrap OpenAir 3 for our interface.  Because we experienced that those technologies work way  together on web mapping sites.  So because there is a web mapping view in GeoNetwork, we  wanted to follow that train.  And it's pretty good for GeoNetwork that we have  moved to those technologies.  New requirements.  So yeah, we don't support very old browser's versions.  You need to move to Java 7 and things like that.  So I'm focusing more about the UI.  But during those two last years, huge improvements have  been done to the core of GeoNetwork as well.  So it's really important that I mention that to you, even  if it's not maybe not concrete.  But we are trying to make the core code of GeoNetwork  really homogeneous and modular.  So we divide all the core into different models.  We're trying to integrate last spring framework.  It's already there.  But we're trying to move all our services to spring  services, to remove the database connection to  Ibanez and GPA.  So our code is really more up to date, the core code, the  Java code.  And it's really easier to maintain and to get  contributions.  We work a lot also on optimization, on the search,  on the search queries, the index, and many, many other  improvements and backfixes.  So searching the information.  So it's the start of GeoNetwork users.  So what is it?  So we're just providing a new user interface for that.  We provide new features like that it's really better for  user experience is the routing.  So it means just every search is stored.  The history of your search is stored and  binding with the URL.  So like that, you can navigate through your browser's  history and you're just navigating to your search  history or what metadata you just viewed or  things like that.  So it's very useful.  Customization, we put a lot of effort to let the  users, not the users, but the developers of GeoNetwork.  I mean, not the core developer, but people who want to get a  new GeoNetwork and want to customize their view and  want to customize their interface, we provide a  huge effort to let them do.  So the technology with bootstrap and everything, it  makes them easier to customize with different styles or  layouts.  But our UI main code is based on an easy customization for  those people who want.  And for sure, a very important new feature for the UI is a  rich map viewer.  So let's just screenshot here.  It's the homepage of the new GeoNetwork.  So it's like before, you can find the same information,  main input, because Google style, you want just to  search from data, you have your data.  We provided some classification.  We want to just provide you entries for your catalog,  classic entries like categories, topic categories,  inspired terms, or different types of metadata.  So that way, it's a very easy way for users just to jump in  your data and look for what they want.  Here, when you make your first research, you come here on  the result page.  So it's just an example of what the result page could look  like.  But as I told you, you can easily customize everything  there.  So if you want a form or faceties, things, or how do you  want to show the result list.  But here's just an example on this page.  What's new here, compared to all versions, is the facet  components.  It's hierarchical faceties.  So it's really useful for people who want to classify all  their metadata in a hierarchical way.  So everything is indexed and based on teresoryses if you  want to organize your data like that.  The metadata view.  So here, it's just important that before, we used a service  that parsed XML to render the metadata view.  And now, it's pretty much faster.  We just displayed the metadata from the index.  So everything is stored client-side.  So that way, we can just navigate to all the metadata  sets with previous next.  It's just instant.  And we can render the metadata the way we want just by  with layout or staining classes.  So that point is really better.  Now, the main map viewer.  So as I told you, we wanted that people, they can just  exploit the data they are looking for.  So mainly, it's geo-network is a geospatial metadata catalog.  So all the data are mainly geospatial.  So one of the most pre-kined of data is WMS or Chef  Filet, or things like that.  And we just want them to be able to see the data they look  for.  So for us, the approach is geo-network is a metadata  catalog and provides services, server-side, to manage  your metadata.  But client-side, we want that it's more than just a  catalog.  It could be sufficient to provide what you need from a  simple SDI.  So there is a way to look for your data, and there is a way  to view your data.  So I think it's all what people need and want when they  just want to provide data.  So here, it's a rich feature map viewer.  So the last version, it was very simple, just a map.  But there, you can find anything you want.  Here, you can search for data that are stored in services  of data catalog in geo-network.  You can find it from WMS, WFS, KEMF, GeoGison.  There is a layer tree.  You can save your context, load context, draw, print.  So everything is there if you need to.  What I told you is that it's easy customizable.  So when a customer wants a geo-network, he often wants  to have specific styles, specific layout, and look.  So it's really easy to just extend the default web page  with components, with AngularJS directive, or with all the  JavaScript code.  Really easy to extend that and build your own view.  Like build your own web form, build your own layout, and  the way you want to display that.  So here, it's an example.  We can have another example.  Pretty looks like the same as the default, but something  like the radars, like the styles, the color, the size.  Here is another example where it's kind of completely  different, but you find the same thing just displayed in a  different way.  But here is an example of what your catalogue can look  like very easily.  So example of exploiting data and CWMS data, you can have  different tools to exploit that to change the way you want  to display the data.  Here, for our customers, we also put cesium.  You can activate the 3D mode or stay in 2Ds.  So depending on the data you want to see.  And the coming feature is going ahead with that.  And if you have WFS or WPSSOS linked to your metadata, you  will be able to exploit those services through the viewer.  So WFS, you can already see every feature you have.  If you have a process linked to metadata, you can launch  this process to the viewer and exploit the data.  And it would be the same from SOS.  So now, the editor part.  So it's the part for data management.  And we focused also a lot on the editor to try to improve  the user experience about how to edit their metadata.  It's a bit complex in the geonetwork world because it has  to respond to a lot of needs.  And it has to be compliant to huge standards like ISO,  different ISO things.  We also come compliant with open data.  So you can use geonetwork as an open data catalog as well.  It's not very spread this way, but you really can do that.  So here's how the editor looks like.  So we put an report also to make it more understandable.  And it's really easier to customize.  Before, it was really hard to create a new profile,  edition profile.  Now, we just build an engine based on a config file where  you can just pick what field you want to edit.  And you can have different profile of edition on the same  page and just pick the one you want.  And it's going to just display the field you want to edit  wherever there are deep in the metadata.  So we provide by default an inspire editor as well.  So it can be really useful for some people.  So here, when you want to create a metadata, you choose  the type.  You can choose template.  You create your new metadata.  You arrive on this kind of editor with everything binding  bound on the isoskemas.  And on the right, you have different things like  validation process, suggestion to help you to fill your  metadata.  We have tooltip and help on every field of the schemas.  We have a wizard on the top right to help you to add  resources to your schemas.  There are new features like generating automatically the  thumbnails from the WMS layer.  So we just get the image and we put it as a thumbnail of the  metadata and things like that.  Multilingual editing, if you have multilingual metadata.  So everything is managed there, like  tetherers, keywords, all many different widgets and high  level widgets to make really the edition really, really  easier.  The view, so the view is really important.  We really focus on that.  There is a new engine for rendering the metadata.  So it's really easier for people who want their custom  view.  It's really fast.  It's written in Groovy.  And it's really small services.  You can debug.  Pretty efficient.  And this came out with a caching system.  So now if the metadata haven't been edited and the  formator that's the engine that render the metadata have  been already triggered, then the HTML response is stored.  And you can have pretty fast all the rendering of the full  metadata.  So here it looks like.  So we wrote a default formator.  So it just displays all in the metadata document and  displays all the fields.  And you can also very easily customize these  formators to have yours.  And now at last, very briefly, the administration.  So you just have to know also the console has been  completely redesigned with different colors, different  entry, and different visual effects to help you to find  what you need.  So very fast, new Arvester management system.  So you can jump into different harvesting nodes and get  some information.  You have feedbacks.  So everything has been really improved to make better user  experience.  And lots of things have been added also, new features,  new stuff, like statistics about the usage of your  catalog, the metadata, and things like that.  So you can find this presentation online.  There is some example of GeoNectar 3 that are already  in production like that.  You can see how we can customize the UI and things  like that.  You can see what it could look like and see maybe mine  could look like that.  Different challenges for coming next year and after.  We have huge perspective coming on.  And that's it.  So thank you to you.  And thank you to all contributors and to all  people who contribute to the translation as well.  And that's it.  Thank you very much.  Questions for Floren?  Yes, Miguel, please.  Hello?  Yes.  I have two small questions.  The first one is about the map view.  It now, I think it doesn't support shape files as a format.  Are you planning to implement that in the future?  It's not on the early schedule.  Usually, shape, yeah, I don't really know what to say.  Usually, you can have, on the metadata, it's linked to a  WMS, and if you want to provide the data by itself, you just  join a zip file containing the shape file, or things like  that.  Or you can use extractors to extract the data to shape file  format from WMS services or WFS services.  But we don't support the native shape file format in the  viewer right now.  Just geogison, KML, KMZ, and this one.  And the second question is about those geospatial formats  like KML or GeoJSON.  They are stored on the server.  Even if you have a Postgres database behind the  geonetwork, are you also planning to  convert and start on the database?  Or you think of it?  What do you mean?  Usually, when there is a KML file linked to a metadata,  it's an external link.  Oh, it's in a, but it's also a way of uploading it, isn't it?  Yeah, you can upload also resources.  But it's another protocol.  And if you upload a KML, you will be able just to download  the KML.  You have to tell what protocol it is.  And if it's a KML protocol, you just need to provide a URL  or thing like that to reach the file.  OK, thank you.  Yes, please.  Hi, I'm Jorgen from Denmark, Danish Geodata Agency.  We have an installation, an older one, a two-point  something.  If we want to migrate, what would you be your best  advice?  Should we migrate or should we stay at a point, two-point  something?  Yeah, all the migration process is managed by GeoNetwork.  So I will advise you just to save your database, because we  never know.  And then just update your GeoNetwork vision, and it  should migrate the database by itself.  So the data model is the same underneath, or what?  Yeah, it's compatible.  OK, super.  Thank you.  And we have lots of feedbacks and experience back about that  on the mailing list.  So I would suggest you just to read some posts on the mailing  list, because many people have done that recently.  So you can find it there.  Thank you very much.
PT6-08_0_143.png PT6-08_144_2099.png PT6-08_2100_3647.png PT6-08_3648_3695.png PT6-08_3696_5207.png PT6-08_5208_6671.png PT6-08_6672_11363.png PT6-08_11364_11555.png PT6-08_11556_13667.png PT6-08_13668_15623.png PT6-08_15624_16235.png PT6-08_16236_17039.png PT6-08_17040_19715.png PT6-08_19716_20699.png PT6-08_20700_20927.png PT6-08_20928_21335.png PT6-08_21336_21419.png PT6-08_21420_21611.png PT6-08_21612_21959.png PT6-08_21960_22703.png PT6-08_22704_23087.png PT6-08_23088_24767.png PT6-08_24768_24983.png PT6-08_24984_26375.png PT6-08_26376_28031.png PT6-08_28032_28163.png PT6-08_28164_28463.png PT6-08_28464_28931.png PT6-08_28932_29219.png PT6-08_29220_29363.png PT6-08_29364_29759.png PT6-08_29760_30035.png PT6-08_30036_36095.png PT6-08_36096_36192.png