Rethink geo/open metadata edition in GeoNetwork
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 266 | |
| Author | ||
| License | CC Attribution 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 purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/66529 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Process (computing)AdditionPlanningSoftwareUMLLecture/ConferenceMeeting/Interview
00:21
MetadataPlanningBus (computing)Multiplication signLibrary catalogLecture/Conference
00:38
Disk read-and-write headMaizeMetadataVideo gameMultiplication signDisk read-and-write headComputer animation
01:01
MetadataSoftwareText editorMereologyGeometryMachine visionOpen setPhase transitionLibrary catalogLecture/ConferenceMeeting/Interview
01:41
Pulse (signal processing)Web portalText editorGeometrySoftwareOpen setLibrary catalogMetadataLevel (video gaming)Traffic reportingCapability Maturity ModelDomain nameLecture/ConferenceMeeting/InterviewComputer animation
02:36
Group actionLibrary catalogOpen setLecture/Conference
03:04
Service (economics)Text editorService (economics)Strategy gameUser interfaceComputer animation
03:25
Text editorRhombusArchitectureText editorAdditionMetadataExterior algebraOpen setCASE <Informatik>Video gameFront and back endsDialectGeometryLecture/ConferenceMeeting/InterviewComputer animation
04:15
Process (computing)Open setLibrary catalogGeometryLecture/ConferenceMeeting/Interview
04:34
MaizeRhombusArchitectureLibrary catalogComputing platformOpen setSatelliteSoftwareText editorMetadataComputer animation
05:15
MetadataSoftwareLecture/ConferenceMeeting/Interview
05:33
Text editorAuthoring systemKolmogorov complexityMetadataAbstractionMultiplication signInterface (computing)Field (computer science)Form (programming)AuthorizationSoftwareExpert systemCartesian coordinate systemGeometryComputer animation
06:36
UsabilityInterface (computing)User interfaceUsabilityMetadataRow (database)Self-organizationText editorLecture/ConferenceComputer animation
07:00
Different (Kate Ryan album)Text editorMultiplication signHeegaard splittingDirection (geometry)Process (computing)Lecture/ConferenceMeeting/Interview
07:19
Text editorMetadataData conversionGeometryProjective planeSoftwareLine (geometry)Process (computing)Machine visionText editorComputer animation
07:44
Data conversionMetadataText editorMachine visionFile formatPivot elementoutputFunction (mathematics)Machine visionBlock (periodic table)Text editorSoftwareProjective planePrototypeWordMarkup languagePivot elementFile formatGoodness of fitMereologyLecture/ConferenceMeeting/InterviewComputer animation
09:10
Text editorMachine visionFile formatPivot elementoutputFunction (mathematics)Core dumpMultiplication signGauge theoryLecture/ConferenceMeeting/Interview
09:26
Field (computer science)Text editorGroup actionIterationProcess (computing)MetadataFile formatPivot elementData conversionComputer networkAnalog-to-digital converterIntegrated development environmentDefault (computer science)Configuration spaceSystem administratorBuildingBlock (periodic table)Decision theoryElectronic mailing listMaxima and minimaTotal S.A.Library catalogText editorField (computer science)File formatMathematicsSheaf (mathematics)Arithmetic progressionForm (programming)2 (number)Data conversionMereologyPivot elementDifferent (Kate Ryan album)System administratorWordData storage deviceMarkup languageAbstractionOcean currentCondition numberRight angleReal numberTouchscreenSelf-organizationMetadataGroup actionLibrary catalogSoftware testingExpert systemInformationMultiplication signFront and back endsFunctional (mathematics)Structural loadRow (database)Interface (computing)Flow separationSoftwareWeb browserBlock (periodic table)Integrated development environmentCodeDebuggerDefault (computer science)Complex (psychology)Process (computing)Transformation (genetics)Relational databaseMachine visionDatabaseDependent and independent variablesBuildingControl flowComputer architectureGeometryCartesian coordinate systemDemo (music)Real-time operating systemLecture/ConferenceComputer animationProgram flowchart
17:26
MetadataExpert systemText editorComplex (psychology)WordSoftware developerCodeLecture/ConferenceMeeting/Interview
18:13
Text editorComputer configurationCodeProduct (business)Revision controlExterior algebraText editorSoftwareGeometryMachine visionLecture/ConferenceMeeting/Interview
18:38
Text editorComputer configurationMetadataText editorComplex (psychology)Extension (kinesiology)Configuration space2 (number)Sheaf (mathematics)Lecture/Conference
19:04
Text editorComputer configurationComputing platformLevel (video gaming)File viewerMetadataDisintegrationFreewareModul <Datentyp>Pole (complex analysis)Open sourceStatisticsText editorAdaptive behaviorOpen sourceExterior algebraMultiplication signRevision controlFile viewerSubject indexingMetadataDataflowSet (mathematics)WordCartesian coordinate systemMachine visionExpected valueGeometryComputing platformProjective planeProduct (business)Row (database)ChainDampingVideo gameConnectivity (graph theory)Field (computer science)WaveSoftwareCycle (graph theory)Computer animation
Transcript: English(auto-generated)
00:08
So yes Thank you to stay there for the last session. So today we're going to talk about how we want to revamp the addition process within GeoNetwork and
00:20
To explain how this is integrated in a whole plan that we have for the GeoNetwork metadata catalog So first an introduction, so we are both from camp to camp Working for a long time with data and metadata I'm Florian Graven, the head of technology of camp to camp and I'm giving a talk with Olivia, our
00:45
Architects and we are both involved in GeoNetwork for a long time and I would say that we are both passionate about Data in general, maybe not in metadata But what we are trying to achieve in camp to camp is try to make
01:00
The life of people who are maintaining metadata easier So we are talking mostly about GeoNetwork, which is a OSGO software about metadata cataloging and the thing that we want to focus on and to emphasize on is that all of this work to edit a part is
01:24
is Embracing a vision that we want to make GeoNetwork More compatible with open data and Because we have seen that many people they have bought both open data and GeoData catalog and it's hard to deal with So we are trying really trying to make a move and to do a turn within GeoNetwork to embrace the open data world
01:44
Toward a unique catalog, which will be really simpler for everyone So what is our ambition with the editor and with all this approach in general? Actually is the Metadata maturity report of the European Commission
02:03
really Put a note, not a note, but the level of adoption of every country about metadata and open data adoption and One thing, one criteria is how they use tools like portal or APIs or things like that. So I think we think that it's our
02:23
Duty to help them toward that way to be able to Develop everywhere and deploy everywhere open data catalog in an easier way so we are trying to push and to bring innovation toward this domain and To help everyone fill the gap with
02:41
data openness in general we also try to dynamize and support the rise of open data everywhere and to Make the transition toward a unique catalog easier and Also, what is very important is to promote and propose the reuse of the data so there were there have been other talk around this during the
03:04
the the week so globally the strategy was just to revamp the Services offered by GeoNetwork and the user interfaces. So the first step Toward this goal was the data hub, which is a search facade. So it's an alternative UI to search the data and
03:26
The second step is the editor facade, which is an alternative to simplify the addition of the metadata What is important to see is that the data hub is already
03:41
Available for anybody who is using GeoNetwork and it really is people's life While searching for data and it's open data oriented the use cases and the user experience But we are just on the halfway to complete the whole schema why because actually the data hub so many region they already have their data hub and
04:06
It's gather open data and geo data, but in the back end usually what it's done is that we are able to harvest any kind of Open data catalog. So usually we maintain geo data and we harvest open data catalog from outside
04:24
The data hub centralized that but we are just the halfway of the process because now We need to be independent on how we feed the catalog How we don't want to rely on open data catalog anymore. So we need to have to continue the path
04:41
To to make able to easily edit simple data simple metadata and that I will not geospatial to get rid of those other satellites Catalogs, so the idea the idea is that the editor that Olivia is going to present we had to feed the open data
05:04
the date geospatial data So the platform could get rid of external and proprietary Softwares, so I'll let you Olivia introduce that Thank you Okay, so Now first I want to take a look about
05:22
Take a look at the current experience for authoring metadata in general just to see where we're coming from So general network has offered a Solution for editing metadata for a very long time and it's always being built in a way that's kind of targeted at
05:41
an expert audience It's It can be confusing for users who are not trained or not proficient in the old metadata schemas and stuff like that and Also when you are in the authoring and the editing interface The form is very complex and that's because your network doesn't really offer a real abstraction over the underlying schema
06:08
For the metadata, so you have all these fields and Experts are often happy with that because they want to tweak every field in a very certain way in a very precise way yeah, but that's pretty much what's currently in place and
06:25
This has been hard to use for many people for a long time We've heard that for a while now people have thought about it. We've discussed it in a community and We it's been a long time since we identified a few axis of improvements Readability usability of the user interface you do use a journey through all the experience of working with meta data
06:47
And also having an overview of your your records and your organization's records So I can't account we've been really Trying to push for the idea of writing a new editor The community has been I would say it's played between different opinions some people would be more inclined to do incremental
07:08
Improvements to this existing solution and we have I think most of the time we've been pushing for a new editor Going to a very different direction So this is kind of the history history of what happened so far because it all these process took several years
07:25
In 2020 we started working on the Jio Network UI project Which is a new UI for Jio Network, which eventually allowed us to do the data hub that Florent talked about This gathered interest notably from the Jio Kestra community
07:43
Which was very in line with our vision for a new editor So we had their support and we could keep going. We eventually wrote down our vision for the new editor which would use the existing blocks that were in Jio Network UI and so we would build on the experience of this project and
08:03
Eventually was presented to a PSC of Jio Network which said Okay, this looks good. You can you can proceed and we see how this goes and then we started the crowdfunding campaign because Our partners were interested but no one had enough fun to say Okay, we will support you through all of this because it's quite a big undertaking
08:23
So crowdfunding campaign for this was a solution. It was a tricky exercise and in the meantime We also did some preliminary work to have like some prototypes also UX and markups so we wanted to show something concrete to people and Yeah, and this year first part of first half of 2023. We eventually reached the goals of the crowdfunding
08:47
So a few words on crowdfunding so we started in full advertising our vision and writing articles and The initial work was covered by R&D budget I came to camp Doing the mock-ups working on the pivot format, which I'm going to talk about later, which was really
09:05
essential to all this vision and And we had a lot of interest for many partners. It was very it was actually great to hear so much positive feedback So that was great. We're super happy with the experience You can see here the little gauge of how much money was pledged eventually
09:23
wait, so At that time we identified a few core UX concepts for the new editor We wanted to make sure that you the user would be able to stop and come back to what they were doing Because writing metadata can be can take a while. Maybe sometimes
09:41
You want to have a break or something so we wanted to make sure that the user was not trapped in an interface or something We wanted to make sure that the cognitive load was not Was manageable so we have said seven years or less visible on screen Also give a clear overview of how far you are in filling up mandatory fields if you have we want to have metadata
10:07
Compliant with inspire. For example, we give you a progress bar saying you did four you have six to go, you know, almost there Trying to encourage the user and support them Right, make sure that the user cannot make mistakes when filling fields, which is basic UX stuff
10:26
I would say and also of our preview of the of the record before publishing right, so we found that we Found that our Do our vision for the new editor on these three founding principles
10:42
The first one is make metadata accessible to everyone This is implying that it's not just for experts and then forget about metadata schemas and then build your own editor Right. So the first one make metadata accessible to everyone. It's pretty straightforward We just wanted it to be be it from the ground up with a user centric approach
11:04
So before writing any kind of code, we just wanted to have we organized like interviews with users user groups we set up working groups that would think about workflows different screens different actions and then we would
11:20
These groups would iterate on mock-ups and then we would implement the mock-ups Right and then forget about metadata schemas. That was also something very very important for us We wanted to make sure that the people Writing metadata would not have to know anything about schemas
11:45
So we introduced the idea of a pivot format here the pivot formats It's a it's an internal format That will allow us to convert back and forth to several Interoperability formats and then whenever the user interacts with the form
12:05
With any kind of editing form we would just work with the pivot format instead of editing in whatever schema we are Concerned with that's a big change because your network offer the current general work For example offers different forms depending on the schema you use
12:25
Right and then so the pivot format just a few words. It's an internal format. We are not introducing a new metadata Format in the wide it's not Stable it it will evolve and
12:40
It's yeah, it's really internal it will be serialized it will be able to be serialized in different ways and Potentially in the future be serialized to be stored in the database relational database so it's really something that opens up a lot of possibilities and We want it also to make sure we want to make sure that this format can handle most of the inspire
13:04
Mandatory fields Because we want Users of this new editor to also be able to produce inspire compliance records in an easy way It's something that was expressed very strongly by most of the users They don't want to worry about it, basically
13:22
Right there was a first conversion written for ISO 19 131 and there's a demo application online That showcases this conversion so you can try it It's on your network that github.io slash Jana to our QI slash simple editor
13:41
So everything is written in JavaScript It means I can run in different environments. We're not limited to the browser or the back end And there was something very important. Is that the transformation preserved the original document will not destroying When we're converting back and forth to to ISO schema, for example, we're not destroying the original metadata
14:03
We're just amending part of the XML document that we changed this is very important because Metadata documents are sometimes written in complex ways and contain information that we don't want to lose. So it's not overwritten and There's a lot of test coverage for us
14:20
It's really important to make sure that whenever the converters evolve and they will evolve We don't lose any feature. We don't lose any kind of functionality So hopefully we'll be able to not do XSL anymore At least some of us don't want to Right, so converters, we will be able to implement more and more converters as the need arise and
14:45
Yeah, so it's a it's for us it's a very Promising approach and it works for ISO and there's no reason that it won't work for any other schema because ISO is quite complex on its own and One of the last really interesting things about the converters is that could be used for more
15:03
It can be used for creating and editing metadata It could could also be used later on for harvesting if you harvest a catalog that outputs dcat You could just convert the records to the pivot format and store them and you could also say well this dcat catalog I can just have the data hub Run over it and search through it because I can convert the records in real time in the front end
15:26
So it gives a lot of flexibility Right and then build your own editor So basically the editor will be made of building blocks and then the administrator will be able to configure it configure it customize it in different ways
15:41
yeah, and the key part here is that we want to provide a default configuration that Enables people to may inspire compliant records again Right a few few mock-ups now. So the all the marker the UX work was made in French. So the markups are in French You see here. This is the dashboard
16:01
This is basically when you will arrive and you will see you records your organization's records have a few information about how much you are what's in currently in progress and Then you would be the first section when you provide the data Second section when where you describe it give it the title abstract, etc
16:21
And then the third part where you would describe how it is published So which license which usage conditions which keywords and things like that? right and just a few words to finish on the Architecture because this how this is going to work and it already works like that actually we have something running
16:41
Very simple is that we will not use your network for editing API basically, we will just use your network for as an Storage of XML documents. So we load if we want to edit a document we load it in XML We transform it to the pivot format. Then we edit it in however way we want
17:00
We convert it back to XM and we store it like that So it takes a lot of responsibility away from the back end and the whole process is really that is Simpler and it's really fast actually. So yeah, we are really happy with that how it works Right, okay Okay, thank you
17:23
so I think to to wrap up about What we just said is In the data world and metadata world you have experts who are really need to be compliant with complex schemas, but we Yeah, we saw that we forgot that that there are a lot of people who doesn't care about that and just want to feel
17:45
Metadata because they want their data to be searchable credible and findable And within the work with the editor, we want to address that to those people We want also to make the contribution easier like with JavaScript and the XSL things etc
18:02
So I think overall the experience would be better for the users and the developers Quick word about the roadmap So we're going to start the editor this this summer to work on the code base And yes, so actually so in a year, hopefully
18:22
Everybody will be able to have a first vision in production then you can plug your geo network on so Note that the old editor is not going to disappear. It's going to be an alternative like the data hub for the search So you still be able to edit very complex schemas or metadata if you need to but if you don't need to you just
18:45
Can use the the editor in a year, hopefully and then the configurability the extension Yeah, the it's good is going to to be on a second step So people will be really able to to design the editor what section what shortcuts?
19:06
What auto feel because what we want is that the people Feel the less field as possible. It's the expectation of everyone
19:21
So last word about the the roadmap so it's a big big big big schema, but Just relate the the history of the geonetwork UI project and the revamp of all this stuff So we have an application called data feeder that is going to be merged into the leader
19:44
Where you can upload the data and they are ingested and we extract automatically metadata out of it the data hub there is also my viewer in geonetwork UI and There is the version 1 this year and we just started the metadata editor and there are other components as you can see
20:03
So we told this this week you can find find the records maybe online after the conference about the API so for the reuse, so we are trying to to yeah to to make a product for the world chain and
20:20
Then maybe we will work on the ingestion of the data as well Because we want to turn out to the data platform and to cover the whole lifecycle of the data flow So to conclude the promise of the work we are doing is All of this world we think that it was very important for us not to start
20:45
something completely from scratch or to present another product but To apply that to an existing product So that's why we wanted to do that under the umbrella of geonetwork because we think that it's a very great engine to deal Data and metadata and search and indexing so it was a bigger effort
21:06
I would say but I think it's how we work We just try to adapt things and make things evolve to be better within the OS geo community So I think hopefully it's going to be the best alternative the best free and open source
21:25
alternative to manage your data sets in general So that's the promise and I think We're on the good way for that and we have we are already successful with the data hub and hopefully the editor will
21:42
Make life easier and people will be happy that it lands in their ecosystem Thank you The sponsors just Thanks to all guys that they responded to the crowdfunding and gave money and help us and believe in our vision And we hope that all other people will come along
22:04
To make the editor even better and and yes now it's time for the thank you
Recommendations
Series of 8 media