-
-
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.
//TODO
//TODO
//TODO
//TODO
//TODO
//TODO
//TODO
//TODO
//TODO
New services to get all the public metadata.
//TODO
//TODO
//TODO
//TODO
//TODO
//TODO
//TODO
//TODO
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.
If you have some comments, start a discussion, raise an issue or use one of our other communication channels to talk to us.