[GeoNetwork-users] Status of GeoNetwork API (old vs. new)

Hello,

Would it be possible to get snapshot of Geonetwork API status, as of today:

- Is the old API yet dismissed, and if yes since which version of
Geonetwork?

- Is it still the new API in beta stage? Or did you reach a stable API
version? (for which we could consider that later minor revisions to come
would not break backward-compatibility) If yes, since which version of
Geonetwork?

These questions around the Geonetwork API are conditioning the upgrade of
Geonetwork, and they are various institutions I'm interacting with that
unfortunately do not make this step, because of this beta stage.

Given this, they prefer to stick with the old API, even if it is not
standardized and completed as the new one could be.

Thanks in advance

Best regards,

Emmanuel

PS : I'm posting this question here, as I suppose that you want to keep
Github tickets for dev, and not questions

Hi Emmanuel

See feedback inline. In any case would be good to hear from other
developers also.

Regards,
Jose García

On Wed, Feb 14, 2018 at 1:01 PM, Emmanuel Blondel (GMAIL) <
emmanuel.blondel1@anonymised.com> wrote:

Hello,

Would it be possible to get snapshot of Geonetwork API status, as of today:

- Is the old API yet dismissed, and if yes since which version of
Geonetwork?

In 3.4.x the old API is still available, but services that has been
replaced in the new API has been annotated in the code as deprecated.

Unfortunately there's no documentation about the deprecated services and
the new services replacing them. That would be nice to have.

- Is it still the new API in beta stage? Or did you reach a stable API
version? (for which we could consider that later minor revisions to come
would not break backward-compatibility) If yes, since which version of
Geonetwork?

I don't know the reason to indicate it's still in beta, I think probably
that applies to GN 3.0.x, where this new API was started, but in 3.4.x all
the new services are added in the new API and the UI has been updated to
use
the new services instead of the deprecated ones.

But there're also still some services not migrated and still in the old API
(these services for sure haven't been deprecated).

About not breaking backward-compatibility, this is also something we should
consider to version the API in case of such changes are required. For now I
don't think we got to that case (possibly as didn't pay much attention to
backward-compatibility for now), but it's something that should be managed
properly.

These questions around the Geonetwork API are conditioning the upgrade of
Geonetwork, and they are various institutions I'm interacting with that
unfortunately do not make this step, because of this beta stage.

Given this, they prefer to stick with the old API, even if it is not
standardized and completed as the new one could be.

Thanks in advance

Best regards,

Emmanuel

PS : I'm posting this question here, as I suppose that you want to keep
Github tickets for dev, and not questions

------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork

--

*Vriendelijke groeten / Kind regards,Jose García
<http://www.geocat.net/&gt;Veenderweg 136721 WD BennekomThe NetherlandsT: +31
(0)318 416664 <+31318416664> <https://www.facebook.com/geocatbv&gt;
<https://twitter.com/geocat_bv&gt;
<https://plus.google.com/u/1/+GeocatNetbv/posts&gt;Please consider the
environment before printing this email.*