Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JS client API proposal #1848

Merged
merged 17 commits into from
Feb 10, 2017
Merged

JS client API proposal #1848

merged 17 commits into from
Feb 10, 2017

Conversation

fxprunayre
Copy link
Member

@fxprunayre fxprunayre commented Jan 23, 2017

See https://github.com/geonetwork/core-geonetwork/wiki/JS-client-API-Proposal

The JS API mode allows to build a catalog application from a JSON configuration file and the load of the GeoNetwork JS library. The main goals are:

  • clarify UI configuration (by grouping and documenting all UI options)
  • be able to embed GeoNetwork in third party website like CMS.
  • add admin interface to customize UI options (and preview results)

All UI settings are configurable in a specific admin tab:

image

The initial development was made for Ifremer to add GeoNetwork catalog and maps in Liferay & EZpublish. This proposal is supported by the Metawal project.

See video https://www.youtube.com/watch?v=pFyh8LZneIo

@fxprunayre fxprunayre added this to the 3.2.1 milestone Jan 23, 2017
@fxprunayre fxprunayre modified the milestones: 3.2.2, 3.2.1 Jan 23, 2017
@fxprunayre fxprunayre mentioned this pull request Feb 6, 2017
@fxprunayre fxprunayre modified the milestones: 3.2.2, 3.4.0 Feb 9, 2017
@fxprunayre fxprunayre changed the base branch from 3.2.x to develop February 10, 2017 12:53
@fxprunayre fxprunayre self-assigned this Feb 10, 2017
@fxprunayre fxprunayre merged commit 94a74bd into geonetwork:develop Feb 10, 2017
fxprunayre added a commit to fxprunayre/core-geonetwork that referenced this pull request Dec 18, 2018
The ui/config settings introduced
geonetwork#1848 (and inspired
from Sextant) is somehow a bit hard to maintain.

The default value is now set from CatController only.

The default db value is empty to use the one from CatController until a
db value is defined by the catalogue admin.

JsonDatabaseMigration task should be used to update the settings (see
geonetwork#2808). We should not
set the full value in SQL migration script anymore (BTW this is a line
in conflict in most of the PR since then).

JSON editor is now used instead of the textarea.

Future work required? Maybe we should find a better way to merge the db
value and update with the latest.
fxprunayre added a commit that referenced this pull request Dec 20, 2018
* UI configuration improvement.

The ui/config settings introduced
#1848 (and inspired
from Sextant) is somehow a bit hard to maintain.

The default value is now set from CatController only.

The default db value is empty to use the one from CatController until a
db value is defined by the catalogue admin.

JsonDatabaseMigration task should be used to update the settings (see
#2808). We should not
set the full value in SQL migration script anymore (BTW this is a line
in conflict in most of the PR since then).

JSON editor is now used instead of the textarea.
pvgenuchten pushed a commit to pvgenuchten/core-geonetwork that referenced this pull request Mar 17, 2021
* UI configuration improvement.

The ui/config settings introduced
geonetwork#1848 (and inspired
from Sextant) is somehow a bit hard to maintain.

The default value is now set from CatController only.

The default db value is empty to use the one from CatController until a
db value is defined by the catalogue admin.

JsonDatabaseMigration task should be used to update the settings (see
geonetwork#2808). We should not
set the full value in SQL migration script anymore (BTW this is a line
in conflict in most of the PR since then).

JSON editor is now used instead of the textarea.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant