[GeoNetwork-devel] CFV / Schema plugin / Add schema bean to make it more plugable

GeoNetwork GeoNetwork Developer
1

Dear PSC,
Here is the proposal to improve schema plugin mechanism https://github.com/geonetwork/core-geonetwork/wiki/Proposal:-Schema-plugin-improvement. Existing plugins only needs to be migrated to a maven module. There is no change to the schema configuration folder. This proposal will be required to use the ISO19115-3 plugin

You can find the code changes in this pull request: https://github.com/geonetwork/core-geonetwork/pull/615

Looking forward to your votes.

Thanks

Francois

2

Hi all, I applied the changes.

For those of you who are using schema plugins, I made the following changes to the schema plugin repository as described in the proposal :

A script is available for the migration (https://github.com/geonetwork/schema-plugins/blob/develop/migrate-to-maven.sh), I applied it to all existing schema-plugins. For iso19139.* plugins they will use the iso19139 bean by default (which means same logic for associated resources management and multilingual handling).

Let me know if you have trouble with the plugins.

Cheers.

Francois

···

2014-08-25 7:42 GMT+02:00 Jesse Eichar <jesse.eichar@anonymised.com>:

As I said on pull request : +1. Looks to add some nice clean up of the code.

On Fri, Aug 22, 2014 at 16:20 PM, Francois Prunayre fx.prunayre@anonymised.com wrote:

Dear PSC,
Here is the proposal to improve schema plugin mechanism https://github.com/geonetwork/core-geonetwork/wiki/Proposal:-Schema-plugin-improvement. Existing plugins only needs to be migrated to a maven module. There is no change to the schema configuration folder. This proposal will be required to use the ISO19115-3 plugin

You can find the code changes in this pull request: https://github.com/geonetwork/core-geonetwork/pull/615

Looking forward to your votes.

Thanks

Francois

3

Hi François,

Great work! Sorry for missing the CFV…

Maria started working on moving schema plugins to metadata101 on github some time ago. Not sure how this is impacting that? Also, it would be good if we jointly worked on such move and continue developing the plugins in that repository. What do you think?

Cheers,
Jeroen

···

2014-08-25 7:42 GMT+02:00 Jesse Eichar <jesse.eichar@anonymised.com>:

As I said on pull request : +1. Looks to add some nice clean up of the code.

On Fri, Aug 22, 2014 at 16:20 PM, Francois Prunayre fx.prunayre@anonymised.com wrote:

Dear PSC,
Here is the proposal to improve schema plugin mechanism https://github.com/geonetwork/core-geonetwork/wiki/Proposal:-Schema-plugin-improvement. Existing plugins only needs to be migrated to a maven module. There is no change to the schema configuration folder. This proposal will be required to use the ISO19115-3 plugin

You can find the code changes in this pull request: https://github.com/geonetwork/core-geonetwork/pull/615

Looking forward to your votes.

Thanks

Francois

4

2014-09-04 12:29 GMT+02:00 Jeroen Ticheler <jeroen.ticheler@anonymised.com>:

Hi François,

Great work! Sorry for missing the CFV...

Maria started working on moving schema plugins to metadata101 on github
some time ago. Not sure how this is impacting that? Also, it would be good
if we jointly worked on such move and continue developing the plugins in
that repository. What do you think?

Yes sure. The proposal makes each plugin a maven module it does not
introduce many changes but gives more flexibility. In the move to
metadata101, we could plan to have one repository per schema in order to
easily add a schema to an installation. Simon already did a start for MCP
https://github.com/metadata101/Marine-Community-Profile-1.5

To be continued...

Francois

Cheers,
Jeroen

On 4 sep. 2014, at 10:53, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Hi all, I applied the changes.

For those of you who are using schema plugins, I made the following
changes to the schema plugin repository as described in the proposal :
* creation of 2.10.x branch (
https://github.com/geonetwork/schema-plugins/tree/2.10.x) based on master
to be used with 2.10.x branch of core-geonetwork
* creation of a develop branch for core-geonetwork/develop
* removed the master branch

A script is available for the migration (
https://github.com/geonetwork/schema-plugins/blob/develop/migrate-to-maven.sh),
I applied it to all existing schema-plugins. For iso19139.* plugins they
will use the iso19139 bean by default (which means same logic for
associated resources management and multilingual handling).

Let me know if you have trouble with the plugins.

Cheers.

Francois

2014-08-25 7:42 GMT+02:00 Jesse Eichar <jesse.eichar@anonymised.com>:

As I said on pull request : +1. Looks to add some nice clean up of the
code.

On Fri, Aug 22, 2014 at 16:20 PM, Francois Prunayre <
fx.prunayre@anonymised.com> wrote:

Dear PSC,
Here is the proposal to improve schema plugin mechanism
https://github.com/geonetwork/core-geonetwork/wiki/Proposal:-Schema-
plugin-improvement. Existing plugins only needs to be migrated to a
maven module. There is no change to the schema configuration folder. This
proposal will be required to use the ISO19115-3 plugin

You can find the code changes in this pull request:
https://github.com/geonetwork/core-geonetwork/pull/615

Looking forward to your votes.

Thanks
Francois

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork