Hello Gabriel,

Indeed, I thought of this as well and did hint at this option somewhere but I guess it was lost in between embarrassing bickering that made up most of the thread.

I like the idea, but I would like to avoid duplicating all of the CSW module code.

My suggestion would be to separate all of the ISO metadata profile into a separate module "gs-csw-iso" and downgrade this module to community status (this shouldn't be a problem, as mentioned before, the current implementation is actually too buggy to be considered a proper feature, and the current maintainers of the CSW module are not familiar with it themselves, as they admit).

The only thing I think that would still need to be duplicated is the GenericRecordBuilder which is now used for both DC and ISO, but I had to make considerable improvements to it to accommodate for the complexity of the ISO scheme (for DC, the old version is sufficient).

I might still need to add a little hook here or there in the core CSW extension, but hopefully that won't be a problem then.

Does this sound like a reasonable compromise/solution?

Kind Regards

Niels

On 30/04/2019 01:19, Gabriel Roldan wrote:
Glanced at all the outstanding CSW extension pull requests.

It happens from time to time that a given extension has no official maintainer, but it keeps being an extension because people might be using it, right?

By the other hand, Niels is actively working on it but noone has the time to review/approve all those PR's.

So, why not just either downgrade it to a community module (unlikely), or create a separate comnunity module (does the NG postfix sound familiar to anyone?) so that he can do his business and when done and complies with all the requirements to upgrade to extension it can be a drop-in replacement for the current CSW extension?

Happened before, probably just in geotools ( wfs-ng, jdbc-ng, shapefile-ng? ), but I don't see why not, the project seems to be really flexible in allowing community modules.

it just occurred to me. 2c.

--
Gabriel Roldán


_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to