SDG Ontology Visualizer

A tool for visualizing ontologies related to UN's Sustainable Development Goals

The project is deployed here

Installation (Docker & GraphDB users)

For installation, see the installation guide extracted from the project report. The guide contains:

• Docker installation
• Deployment
• Local development
• User setup on GraphDB

Import Ontology to GraphDB

Run: yarn in both /backend and /frontend to install dependencies

Local development is possible both with and without Docker.

• Without Docker: Run yarn start in the /backend and go to url: localhost:7200
  • If prompted with a login page: Log in with details provided in .env file in the /backend folder. If the file is missing, follow the installation guide, section A.3 Local development.
  • NOTE: Docker is still required to deploy local changes to the hosted website.
• With Docker: Follow the installation guide, section A.3 Local development

  • NOTE: Every time the ontology is updated, the data needs to be updated with the follong command: Run python3 datagen.py in /utils folder (image below).

    

You should now see this:

GraphDB Standard Edition

1. Delete existing repository under: Setup > Repositories
2. Add a new repository WITH the arrow down button (.ttl file): backend > database > conf
3. Follow the rest of GraphDB Free Edition guide

GraphDB Free Edition

1. Navigate to: Import > RDF
2. Delete existing .owl file (if it exists)
3. click Upload RDF files and choose .owl file: backend > database > ontology
4. Press Import and a green text with "Imported successfully" should be displayed as seen in the image below

Work Environment (technical)

Ontology

• If the node in the ontology is of none or multiple types, the individual will not be displayed in the graph. This is because the ontology exists of many individuals not needed in the graph.
• Every node needs a label of type string in order to be displaed in the graph.
  • If the label contains a parentheses symbol there will be an error when clicking the node.

What's new

Implemented the KPIs from U4SSC

The KPIs are divided into categories from the Triple Bottom Line (economy, enviornment and Social and Culture). This categorization is gathered from an Air Table.

here is a custom edge between two nodes called: Egendefinert Vemund. The reason behind this edge is to illustrate the possibility of an ontology and how KPIs is connected accross different categories and not belonging to one category only.

Implemented Trondheim Municipality (Kommune)

When implementing TK (Trondheim kommune) into the ontology, it was important to get a lot of details combined with an easy to understand overview. Thus TK was divided into resulted in directories and further into units. The division was based on this hierarchy.

Map KPI to TK

This part is pure self defined as it is no current defined relation between KPI and TK. Therefore the relations are defined logically. It should be noted that not all KPIs are mapped, just some of them to prove the possibility of the ontology. Also, since the relations are not defined by any legit source, they most likely will have to be re-defined and that would be a lot of unnecerary work.

Future Work

visualize if TK can complete KPIs within the deadline of 2030.

An ideá is to make a toggle button and when pressed, all willBeCompleted KPIs will be green and the rest will be red. Currently the backend part of this step is finished.

Approved relations between TK - KPI and KPI and categories.

This needs to be approved by someone, somehow.

If a KPI are achieved, how will that affect other KPIs.

Algorithm.

Change the code so that a node be be of several types (techical)

By doing this, we avoid duplicates of instances within the ontology e.g., Transport can be of type Utviklingsområde and Kategori. However now there exist two of them, though with different name.

Images

This section contains images from the website