Hi all, working on the new ISO19115-3 schema plugin, I need to make GeoNetwork less dependent on ISO19139 and for this I’m making some changes to the schema plugin architecture.
Here [1] is a draft proposal and here [2] a first implementation covering the relation search which could be now defined in the plugin and not in core.
If you have any comments on what has been done so far or ideas to improve the structure, let me know.
Thanks.
Francois
[1] https://github.com/geonetwork/core-geonetwork/wiki/Proposal:-Schema-plugin-improvement
[2] https://github.com/geonetwork/core-geonetwork/pull/615
Francois,
The proposal looks good (I'll let others comment on more of the details), but:
- presumably other services required by a schema plugin could be added using the same/similar methods? eg. in iso19139.mcp we have a few services that support creative commons licensing
- we need to create a branch of the current schemaplugins repo for 2.10.x? - I would like 19115-3 to be available in that branch, seems this wouldn't be hard given the fact that the schema folder is basically unchanged inside the new structure and we already have an angular editor implementation for 2.10.x
Cheers,
Simon
________________________________________
From: Francois Prunayre [fx.prunayre@anonymised.com]
Sent: Wednesday, 20 August 2014 11:49 PM
To: Devel geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] Schema plugin changes
Hi all, working on the new ISO19115-3 schema plugin, I need to make GeoNetwork less dependent on ISO19139 and for this I'm making some changes to the schema plugin architecture.
Here [1] is a draft proposal and here [2] a first implementation covering the relation search which could be now defined in the plugin and not in core.
If you have any comments on what has been done so far or ideas to improve the structure, let me know.
Thanks.
Francois
[1] Proposal: Schema plugin improvement · geonetwork/core-geonetwork Wiki · GitHub
[2] Schema plugin / Add schema bean to make it more plugable by fxprunayre · Pull Request #615 · geonetwork/core-geonetwork · GitHub
Thanks for the feedback Simon,
···
2014-08-20 17:58 GMT+02:00 <Simon.Pigot@anonymised.com>:
Francois,
The proposal looks good (I’ll let others comment on more of the details), but:
- presumably other services required by a schema plugin could be added using the same/similar methods? eg. in iso19139.mcp we have a few services that support creative commons licensing
Yes, I’ll also see CSW outputSchema which should be defined on the plugin. I’ve added interface for adding features to a plugin eg.
https://github.com/fxprunayre/core-geonetwork/blob/improvement/schema-plugin-bean/schemas/iso19139/src/main/java/org/fao/geonet/schema/iso19139/ISO19139SchemaPlugin.java#L22
- we need to create a branch of the current schemaplugins repo for 2.10.x?
I agree, I’ll do that and rename master as develop like in core-geonetwork.
- I would like 19115-3 to be available in that branch, seems this wouldn’t be hard given the fact that the schema folder is basically unchanged inside the new structure and we already have an angular editor implementation for 2.10.x
Do you think also backporting the schema plugin bean to 2.10.x or only basic support in 2.10.x for 19115-3 ?
Cheers.
Francois
Cheers,
Simon
From: Francois Prunayre [fx.prunayre@anonymised.com]
Sent: Wednesday, 20 August 2014 11:49 PM
To: Devel geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] Schema plugin changes
Hi all, working on the new ISO19115-3 schema plugin, I need to make GeoNetwork less dependent on ISO19139 and for this I’m making some changes to the schema plugin architecture.
Here [1] is a draft proposal and here [2] a first implementation covering the relation search which could be now defined in the plugin and not in core.
If you have any comments on what has been done so far or ideas to improve the structure, let me know.
Thanks.
Francois
[1] https://github.com/geonetwork/core-geonetwork/wiki/Proposal:-Schema-plugin-improvement
[2] https://github.com/geonetwork/core-geonetwork/pull/615