-
-
Notifications
You must be signed in to change notification settings - Fork 489
Bolsena 2015
The idea is to be able to run a standalone metadata editor that doesn't have the rest of the features: csw server, search, harvesting,...
Current status: Working but not so easy to pull request to GeoNetwork. Working on it.
Based on the standalone editor, we created a maven artifact repository where GeoNetwork jars can be deployed. This way, we can create customized versions of GeoNetwork without having to git clone the full repository.
Current status: Deployed, but not official.
There are a couple of systems (EC, Tufts) that read an original GIS file and then create the metadata associated to it. We should decide which one to use, polish it and merge it back to GeoNetwork.
The idea is to be able to customize GeoNetwork without having to modify the source code of GeoNetwork. Overriding the UI amd adding new services with the event system.
Current status: Documentation ongoing.
Trying to make GeoNetwork more social, groups is something we can make more dynamic. Groups should have a boolean to indicate if they are public or not. And it they are public (or we can say: they accept users), then a user should have an option to request joining that group.
This join can be made automatically or maybe some useradmin of the group should be able to accept or reject the request.
We also need some configuration to be able to disable it.
Current status: Done for Cobweb, but still needs polishing to remove very strong customizations.
Cobweb is experimenting with GeoXACML.
Current status: Are we interested on it?
As with WFS, we need some way to display and download data from SOS.
Current status: To be started soon.
Metadata A is related to Metadata B. Metadata B has some links to some OGC services (or other onlineResource). Should metadata A show also the links?
Current status: Done in Cobweb. We have to decide if we want this on trunk.
To simplify development fo customizations in GeoNetwork without having to modify the source code of GeoNetwork, we created the event system. This system (right now supports only basic events) will fire some events when certain things happen in GeoNetwork (create metadata,update user, login) and then a developer can listen to that event and fire some specific code associated to it.
Current status: Done and merged. We should implement more types of events.
Taken from NGR. WFS servers can be contacted by GeoNetwork so the data gets downloaded. The user can select format (shapefile, geojson, whatever the server supports) and filter by bounding box.
Current status: Need merging from 2.10.something.
New services to get all the public metadata in DCAT format to export it.
Current status: Testing. Possible merge back to trunk at some point.
UI module/controls to easily manage WPS service.
Current status: Ongoing.
https://github.com/metadata101/iso19115-3
Current status: Done.
Schema plugin under development.
Schema plugin under development.
Released at the same time as GeoNetwork 3.
Current status: Released.
We should update the GeoNetwork version on the Osgeo Live DVD.
Current status: Ongoing (Jessie?)
It has a very old version of GeoNetwork. On the other hand it may have features interesting to GeoNetwork like the data extractor.
Current status: Plan to use GN 3 at some point.
A user can use the GeoNetwork map to create a WMC that will get saved along with the metadata that defines it.
Current status: Done on two different projects. We should try to merge it back.
While reviewing some of the new features we are working on, some other features popped out as interesting to many parties.
When we get requested to add a new language to GeoNetwork, what are the requirements the translation should meet to be allowed on Transifex? We agreed that we need to force at least a high percentage (85%?) of the translation already done to allow a new language.
It would be good to write some documentation on good practices and how to develop against GeoNetwork. Not only to developers of GeoNetwork, but also to people who extend it by customizations.
We need some place where we can check public URLs of different skins on GeoNetwork.
Some features on the UI are not enabled by default. We need some kind of documentation so we know they exist and they are available.
We should document the different angular modules of GeoNetwork, so adding new features is not very complex. At least, we should have some indication where to start.
¿ISO19115-3? allows to add comments to metadata. If we want to improve the social capabilities of GeoNetwork, this is a good task to complete.
- Protractor: https://angular.github.io/protractor/#/
- Integration Tests
- Unit Tests
We should improve them and make sure the tests pass.
Paul's proposal to be able to display on the UI vector data in the format of tables, graphs or maps easily.
Current status: Proposal.
Minimap obstructing the view of results. Home results overview in three columns. Too many hidden icons of small breakpoint? Labels missing on the tool bar. Main action buttons at the top (Add new record, import, manage)
Current status: Proposal.
If you have some comments, start a discussion, raise an issue or use one of our other communication channels to talk to us.