Skip to content
Valerio Vinciarelli edited this page Sep 23, 2020 · 1 revision

Overview

Currently EPOS TCS communities willing to provide EPOS-DCAT-AP metadata descriptions of data resources needs to undertake a manual process to produce metadata files, usually serialized in RDF/turtle, which is prone to (unintentional) errors.

The beta version of the Metadata Editor allows users to import EPOS-DCAT-AP SHACL constraints and create a new EPOS-DCAT_AP turtle files from scratch and validate them against SHACL constraint.

The editor includes a Graphical User Interface (GUI) to ease the creation of files also to those users who are not experts nor familiar with the EPOS-DCAT-AP model, and an export feature to ease the compilation of RDF/turtle files.

Functionalities

Below are described the functionalities available in the EPOS Metadata Editor, and then some screenshots show how these functionalities appear in the GUI.

  1. EPOS-DCAT-AP SHACL file import
    The application allows the user to import EPOS-DCAT-AP SHACL file from URL or local folder through a wizard.

  2. EPOS-DCAT-AP RDF/Turtle file creation from scratch The application allows the user to create a new EPOS-DCAT-AP RDF/Turtle file through a wizard.

  3. EPOS-DCAT-AP RDF/Turtle file import The application allows the user to import an existing EPOS-DCAT-AP RDF/Turtle file through a wizard.

  4. Metadata entities Graph representation The application uses libraries to visualize the metadata entities as a Graph (with nodes and relationships).

  5. Metadata entities population through nodes creation The application allows the user to create nodes by using Palette widget (e.g. Drag&Drop, double click, right click) which contains all shapes defined by EPOS-DCAT-AP SHACL constraints.

  6. Metadata entity properties population The application allows the user to fill in metadata entity properties through table representation, where the properties are grouped by mandatory, recommended and optional as they are defined in EPOS-DCAT-AP SHACL constraints.

  7. SHACL constraints validation The application uses libraries (Javax and Hibernate) to validate metadata entities against EPOS-DCAT-AP SHACL constraints.

  8. EPOS-DCAT-AP RDF/Turtle file serialization The application serializes the metadata entities into RDF/Turtle format and allows the user to visualize the file through an RDF/Turtle editor.

  9. EPOS-DCAT-AP RDF/Turtle file export The application allows the user to export EPOS-DCAT-AP RDF/Turtle file on local folder.

  10. Outline of metadata entities and relationships currently active on graph The application shows a view, named Outline, in order to display all nodes and relationships on graph. The nodes are grouped according to the shape type and are displayed in a tree-like structure.

  11. Nodes classification through colours The application assigns a random colour to each shape. The nodes are coloured according to the shape type and the user is able afterwards to customize them.

  12. Dataset pre-compilation from DOI The development of this functionality is based on a mapping work carried out at the Joint Research Centre of the European Commission in order to align DataCite metadata with DCAT-AP through an XSLT-based implementation (https://ec-jrc.github.io/datacite-to-dcat-ap/). In particular, we created an extension of this XSLT (https://github.com/ec-jrc/datacite-to-dcat-ap/) for EPOS-DCAT Application Profile which is used by EPOS Metadata Editor to transform the DataCite metadata into EPOS-DCAT-AP entities/properties. The application:

    1. Allows the user to specify a DOI;
    2. Transforms the DataCite metadata into EPOS-DCAT-AP by using XSLT;
    3. Pre-compiles the GUI with available metadata (nodes, relationships, properties).
  13. GIT module implementation This functionality allows users to push EPOS-DCAT-AP RDF/Turtle files created or updated through the EPOS Metadata Editor to their favorite Git repository. In particular, the application uses JGit Java library to create a specific branch on a Git repository by using the native Git implementation for the authentication.

  14. Improvements/bug fixing guided by the users' feedback We improved existing functionalities on the basis of users' feedback. In particular, the application allows:

    • to apply filters on the graph in order to visualize or hide nodes
    • to specify spatial information (POLYGON, POINT) by using a GeoMap GUI widget.

References

  1. https://github.com/epos-eu/EPOS-DCAT-AP
  2. https://wiki.eclipse.org/Rich_Client_Platform

Clone this wiki locally