Custom editor examples

EEA spatial datasets editor

EEA spatial dataset editor is based on EEA metadata profile based on INSPIRE requirements with additional details about EEA encoding rules (eg. title, resource identifier convention).

../../_images/example-eea-sdi-editor.png

It illustrates:

  • Simple form with 2 levels only

  • Place label above input

  • Each fields have a clear description with links to EEA metadata profile documentation

  • Right panel link to helpdesk team

See configuration file.

Ifremer editors

Sextant catalog contains a large variety of spatial information described in french and/or english. Those datasets collected/created in various projects which have different needs adapt encoding forms to match projects requirements:

Sextant default editor

../../_images/example-sextant-geo.png
../../_images/example-sextant.png

It illustrates:

  • Custom button triggering process

And then specific editors are created depending on projects:

CERSAT projects

../../_images/example-cersat.png

It illustrates:

  • Custom tabs

  • Using table mode for rendering sensor instrument and platforms

  • Using custom buttons to add information when missing

Checkpoint projects

../../_images/example-medsea.png

It illustrates:

  • Heavy use of keywords for classification and description

  • Use project terminology

EMODNET projects

../../_images/example-emodnet.png

Metawal - SPW editor

../../_images/example-metawal.png

See configuration file.

It illustrates:

  • Using custom buttons to add associated resources

DCAT-AP plugin - Informatie Vlaanderen

../../_images/example-dcatnl.png
../../_images/example-dcatnl-tag.png

See DCAT-AP Schema Plugin.

Other plugins

Check also the plugin repository which contains other examples.